[Touch-packages] [Bug 1648312] Re: discovered an unintentional extra feature in the spread aka task switcher
well then, why is it so hard to execute the short swipe? I only manage to perform it 2-3 times out of 10. Then this feature should be fixed ** Changed in: ubuntu-keyboard (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648312 Title: short swipe on spread gesture Status in ubuntu-keyboard package in Ubuntu: New Bug description: Using Ubuntu Touch 15.04 (r480) on Meizu MX4. The spread gesture is drag from the right edge to the left. While I was working in windowed mode, I only today learnt about the apparently long present short swipe function: the gesture, if only performed mid-way, and then discontinued, would execute a cross-fade transition between the current window and the next window in the z-order queue, and then switch to that window WITHOUT going to the full spread. Later I tried to reproduce only to learn that it is not easy, because the gesture has to be discontinued very very precisely, otherwise the full spread mode will kick in. ORIGINAL: "Obviously now, I understand that this is not really a feature, rather an undocumented behavior of sort. But I like it. Perhaps this could be tuned, to the point where it can become an ACTUAL feature, that users could take advantage of?" UPDATED: been informed (see coments) that this is actually a feature, so, I'd like to file a bug: the supposed feature is VERY hard to execute, most of attempts end up not executing it at all, because it apparently requires that the gesture be stopped at a VERY precise point in order to be recognized as the short swipe, and not a long swipe. Attached is me trying to capture the scenario on camera. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648312/+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 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]
Please let us know what the "Selected driver" log message was. Or better yet, attach the full log output. A similar error was encountered in bug 1355005 and although that bug is unclear it seems to generally be a case of Mir selecting a driver other than mesa-kms, and if that happens then such other drivers will reject the --vt 1 option. So if you Raspberry Pi is selecting the mesa-kms driver then yes we have a Mir bug. If it's not and is somehow selecting the Android driver instead (and if that actually works) only then is it a bug in the snap (should not be passing --vt 1). ** Changed in: mir Status: New => Incomplete ** Changed in: mir (Ubuntu) Status: New => Incomplete -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1648312] Re: discovered an unintentional extra feature in the spread aka task switcher
It *is* a feature, and has been there since the early days of ubuntu touch: - short swipe from the right edge: switch to the most recent app - long swipe: reveal the app spread ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648312 Title: discovered an unintentional extra feature in the spread aka task switcher Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Using Ubuntu Touch 15.04 (r480) on Meizu MX4. The spread gesture is drag from the right edge to the left. Only today I was doing the gesture slowly only to discover, what I thought was an extra feature, in the windowed mode: the gesture, if only performed mid-way, and then discontinued, would execute a cross-fade transition between the current window and the next window in the z-order queue, and then switch to that window WITHOUT going to the full spread. Later I tried to reproduce only to learn that it is not easy, because the gesture has to be discontinued very very precisely, otherwise the full spread mode will kick in. Obviously now, I understand that this is not really a feature, rather an undocumented behavior of sort. But I like it. Perhaps this could be tuned, to the point where it can become an ACTUAL feature, that users could take advantage of? Attached is me trying to capture the scenario on camera. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648312/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame
And again:
06:27:08 11:
/<>/mir-0.25.0+xenial3115bzr3852/tests/acceptance-tests/test_client_input.cpp:667:
Failure
06:27:08 11: Mock function called more times than expected - returning directly.
06:27:08 11: Function call: handle_input(touch_event(when=1476068422342080
(39.829455ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=10.9263, y=17.4821, pressure=1, major=8, minor=5, size=8}, modifiers=none))
06:27:08 11: Expected: to be called between 20 and 180 times
06:27:08 11: Actual: called 181 times - over-saturated and active
06:27:08 11:
06:27:08 11: GMOCK WARNING:
06:27:08 11: Uninteresting mock function call - returning directly.
06:27:08 11: Function call: handle_input(touch_event(when=1476068744375968
(24.843672ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=10.97,
y=17.552, pressure=1, major=8, minor=5, size=8}, modifiers=none))
06:27:08 11: Stack trace:
06:27:08 11: [2016-12-08 06:27:08.848436] mirserver: Stopping
06:27:08 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame
(5518 ms)
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/3086/consoleFull
--
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/1570698
Title:
CI failure in TestClientInput.receives_one_touch_event_per_frame
Status in Mir:
Triaged
Status in mir package in Ubuntu:
Triaged
Bug description:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull
02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy
(version 0.22.0)
02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display
configuration:
02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800
60.00Hz
02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800
60.00Hz
02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver:
mir:stub-input (version: 0.22.0)
02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
02:44:44 11:
02:44:44 11: GMOCK WARNING:
02:44:44 11: Uninteresting mock function call - returning directly.
02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:44 11: Stack trace:
02:44:44 11:
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
Failure
02:44:44 11: The difference between 1.0f and client_input_events_per_frame is
0.2400953674316, which exceeds 0.2f, where
02:44:44 11: 1.0f evaluates to 1,
02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684,
and
02:44:44 11: 0.2f evaluates to 0.2000298023224.
02:44:44 11:
02:44:44 11: GMOCK WARNING:
02:44:44 11: Uninteresting mock function call - returning directly.
02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:45 11: Stack trace:
02:44:45 11:
02:44:45 11: GMOCK WARNING:
02:44:45 11: Uninteresting mock function call - returning directly.
02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:45 11: Stack trace:
02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame
(4083 ms)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1646758] Re: Can't update or install apps
For me everythings right with the new update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646758 Title: Can't update or install apps Status in Canonical System Image: Fix Released Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: bq M10 rc-proposed r243 When trying to update an app this morning, I got an error about destination path not being writable. The app is YouTube by Mateo Salta. Screenshot with the error attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646758/+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 1648319] [NEW] Failed to use bus name org.freedesktop.DisplayManager
Public bug reported: I have implemented the command lightdm --test-mode --debug and I happened here such error: == [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683 [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using Xephyr for X servers [+0.01s] DEBUG: Registered seat module xlocal [+0.01s] DEBUG: Registered seat module xremote [+0.01s] DEBUG: Registered seat module unity [+0.01s] DEBUG: Registered seat module surfaceflinger [+1.13s] DEBUG: Adding default seat [+1.13s] DEBUG: Seat: Starting [+1.13s] DEBUG: Seat: Creating greeter session [+1.17s] DEBUG: Seat: Creating display server of type x [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory) [+1.20s] DEBUG: Using VT 7 [+1.20s] DEBUG: Seat: Starting local X display on VT 7 [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+1.36s] DEBUG: DisplayServer x-1: Launching X Server [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+1.36s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? = On the Internet I have the exact solution to this problem is not found. The computer I have is only one graphics card and built-in The controller is not present. Somebody help than you can! ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: debian ** Tags added: debian ** Description changed: I have implemented the command lightdm --test-mode --debug and I happened here such error: == [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683 [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /var/lib/menu-xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/gdm/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using Xephyr for X servers [+0.01s] DEBUG: Registered seat module xlocal [+0.01s] DEBUG: Registered seat module xremote [+0.01s] DEBUG: Registered seat module unity [+0.01s] DEBUG: Registered seat module surfaceflinger [+1.13s] DEBUG: Adding default seat [+1.13s] DEBUG: Seat: Starting [+1.13s] DEBUG: Seat: Creating greeter session [+1.17s] DEBUG: Seat: Creating display server of type x [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory) [+1.20s] DEBUG: Using VT 7 [+1.20s] DEBUG: Seat
[Touch-packages] [Bug 1244989] Re: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop
I can not understand how to solve this problem! Will you help me? I have one vidoeokarta computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1244989 Title: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop Status in lightdm package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Bug description: Installed the Ubuntu 14.04 "Trusty Tahr" daily image (21-Oct-2013 13:57) into Virtualbox 4.2.18 r88780 and it won't load LightDM, I switched to tty1 and I see the following message: Stopping startpar bridge for notification of upstart job start/stop On several lines alternating between `[start]` and `[stop]` messages at the end. If I use `sudo lightdm restart` it just brings up a blank screen. I didn't have this specific problem when I was running the Saucy development branch. When I try to use `sudo lightdm restart` I get the error: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? and I get a blank screen again. Guest: lightdm 1.8.2 1851 MB of RAM Host: Pentium Dual-Core CPU E5200 @ 2.50GHz 4GB (3.7GiB) DDR2 RAM + 1.8GiB Swap nVidia GeForce 7100 (512MB GRAM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1244989/+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 1646758] Re: Can't update or install apps
The manual workaround, that has worked for me: $ sudo mount -o remount,rw / $ sudo mkdir /Downloads $ sudo chown -R phablet:phablet /Downloads $ sudo ln -s /home/phablet/Downloads /Downloads $ sudo mount -o remount,ro / I restarted my phone, but then I took full advantage of the hack, I got all the updates installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646758 Title: Can't update or install apps Status in Canonical System Image: Fix Released Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: bq M10 rc-proposed r243 When trying to update an app this morning, I got an error about destination path not being writable. The app is YouTube by Mateo Salta. Screenshot with the error attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646758/+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 1648312] [NEW] discovered an unintentional extra feature in the spread aka task switcher
Public bug reported: Using Ubuntu Touch 15.04 (r480) on Meizu MX4. The spread gesture is drag from the right edge to the left. Only today I was doing the gesture slowly only to discover, what I thought was an extra feature, in the windowed mode: the gesture, if only performed mid-way, and then discontinued, would execute a cross-fade transition between the current window and the next window in the z-order queue, and then switch to that window WITHOUT going to the full spread. Later I tried to reproduce only to learn that it is not easy, because the gesture has to be discontinued very very precisely, otherwise the full spread mode will kick in. Obviously now, I understand that this is not really a feature, rather an undocumented behavior of sort. But I like it. Perhaps this could be tuned, to the point where it can become an ACTUAL feature, that users could take advantage of? Attached is me trying to capture the scenario on camera. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Attachment added: "MAH05479.MP4" https://bugs.launchpad.net/bugs/1648312/+attachment/4788927/+files/MAH05479.MP4 ** Description changed: Using Ubuntu Touch 15.04 (r480) on Meizu MX4. The spread gesture is drag from the right edge to the left. Only today I was doing the gesture slowly only to discover, what I thought was an extra feature, in the windowed mode: the gesture, if only performed mid-way, and then discontinued, would - execute a cross-fade transition the current window with the next window - in the z-order queue, and then switch to that window WITHOUT going to - the full spread. + execute a cross-fade transition between the current window and the next + window in the z-order queue, and then switch to that window WITHOUT + going to the full spread. Later I tried to reproduce only to learn that it is not easy, because the gesture has to be discontinued very very precisely, otherwise the full spread mode will kick in. Obviously now, I understand that this is not really a feature, rather an undocumented behavior of sort. But I like it. Perhaps this could be tuned, to the point where it can become an ACTUAL feature, that users could take advantage of? Attached is me trying to capture the scenario on camera. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648312 Title: discovered an unintentional extra feature in the spread aka task switcher Status in ubuntu-keyboard package in Ubuntu: New Bug description: Using Ubuntu Touch 15.04 (r480) on Meizu MX4. The spread gesture is drag from the right edge to the left. Only today I was doing the gesture slowly only to discover, what I thought was an extra feature, in the windowed mode: the gesture, if only performed mid-way, and then discontinued, would execute a cross-fade transition between the current window and the next window in the z-order queue, and then switch to that window WITHOUT going to the full spread. Later I tried to reproduce only to learn that it is not easy, because the gesture has to be discontinued very very precisely, otherwise the full spread mode will kick in. Obviously now, I understand that this is not really a feature, rather an undocumented behavior of sort. But I like it. Perhaps this could be tuned, to the point where it can become an ACTUAL feature, that users could take advantage of? Attached is me trying to capture the scenario on camera. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648312/+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 1648303] [NEW] wifi saved networks don't have effect, despite being listed
Public bug reported: I hesitated to file this bug for approx a week because none else seemed to report simillar issue, and felt like I was dealing with some weird edge case. But: When I connect to password protected wifi access point the network gets saved in System Settings / Wi-Fi / Previous Networks. Despite it being saved, it never seems to take any effect once disconnected form the saved network, and returning to it. It will ask me for password over and over again, and also save it over and over again under Wi-Fi/Previous networks, with the same name but suffixed with an ever increasing index. In the attached screen you can see "sd 3" and "sd3 1" but it would go on and on to probably "sd3 99" and beyond. My phone is Meizu MX4. I was using r478 earlier today, which was already 2-3 updates through since I started seeing this problem, and it persisted. I reflashed my phone to some old double digit release (i think r79), and it worked. Then I updated, this time I was already directly updated to r480, which I am currently on, but the problem returned. The attached screen is taken under r480. Perhaps I am an isolated case, but I reproduced this problem even after reflashing and updating to recent release. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161208_134745965.png" https://bugs.launchpad.net/bugs/1648303/+attachment/4788903/+files/screenshot20161208_134745965.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648303 Title: wifi saved networks don't have effect, despite being listed Status in ubuntu-keyboard package in Ubuntu: New Bug description: I hesitated to file this bug for approx a week because none else seemed to report simillar issue, and felt like I was dealing with some weird edge case. But: When I connect to password protected wifi access point the network gets saved in System Settings / Wi-Fi / Previous Networks. Despite it being saved, it never seems to take any effect once disconnected form the saved network, and returning to it. It will ask me for password over and over again, and also save it over and over again under Wi-Fi/Previous networks, with the same name but suffixed with an ever increasing index. In the attached screen you can see "sd 3" and "sd3 1" but it would go on and on to probably "sd3 99" and beyond. My phone is Meizu MX4. I was using r478 earlier today, which was already 2-3 updates through since I started seeing this problem, and it persisted. I reflashed my phone to some old double digit release (i think r79), and it worked. Then I updated, this time I was already directly updated to r480, which I am currently on, but the problem returned. The attached screen is taken under r480. Perhaps I am an isolated case, but I reproduced this problem even after reflashing and updating to recent release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648303/+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 1644975] Re: Resume from disk (swapfile) fails
I'm marking this status to confirmed because this is a re-open of https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/554009 ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1644975 Title: Resume from disk (swapfile) fails Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Well, hibernation with swap file doesn't work while hibernation with swap partition works perfectly fine with the exactly same configuration and hardware. The reason is that when resuming from swap file, initramfs script can't correctly detect the machine are hibernated from the last shut down. And I investigated the issue and found this patch solved https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the hibernate to work. And it isn't applied to the package. I'd like to help this is really applied to the official package. In short, my setup is swapfile inside the system filesystem (LUKS + LVM2 + ext4). Also, I roughly followed this tutorial to prepare this configurartion that: https://ubuntuforums.org/showthread.php?t=1042946 I've opening this bug because the original bug report is closed and getting no response... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1648301] [NEW] phone app doesn't support landscape mode rendering itself unusable in windowed mode
Public bug reported: On a phone running Ubuntu Touch, I would think, phone app is the absolute essential. It should even more so be ready for every user scenario. But it isn't. It does not support landscape mode. When in staged mode, it just simply ignores the landscape mode and forcefully displays itself vertically. Well, at least it can be used, so fine. However, when in windowed mode, you can no longer make use of this. I use my Ubuntu Touch phone mostly in landscape windowed mode. I cannot make phone calls, because I can't even see the "call" button (attached screen from my Meizu MX4 Ubuntu Edition). Now, regardless whether or not it is anticipated by Canonical that users will like me use Ubuntu Touch on the phone in landscape windowed mode, it just should be possible! And it's not a big deal either, make the UI a bit more responsive. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161208_132121324.png" https://bugs.launchpad.net/bugs/1648301/+attachment/4788895/+files/screenshot20161208_132121324.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648301 Title: phone app doesn't support landscape mode rendering itself unusable in windowed mode Status in ubuntu-keyboard package in Ubuntu: New Bug description: On a phone running Ubuntu Touch, I would think, phone app is the absolute essential. It should even more so be ready for every user scenario. But it isn't. It does not support landscape mode. When in staged mode, it just simply ignores the landscape mode and forcefully displays itself vertically. Well, at least it can be used, so fine. However, when in windowed mode, you can no longer make use of this. I use my Ubuntu Touch phone mostly in landscape windowed mode. I cannot make phone calls, because I can't even see the "call" button (attached screen from my Meizu MX4 Ubuntu Edition). Now, regardless whether or not it is anticipated by Canonical that users will like me use Ubuntu Touch on the phone in landscape windowed mode, it just should be possible! And it's not a big deal either, make the UI a bit more responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648301/+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 1648301] Re: phone app doesn't support landscape mode
Also, let me add that the phone app in the windowed mode does not allow user to resize the window down to fit in the landscape mode screen facility. It only allow to grow the window bigger. This is some sort of bad UI/UX decission. ** Summary changed: - phone app doesn't support landscape mode + phone app doesn't support landscape mode rendering itself unusable in windowed mode ** Description changed: - On a phone running Ubuntu Touch, I would thing, phone app is the + On a phone running Ubuntu Touch, I would think, phone app is the absolute essential. It should even more so be ready for every user scenario. But it isn't. It does not support landscape mode. When in staged mode, it just simply ignores the landscape mode and forcefully displays itself vertically. Well, at least it can be used, so fine. However, when in windowed mode, you can no longer make use of this. I use my Ubuntu Touch phone mostly in landscape windowed mode. I cannot make phone calls, because I can't even see the "call" button (attached screen from my Meizu MX4 Ubuntu Edition). Now, regardless whether or not it is anticipated by Canonical that users will like me use Ubuntu Touch on the phone in landscape windowed mode, it just should be possible! And it's not a big deal either, make the UI a bit more responsive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648301 Title: phone app doesn't support landscape mode rendering itself unusable in windowed mode Status in ubuntu-keyboard package in Ubuntu: New Bug description: On a phone running Ubuntu Touch, I would think, phone app is the absolute essential. It should even more so be ready for every user scenario. But it isn't. It does not support landscape mode. When in staged mode, it just simply ignores the landscape mode and forcefully displays itself vertically. Well, at least it can be used, so fine. However, when in windowed mode, you can no longer make use of this. I use my Ubuntu Touch phone mostly in landscape windowed mode. I cannot make phone calls, because I can't even see the "call" button (attached screen from my Meizu MX4 Ubuntu Edition). Now, regardless whether or not it is anticipated by Canonical that users will like me use Ubuntu Touch on the phone in landscape windowed mode, it just should be possible! And it's not a big deal either, make the UI a bit more responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1648301/+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 1648300] [NEW] package initramfs-tools 0.103ubuntu4.4 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: 'lsb_release -rd': Description:Ubuntu 14.04.5 LTS Release:14.04 'apt-cache policy initramfs-tools': initramfs-tools: Установлен: 0.103ubuntu4.4 Кандидат: 0.103ubuntu4.4 Таблица версий: *** 0.103ubuntu4.4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.103ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.4 ProcVersionSignature: Ubuntu 4.4.0-53.74~14.04.1-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Dec 8 08:58:57 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2015-12-24 (349 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.4 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1648300 Title: package initramfs-tools 0.103ubuntu4.4 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in initramfs-tools package in Ubuntu: New Bug description: 'lsb_release -rd': Description: Ubuntu 14.04.5 LTS Release: 14.04 'apt-cache policy initramfs-tools': initramfs-tools: Установлен: 0.103ubuntu4.4 Кандидат: 0.103ubuntu4.4 Таблица версий: *** 0.103ubuntu4.4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.103ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.4 ProcVersionSignature: Ubuntu 4.4.0-53.74~14.04.1-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Dec 8 08:58:57 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2015-12-24 (349 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.4 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1648300/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
@fourdollars, I installed your ppa in #120 above. Unfortunately I could not detect any significant change compared to the latest released versions. Following are my notes from my tests. The test PC has a fresh Ubuntu 16.04 install with all updates. The wifi interface name is wlp1s0 and there is no wired ethernet hw in the PC. First tests done before installing the test ppa. The tests where run in the exact sequence as listed. Action. - Result 1 Initial start of PC. - nm-applet ok 2 Radio HW off-on. - nm-applet not connected, no APs listed 3 service network-manager restart. - after long delay (>30s), connected, APs listed 4 suspend/resume. - not connected, no APs listed 5 service network-manager restart. - nm-applet ok 6 radio HW off-on. after long delay, works ok, APs listed 7 suspend/resume. - after long delay, works ok, APs listed 8 radio hw off-on. - nm-applet ok 9 shut down 10 start PC. - nm-applet ok 11 disable/enable networking (nm-applet menu option). nm-applet shows up/down arrow, no APs 12 listed, connection working 12 service network-manager restart. - nm-applet ok 13 suspend/resume. - nm-applet ok 14 disable/enable networking. - long delay until connecting, APs listed 15 Shut down Started PC Installed fourdollars ppa and verified that "test1" versions had been installed. 16 Restarted PC. - nm-applet ok 17 radio hw off/on. - nm-applet not connected, no APs listed, after very long delay up/down arrows 18 killall nm-applet && nm-applet & exit. - nm-applet ok 19 radio hw off/on. - not connected, no APs listed, after long delay up/down arrows, connection working 20 service network-manager restart. - nm-applet ok 21 suspend/resume. - nm-applet ok 22 disable/enable networking. - nm-applet ok 23 suspend/resume. - nm-applet ok 24 shut down 25 start PC. nm-applet ok 26 suspend/resume. - up/down arrows, no APs listed, connected 27 killall nm-applet && nm-applet & exit. - nm-applet ok 28 suspend/resume. - up/down arrows, no APs, connected 29 service network-manager restart. - nm-applet ok 30 radio hw off/on. - nm-applet ok 31 Restart PC. - nm-applet ok 32 radio hw off/on. - not connected, no APs listed 33 killall nm-applet && nm-applet & exit. - not connected, no APs listed 34 service network-manager restart. - long delay until connected, APs listed 35 radio hw off/on. - nm-applet ok I hope these tests can be of some use... as noted earlier, it appears as if the problem goes away after "sudo service network-manager restart". The "killall nm-applet && nm-applet & exit" will make the nm-applet work ok, but only until next disabling event be it suspend/resume, hw switch off/on or sw disable/enable. In addition to this documented test I have experienced the two problem symptoms (no wifi connection and or incorrect network icon and no APs listed in the nm-applet) on 7 different PCs all with Ubuntu 16.04 with latest updates. All the PCs have different HW (incl wifi) and are of widely different ages. In fact I only have one PC that has not exhibited any of the problems. That PC is running Lubuntu 16.04. It is my experience that the "sudo service network-manager restart" command will correct the problem situation about 70% of the times and when that command is not correcting the problem the "killall nn-applet && nm-applet & exit" command will correct the problem in most of the remaining cases, however there are a few occasions when neither command will correct the situation. Sorry for the long post, but I hope it helps locating the bug(s). -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]
Is there another message in the log saying "mirserver: Selected driver: ..."? -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1645798] Re: No snaps appear in scope on Core 16
Sorry, I don't know what a "BFB result" is. It does show "Apps". I've attached a screenshot. ** Attachment added: "Screenshot from 2016-12-08 14-23-54.png" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+attachment/477/+files/Screenshot%20from%202016-12-08%2014-23-54.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1645798 Title: No snaps appear in scope on Core 16 Status in Canonical System Image: Confirmed Status in Unity8 Session Snap: Confirmed Status in unity-api package in Ubuntu: In Progress Status in unity-scope-click package in Ubuntu: New Bug description: No snaps appear in scope on Core 16 whereas they do appear in unity8 snap on classic To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+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 1631636] Re: xorg
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1631636 Title: xorg Status in xorg package in Ubuntu: Expired Bug description: xorg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 8 14:29:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920] InstallationDate: Installed on 2016-10-03 (5 days ago) InstallationMedia: It MachineType: LENOVO 20041 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=69281983-da29-49b8-b23e-52c97eb2dadb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 29CN40WW(V2.17) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr29CN40WW(V2.17):bd04/13/2011:svnLENOVO:pn20041:pvrLenovoG460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20041 dmi.product.version: Lenovo G460 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Oct 8 14:06:42 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631636/+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 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]
Thanks for pointing that out. So it's probably not a bug in the snap itself but a Mir bug. I have seen this happen before in other bug reports (spurious 'Unknown command line options: --vt 1' even when the mesa-kms driver is present), but will need to find those old bug reports... -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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)
Another interesting idea: If we implement a headless driver (discussed today) with GL support (OSMesa) then that gets us halfway to resolving this bug. Then all that's required is to replace the headless output with a linear framebuffer device (which fbdev is?). -- 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 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]
** Summary changed: - Running Mir-Server snap, gives error! (localhost snap[4768]: Unknown command line options: --vt 1) + Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
The 2 i915 patches can't be backported to 3.19 kernel, so I use another way to archive the same function. The test kernel could be found here, I'll try to see if we could find a machine here to verify it. http://people.canonical.com/~acelan/bugs/lp1646537/ ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress -- 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/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1648292] Re: Running Mir-Server snap, gives error! (localhost snap[4768]: Unknown command line options: --vt 1)
Here before that error lists Dec 8 03:35:39 localhost snap[2590]: [2016-12-08 03:35:39.561979] mirplatform: Found graphics driver: mir:mesa-kms (version 0.24.1) Dec 8 03:35:39 localhost snap[2590]: [2016-12-08 03:35:39.562510] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.24.1) -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1648292] Re: Running Mir-Server snap, gives error! (localhost snap[4768]: Unknown command line options: --vt 1)
Incidentally in future I think the VT option should be server-wide. It's not graphics-driver specific, however some kernels don't have VT support (ChromeOS??) so we need to be aware of that too. ** Tags added: vt -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1648292] Re: Running Mir-Server snap, gives error!
The error 'Unknown command line options: --vt 1' means you don't have (or aren't using?) the mesa-kms graphics driver needed to interpret that option. I don't know if the mir-server snap has correctly provided this. ** Also affects: mir Importance: Undecided Status: New ** Summary changed: - Running Mir-Server snap, gives error! + Running Mir-Server snap, gives error! (localhost snap[4768]: Unknown command line options: --vt 1) -- 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/1648292 Title: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1] Status in Mir: New Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1648292/+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 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Luke Yelavich (themuso) ** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Xenial) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Xenial) Assignee: (unassigned) => Luke Yelavich (themuso) -- 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/1641954 Title: Output switches from HDMI speakers to internal speakers on DPMS off Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Xenial: In Progress Bug description: PulseAudio 8.0 includes a well-known user-experience regression: Its new auto-routing algorithm tries to switch to another output, as soon as the active output gets disconnected. This leads to the following bad user experience: (1) Alice listens to music on her speakers, which are connected to the screen, which is connected through HDMI to the computer. (2) Alice leaves the computer, the screen gets suspended (DPMS off). (3) PulseAudio sees that the HDMI output got disconnected (although only for a short interval) and switches to internal speaker. (4) Alice returns to the computer but finds that the music is now playing through the internal speakers. (5) Alice can switch the output to the HDMI speakers manually, but the above user experience bug will reoccur when she leaves the computer again. This is a well-known upstream bug that was fixed in PulseAudio 9.0. Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is desirable to backport this fix to PulseAudio 8.0, so that all LTS users have better experience. Upstream said they would not do this and that I should report this to Ubuntu directly. Other information: * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946 * Fix 1: https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09 * Fix 2: https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+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 1648292] [NEW] Running Mir-Server snap, gives error!
Public bug reported: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 ** 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/1648292 Title: Running Mir-Server snap, gives error! Status in mir package in Ubuntu: New Bug description: I don't know, if this is right place! Trying to run mir-server gives error: Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1 Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Main process exited, code=exited, status=1/FAILURE Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Unit entered failed state. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Failed with result 'exit-code'. Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: Service hold-off time over, scheduling restart. Running on Raspberry pi 2, Ubuntu snappy core! runned lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1648292/+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 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
Incomplete. I can still reproduce a freeze using the instructions in the description but it also looks like those instructions are wrong. Because if you do the same in X you will fine the Scores dialog is modal and is meant to make the main window unresponsive to input. That said, I also remember anpok saying he found and fixed a reason for bugs like this in GTK. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: In Progress => Incomplete -- 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/1445543 Title: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze Status in GTK+: New Status in Mir: Invalid Status in Ubuntu: Incomplete Bug description: GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly. Example: $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input. Other dialogs (e.g. "About") work fine. From the Mir side there's no obvious difference between these windows. In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. That shows most of the Mir stack is working correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1445543/+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 1445542] Re: Using the Mir backend, secondary windows of GTK apps open behind the primary window
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Incomplete -- 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/1445542 Title: Using the Mir backend, secondary windows of GTK apps open behind the primary window Status in Mir: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Using the Mir backend, secondary windows of GTK apps open behind the primary window. This is odd because Mir's default behaviour is to put any new surface on top. e.g. Remmina (after you apply the fix for bug 1444132) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445542/+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 1627750] Re: gnome-terminal displays input in wrong window
Could we generalise and merge this with bug 1625397? -- 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/1627750 Title: gnome-terminal displays input in wrong window Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: New Bug description: $ miral-server --startup gnome-terminal Go "File=>Open Terminal" to create a second window Type in the new window. Expect: typing to appear in the new window Actual: typing appears in the original window Focus *is* on the new window as can be verified by Alt-F4, which correctly closes the new window. To manage notifications about this bug go to: https://bugs.launchpad.net/miral/+bug/1627750/+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 1633046] Re: Pressing play/pause hotkey hangs U8 session
** Changed in: media-hub (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1633046 Title: Pressing play/pause hotkey hangs U8 session Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Log in to a U8 session in 16.10. Press the play/pause hotkey. Note that the session is now hung. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1633046/+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 1633046] Re: Pressing play/pause hotkey hangs U8 session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: media-hub (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/1633046 Title: Pressing play/pause hotkey hangs U8 session Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Log in to a U8 session in 16.10. Press the play/pause hotkey. Note that the session is now hung. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1633046/+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 1648167] Re: Touch window controls dismiss the touch overlay instead
** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Triaged -- 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/1648167 Title: Touch window controls dismiss the touch overlay instead Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Steps: * three-finger-tap a window to get the window controls * tap on one of the window control buttons (close/min/max) Expected: * the action is taken Current: * touch controls are dismissed instead No autotest for this, looks like. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648167/+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 1648168] Re: Launcher quicklists are blurry
There's a remote possibility this could be related to bug 1603296, assuming bug 1603296 is also related to texture misalignment. ** Tags added: unity8-desktop visual-quality ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1648168 Title: Launcher quicklists are blurry Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Steps: * right-click on a launcher item Expected: * text in the quicklist is sharp Current: * text is blurred, likely not pixel-aligned. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648168/+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 1369493] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
The same bug for me. Logs: Setting up procps (2:3.3.10-4ubuntu2.3) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1369493 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in sysvinit package in Ubuntu: Confirmed Bug description: Upgrading xorg on Utopic (booted with upstart), the install dialog-box have displayed this warning: Setting up x11-common (1:7.7+7ubuntu2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults * Setting up X socket directories...[ OK ] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: sysv-rc 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 15 12:12:53 2014 PackageArchitecture: all SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1369493/+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 1648267] Re: Regression with Zesty binutils building u-boot
Prior to this commit linking works: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;a=commit;h=1a9ccd70f9a7 "Fix the linker so that it will not silently generate ELF binaries with invalid program headers. Fix readelf to report such invalid binaries." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1648267 Title: Regression with Zesty binutils building u-boot Status in binutils package in Ubuntu: New Bug description: With GNU ld (GNU Binutils for Ubuntu) 2.27.51.20161202 (arm-linux- gnueabi), building my u-boot target fails: LD u-boot arm-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N arm-linux-gnueabi-ld.bfd: final link failed: Bad value Makefile:1187: recipe for target 'u-boot' failed If I instad use the GNU ld (2.27-9ubuntu1+9) 2.27 (arm-none-eabi), the same code links without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1648267/+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 1648267] [NEW] Regression with Zesty binutils building u-boot
Public bug reported: With GNU ld (GNU Binutils for Ubuntu) 2.27.51.20161202 (arm-linux- gnueabi), building my u-boot target fails: LD u-boot arm-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N arm-linux-gnueabi-ld.bfd: final link failed: Bad value Makefile:1187: recipe for target 'u-boot' failed If I instad use the GNU ld (2.27-9ubuntu1+9) 2.27 (arm-none-eabi), the same code links without issue. ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1648267 Title: Regression with Zesty binutils building u-boot Status in binutils package in Ubuntu: New Bug description: With GNU ld (GNU Binutils for Ubuntu) 2.27.51.20161202 (arm-linux- gnueabi), building my u-boot target fails: LD u-boot arm-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N arm-linux-gnueabi-ld.bfd: final link failed: Bad value Makefile:1187: recipe for target 'u-boot' failed If I instad use the GNU ld (2.27-9ubuntu1+9) 2.27 (arm-none-eabi), the same code links without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1648267/+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 1648263] [NEW] package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: What i do? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-chardet 2.3.0-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Wed Dec 7 21:27:50 2016 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: chardet Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chardet (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 chardet in Ubuntu. https://bugs.launchpad.net/bugs/1648263 Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in chardet package in Ubuntu: New Bug description: What i do? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-chardet 2.3.0-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Wed Dec 7 21:27:50 2016 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: chardet Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1648263/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
** Branch linked: lp:ubuntu/trusty-security/libav -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in libav: Unknown Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Invalid Status in firefox source package in Precise: New Status in libav source package in Precise: Confirmed Status in firefox source package in Trusty: New Status in libav source package in Trusty: Fix Released Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/1643467/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
This bug was fixed in the package libav - 6:9.20-0ubuntu0.14.04.1 --- libav (6:9.20-0ubuntu0.14.04.1) trusty-security; urgency=medium * SECURITY UPDATE: Updated to 9.20 to fix various crashes with invalid-free, corrupted double-linked list or out-of-bounds read (LP: #1643467) - No CVE number -- Marc Deslauriers Wed, 07 Dec 2016 15:36:50 -0500 ** Changed in: libav (Ubuntu Trusty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in libav: Unknown Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Invalid Status in firefox source package in Precise: New Status in libav source package in Precise: Confirmed Status in firefox source package in Trusty: New Status in libav source package in Trusty: Fix Released Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/1643467/+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 1648248] [NEW] package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgl1-mesa-dri:i386 12.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 8 01:53:09 2016 DistUpgraded: 2016-12-08 01:37:37,620 DEBUG running apport_crash() DistroCodename: yakkety DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:i386:12.0.3-1ubuntu2 Setting up dbus-user-session (1.10.10-1ubuntu1.1) ... dpkg: error processing package libgl1-mesa-dri:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. RV730 XT [Radeon HD 4670] [1787:2268] InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=c93d3af3-5cd3-433f-abdc-c5fe4e0a0150 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.2.15 SourcePackage: mesa Title: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to yakkety on 2016-12-07 (0 days ago) dmi.bios.date: 05/14/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-MA770T-ES3 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.:bvrF3:bd05/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA770T-ES3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.drirc: 2016-10-06T11:58:42 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Dec 8 01:50:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package compiz-0.9 i386 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1648248 Title: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgl1-mesa-dri:i386 12.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 8 01:53:09 2016 DistUpgraded: 2016-12-08 01:37:37,620 DEBUG running apport_crash() DistroCodename: yakkety DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:i386:12.0.3-1ubuntu2 Setting up dbus-user-session (1.10.10-1ubuntu1.1) ... dpkg: error processing package libgl1-mesa-dri:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before atte
[Touch-packages] [Bug 1648248] Re: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1648248 Title: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgl1-mesa-dri:i386 12.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 8 01:53:09 2016 DistUpgraded: 2016-12-08 01:37:37,620 DEBUG running apport_crash() DistroCodename: yakkety DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:i386:12.0.3-1ubuntu2 Setting up dbus-user-session (1.10.10-1ubuntu1.1) ... dpkg: error processing package libgl1-mesa-dri:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. RV730 XT [Radeon HD 4670] [1787:2268] InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=c93d3af3-5cd3-433f-abdc-c5fe4e0a0150 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.2.15 SourcePackage: mesa Title: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to yakkety on 2016-12-07 (0 days ago) dmi.bios.date: 05/14/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-MA770T-ES3 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.:bvrF3:bd05/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA770T-ES3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.drirc: 2016-10-06T11:58:42 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Dec 8 01:50:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1648248/+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 1645798] Re: No snaps appear in scope on Core 16
@michi Is there at least the BFB result for the store? Does it show "Apps" at the top of the dash? Or is everything totally blank? If answers are "yes, yes, no" then the result set is indeed just empty for some reason. If answers are "no, yes, no" then either unity-scope-snappy is not installed and it's getting no results, or it's crashing/failing to complete the run. If answers are "no, no, yes" then the system thinks the scope isn't available and it's not being run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1645798 Title: No snaps appear in scope on Core 16 Status in Canonical System Image: Confirmed Status in Unity8 Session Snap: Confirmed Status in unity-api package in Ubuntu: In Progress Status in unity-scope-click package in Ubuntu: New Bug description: No snaps appear in scope on Core 16 whereas they do appear in unity8 snap on classic To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+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 1648240] Re: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied
** Tags removed: need-duplicate-check -- 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/1648240 Title: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied Status in systemd package in Ubuntu: New Bug description: Ran do-release-upgrade on a Windows Insider build that had an up-to- date install of Bash on Windows from Anniversary Edition installed. I had done this upgrade on another Windows 10 Insider machine, about a month ago, without these errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0 (not installed) Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Dec 7 13:20:02 2016 Dmesg: DpkgTerminalLog: Preparing to unpack .../libsystemd0_229-4ubuntu12_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu12) ... dpkg: error processing archive /var/cache/apt/archives/libsystemd0_229-4ubuntu12_amd64.deb (--unpack): unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied DuplicateSignature: package:libsystemd0:(not installed):unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied ErrorMessage: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: systemd Title: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied UpgradeStatus: Upgraded to xenial on 2016-12-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648240/+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 1648240] [NEW] package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied
Public bug reported: Ran do-release-upgrade on a Windows Insider build that had an up-to-date install of Bash on Windows from Anniversary Edition installed. I had done this upgrade on another Windows 10 Insider machine, about a month ago, without these errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0 (not installed) Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Dec 7 13:20:02 2016 Dmesg: DpkgTerminalLog: Preparing to unpack .../libsystemd0_229-4ubuntu12_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu12) ... dpkg: error processing archive /var/cache/apt/archives/libsystemd0_229-4ubuntu12_amd64.deb (--unpack): unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied DuplicateSignature: package:libsystemd0:(not installed):unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied ErrorMessage: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: systemd Title: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied UpgradeStatus: Upgraded to xenial on 2016-12-07 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package uec-images xenial -- 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/1648240 Title: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied Status in systemd package in Ubuntu: New Bug description: Ran do-release-upgrade on a Windows Insider build that had an up-to- date install of Bash on Windows from Anniversary Edition installed. I had done this upgrade on another Windows 10 Insider machine, about a month ago, without these errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0 (not installed) Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Dec 7 13:20:02 2016 Dmesg: DpkgTerminalLog: Preparing to unpack .../libsystemd0_229-4ubuntu12_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu12) ... dpkg: error processing archive /var/cache/apt/archives/libsystemd0_229-4ubuntu12_amd64.deb (--unpack): unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied DuplicateSignature: package:libsystemd0:(not installed):unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied ErrorMessage: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: systemd Title: package libsystemd0 (not installed) failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/libsystemd.so.0.14.0.dpkg-new': Permission denied UpgradeStatus: Upgraded to xenial on 2016-12-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648240/+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 1648224] Re: [krilin] Dialer-app surface freezes during outgoing calls
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1648224 Title: [krilin] Dialer-app surface freezes during outgoing calls Status in dialer-app package in Ubuntu: Confirmed Bug description: My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu 15.04 OTA 14 (stable channel). The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1. 1. What I do When I do an outgoing call. 2. What I expect The surface of the app continues to work, I can hang up, put on the microphone etc. 3. What happens The surface of the dialer-app freezes, the call goes on. But I cannot hang up, turn on the microphone etc. The only workaround is: - close dialer app in Task Manager - Open other app. - Re-open dialer app via the green bar on the top. - Re-opened dialer app has working surface, so I can hang up, turn on the microphone etc. The bug did already appear in OTA13 and is still present now in OTA 14. The bug does not occure when I accept an incoming call. The bus is reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1648224/+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 1370629] Re: 51-android.rules
Install android-sdk-platform-tools-common The 'adb' package in Ubuntu 17.04 Alpha now recommends that package so this will be more obvious in the future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1370629 Title: 51-android.rules Status in android-platform-system-core package in Ubuntu: Fix Released Status in android-tools package in Ubuntu: Confirmed Bug description: i wish you can add the file 51-android.rules to the project,according http://developer.android.com/tools/device.html. you can find the file 51-android.rules in my project. https://github.com/snowdream/51-android To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1370629/+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 1370629] Re: 51-android.rules
I forgot to mention that android-sdk-platform-tools-common includes the udev rules in Ubuntu 16.04 LTS and newer. ** Changed in: android-platform-system-core (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1370629 Title: 51-android.rules Status in android-platform-system-core package in Ubuntu: Fix Released Status in android-tools package in Ubuntu: Confirmed Bug description: i wish you can add the file 51-android.rules to the project,according http://developer.android.com/tools/device.html. you can find the file 51-android.rules in my project. https://github.com/snowdream/51-android To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1370629/+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 1648237] Re: update-manager and unattended-upgrades failure
Also: https://ubuntuforums.org/showthread.php?t=2330407 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1648237 Title: update-manager and unattended-upgrades failure Status in ubuntu-mate: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: A series of issues about update-manager and unattended-upgrade. I have set the system to: - automatically check for update daily - when there are security updates, download and install them automatically - when there are other updates, display them immediately. What occurs: (1) unattended-upgrade runs on boot but systematically its log states every day that: "No packages found that can be upgraded unattended and no pending auto-removals" even where there are security updates to install. (2) update-manager appears not to refresh the cache automatically after boot. (3) when the cache is manually refreshed so there are updates, update- manager runs after a subsequent boot and appears in the panel. However clicking on it leads it to simply disappear. (4) update-manager will not launch from the menu. When launched from a terminal it runs correctly, refreshes the cache and will install updates. No crash reports, nothing obvious in log files. Ubuntu-MATE 16.10 clean install, fully updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1648237/+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 1648237] Re: update-manager and unattended-upgrades failure
Other similar reports: https://ubuntuforums.org/showthread.php?t=2339387 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1648237 Title: update-manager and unattended-upgrades failure Status in ubuntu-mate: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: A series of issues about update-manager and unattended-upgrade. I have set the system to: - automatically check for update daily - when there are security updates, download and install them automatically - when there are other updates, display them immediately. What occurs: (1) unattended-upgrade runs on boot but systematically its log states every day that: "No packages found that can be upgraded unattended and no pending auto-removals" even where there are security updates to install. (2) update-manager appears not to refresh the cache automatically after boot. (3) when the cache is manually refreshed so there are updates, update- manager runs after a subsequent boot and appears in the panel. However clicking on it leads it to simply disappear. (4) update-manager will not launch from the menu. When launched from a terminal it runs correctly, refreshes the cache and will install updates. No crash reports, nothing obvious in log files. Ubuntu-MATE 16.10 clean install, fully updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1648237/+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 1648237] [NEW] update-manager and unattended-upgrades failure
Public bug reported: A series of issues about update-manager and unattended-upgrade. I have set the system to: - automatically check for update daily - when there are security updates, download and install them automatically - when there are other updates, display them immediately. What occurs: (1) unattended-upgrade runs on boot but systematically its log states every day that: "No packages found that can be upgraded unattended and no pending auto-removals" even where there are security updates to install. (2) update-manager appears not to refresh the cache automatically after boot. (3) when the cache is manually refreshed so there are updates, update- manager runs after a subsequent boot and appears in the panel. However clicking on it leads it to simply disappear. (4) update-manager will not launch from the menu. When launched from a terminal it runs correctly, refreshes the cache and will install updates. No crash reports, nothing obvious in log files. Ubuntu-MATE 16.10 clean install, fully updated. ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Summary changed: - update-manager and unattended-upgrade failure + update-manager and unattended-upgrades failure ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1648237 Title: update-manager and unattended-upgrades failure Status in ubuntu-mate: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: A series of issues about update-manager and unattended-upgrade. I have set the system to: - automatically check for update daily - when there are security updates, download and install them automatically - when there are other updates, display them immediately. What occurs: (1) unattended-upgrade runs on boot but systematically its log states every day that: "No packages found that can be upgraded unattended and no pending auto-removals" even where there are security updates to install. (2) update-manager appears not to refresh the cache automatically after boot. (3) when the cache is manually refreshed so there are updates, update- manager runs after a subsequent boot and appears in the panel. However clicking on it leads it to simply disappear. (4) update-manager will not launch from the menu. When launched from a terminal it runs correctly, refreshes the cache and will install updates. No crash reports, nothing obvious in log files. Ubuntu-MATE 16.10 clean install, fully updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1648237/+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 1647133] Re: dns=dnsmasq does not work any more
Ah, so you didn't have resolvconf installed (and therefore also not ubuntu-minimal), that's a good data point, thank you! This should be part of this bug -- NM should get along with this better. Do you see the search domain in "systemd-resolve --status"? -- 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/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR
** Changed in: lightdm (Ubuntu) Status: New => Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- 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/1648107 Title: $XAUTHORITY should move into $XDG_RUNTIME_DIR Status in lightdm package in Ubuntu: Triaged Bug description: Historically, the X authority file was placed into $HOME/.Xauthority such that X11 clients on remote servers could access it in environments in which $HOME is located on a network file system. Today, this practice has become an anachronism that causes far more problems than it solves: a) Remote X11 clients are typically started today via "ssh -X", which emulates its own X11 server port $DISPLAY and therefore always creates its own X authority file entry on the remote server. Therefore, there is no longer any practical benefit from having the X authority file located in $HOME. b) If $HOME is on a network file system that implements "root squash", then commands such as "sudo xterm" or "sudo wireshark" won't work to start an X client with root privileges, as root is not able to read ~/.Xauthority via NFS. :-( c) If $HOME is on a network file system with Kerberos authentication, then users can easily get locked out by their screensavers once the Kerberos ticket expires. This is because some screen lockers (e.g., gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome- screensaver/gnome-screensaver-dialog) in order to ask the user of a locked screen for their password. Such a tool needs to access $XAUTHORITY right before it can display the password prompt, which will fail if the user's Kerberos ticket has expired (e.g. because a machine was suspended for 24 hours and therefore the ticket was not refreshed automatically on time). Without the ability to ask for a password, the screensaver then cannot call pam_krb5 to renew the user's Kerberos ticket, and the user remains locked out in a deadlock situation. :-( Both b) and c) are regular reasons for support requests in educational/corporate Linux environments with $HOME on Kerberized NFS. The solution is simple. Instead of $HOME/.Xauthority, just use in future $XDG_RUNTIME_DIR/xauthority as the location of the X authority file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER might be a suitable fallback option.) According to https://standards.freedesktop.org/basedir-spec/basedir- spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for holding the X authority file: it is always located in a local tmpfs filesystem, guaranteed to be accessible only to the current user, and will be wiped when the user has closed all sessions. On modern Linux systems, pam_systemd usually creates XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end. (Note that according to https://standards.freedesktop.org/basedir-spec /basedir-spec-latest.html you should set the "sticky bit" on any files created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.) Feature request: please provide an option for LightDM to do the equivalent of export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority chmod +t $XAUTHORITY and encourage Linux distribution maintainers to set this option by default, such that ~/.Xauthority is no longer used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+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 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
Status in systemd:
New
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces
in their model or serial strings result in incorrect symlinks, e.g. if the
model string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
it creates:
/dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
/dev/Corp -> nvme0n1
/dev/NVMe -> nvme0n1
/dev/drive_SERIAL -> nvme0n1
This is because of the way udev handles the SYMLINK value strings; by
default, it does not do any whitespace replacement. To enable
whitespace replacement of a symlink value, the rule must also include
OPTIONS+="string_escape=replace". This is done for 'md' and 'dm'
devices in their rules. However, there are no rules that actually
want to specify multiple symlinks, and defaulting to not replacing
whitespace makes no sense; instead, the default should be to replace
all whitespace in each symlink value, unless the rule explicitly
specifies OPTIONS+="string_escape=none".
[Test Case]
This assumes using udev with the patch from bug 1642903.
Without this patch, when using a NVMe drive that contains spaces in
its model and/or serial strings, check the /dev/disk/by-id/ directory.
It should contain a partially-correct symlink to the NVMe drive, with
the name up to the first space. All following space-separated parts
of the mode/serial string should have symlinks in the /dev/ directory.
This is the incorrect behavior.
With this patch, check the /dev/disk/by-id/ directory. It should
contain a fully-correct symlink to the NVMe drive, and no part of the
drive's model/serial number string should be a link in the /dev
directory.
An example of the correct/incorrect naming is in the Impact section.
There should be no other changes to any of the symlinks under /dev
before and after this patch. Typical locations for symlinks are
/dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
/dev/disk/by-label/
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This is also tracked with upstream systemd (udev) bug 4833:
https://github.com/systemd/systemd/issues/4833
Also note, this can be worked around in individual rules ONLY (i.e.
not fixed for all rules) by appending OPTIONS+="string_escape=replace"
to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:
KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
ENV{ID_SERIAL_SHORT}=="?*",
ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
/by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647485/+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 1648224] [NEW] [krilin] Dialer-app surface freezes during outgoing calls
Public bug reported: My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu 15.04 OTA 14 (stable channel). The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1. 1. What I do When I do an outgoing call. 2. What I expect The surface of the app continues to work, I can hang up, put on the microphone etc. 3. What happens The surface of the dialer-app freezes, the call goes on. But I cannot hang up, turn on the microphone etc. The only workaround is: - close dialer app in Task Manager - Open other app. - Re-open dialer app via the green bar on the top. - Re-opened dialer app has working surface, so I can hang up, turn on the microphone etc. The bug did already appear in OTA13 and is still present now in OTA 14. The bug does not occure when I accept an incoming call. The bus is reproducible. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1648224 Title: [krilin] Dialer-app surface freezes during outgoing calls Status in dialer-app package in Ubuntu: New Bug description: My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu 15.04 OTA 14 (stable channel). The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1. 1. What I do When I do an outgoing call. 2. What I expect The surface of the app continues to work, I can hang up, put on the microphone etc. 3. What happens The surface of the dialer-app freezes, the call goes on. But I cannot hang up, turn on the microphone etc. The only workaround is: - close dialer app in Task Manager - Open other app. - Re-open dialer app via the green bar on the top. - Re-opened dialer app has working surface, so I can hang up, turn on the microphone etc. The bug did already appear in OTA13 and is still present now in OTA 14. The bug does not occure when I accept an incoming call. The bus is reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1648224/+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 1105493] Re: network manager runs dnsmasq as user nobody
nivlac, 'nobody' is a poor choice: the intended use of user 'nobody' (and group 'nogroup') is for NFS. If daemons start using 'nobody' (or 'nogroup') then they can interfere with the proper operation of NFS or other daemons that also use 'nobody' (or 'nogroup'). Thanks -- 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/1105493 Title: network manager runs dnsmasq as user nobody Status in network-manager package in Ubuntu: Confirmed Bug description: Network Manager starts dnsmasq to provide better performing DNS service to the end user; however, it starts dnsmasq as user nobody: $ ps auwwx | grep [d]nsmasq nobody 993 0.0 0.1 33072 1120 ?S12:06 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Generally it's bad form from a security perspective to run daemons as user nobody because a vulnerability in one daemon will possibly allow it, when compromised, to interfere with another daemon that is also running as nobody. The preferred solution is to run it under a service-specific system user. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jan 25 14:17:36 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-25 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 10.0.2.2 dev eth0 proto static 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 16065df63-d4a5-4426-bf03-4b938adcdf28 802-3-ethernet1359152173 Fri 25 Jan 2013 02:16:13 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1105493/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
** Bug watch added: bugzilla.libav.org #939 http://bugzilla.libav.org/show_bug.cgi?id=939 ** Also affects: firefox via http://bugzilla.libav.org/show_bug.cgi?id=939 Importance: Unknown Status: Unknown ** No longer affects: firefox ** Also affects: libav via http://bugzilla.libav.org/show_bug.cgi?id=939 Importance: Unknown Status: Unknown ** Also affects: firefox (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: libav (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libav (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: libav (Ubuntu Precise) Status: New => Confirmed ** Changed in: libav (Ubuntu Trusty) Status: New => Confirmed ** Changed in: libav (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in libav: Unknown Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Invalid Status in firefox source package in Precise: New Status in libav source package in Precise: Confirmed Status in firefox source package in Trusty: New Status in libav source package in Trusty: Confirmed Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/1643467/+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 1589149] Re: the two Hotspots buttons seem to disagree
My experience with my mx4 is that most of the time the hotspot works after a couple of attempts (almost always fails on first attempt) but the last months it rarely show any indicator. It also, as stated earlier by others in this thread, often stays active after turned off. For me, the hotspot also seems to break wifi and only a reboot helps. Flight mode also seems to break from time to time and it has only happened for me after using the hotspot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1589149 Title: the two Hotspots buttons seem to disagree Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: When i try to activate the hotspot using the menu that you can make appear from above (the black-background one) it seems not to work (no hotspot and no hotspot symbol on the top menu appearing). If I open setting->hotspot, there the hotspot button is deactivated (not green) while the hotspot button in the black menu is green. It seems the button in the Settings if activated can really make the hotspot work (and make the hotspot button in the black menu green) but the hotspot button in the black menu seems to just do nothing (except cutting wifi) On the meizu 4 with ota 11. I think the problem came with ota 11. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589149/+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 1594938] Re: [arale] Hotspot activation doesn't always work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work Status in Canonical System Image: New Status in network-manager package in Ubuntu: Confirmed Bug description: Although the hotspot logic was vastly improved in OTA11, there are still intermittent issues with enabling hotspot on arale. On a freshly flashed phone running rc-proposed / 356, when I first attempt to setup a hotspot, when I click the "Start" button, the spinner shows up and the hotspot never actually starts ( see attached screenshot ). I was then able to cancel the dialog and enable hotspot via the toggle switch. The correct icon was shown on the panel, and the hotspot was visible from other devices. Note, the only change I made to the configuration was to change the default password to "12345678" ( the minimum length WPA-PSK passphrase ). Here's my image details: current build number: 356 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-21 14:39:34 version version: 356 version ubuntu: 20160621 version device: 20160526-af18709 version custom: 20160504-975-19-6 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
I found ( http://askubuntu.com/a/856322/66509 ) PPA with newer libav (version 11.2-1ppa1) for Precise: sudo add-apt-repository ppa:itachi-san/ffmpeg sudo apt-get update sudo apt-get install libav-tools libavcodec56 Is it possible to make SRU and include it to Precise main repository? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Triaged Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+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 1647696] Re: the app switcher and the app drawer are very laggy on MX4
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/1647696 Title: the app switcher and the app drawer are very laggy on MX4 Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: the app switcher and the app drawer are very laggy on MX4 i am not sure how to view the actual FPS but they feel very laggy mx4/rc-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647696/+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 1633046] Re: Pressing play/pause hotkey hangs U8 session
@Will: Are you sure media-hub is running in this session and actually being utilized? Check in ~/.cache/upstart/media-hub.log (this log may be located elsewhere in Unity8 session on the desktop, I'm not entirely sure). -- 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/1633046 Title: Pressing play/pause hotkey hangs U8 session Status in media-hub package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: Log in to a U8 session in 16.10. Press the play/pause hotkey. Note that the session is now hung. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1633046/+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 1648194] [NEW] Opening a 11th window all the windows chrash
Public bug reported: Then when I relaunch the browser all the ten windows are reopened. How to reproduce the bug: Open the browser, then open the right bar and press new window. In the new window press the new window button. Continue in that way until in the 10th window you press new window, and all chrashes. Relaunch the browser and you will see all the ten window again opened. I'm on bq E5, rc-proposed. Thanks for all your work and for the new windows functionality! ;) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1648194 Title: Opening a 11th window all the windows chrash Status in webbrowser-app package in Ubuntu: New Bug description: Then when I relaunch the browser all the ten windows are reopened. How to reproduce the bug: Open the browser, then open the right bar and press new window. In the new window press the new window button. Continue in that way until in the 10th window you press new window, and all chrashes. Relaunch the browser and you will see all the ten window again opened. I'm on bq E5, rc-proposed. Thanks for all your work and for the new windows functionality! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1648194/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
I have prepared a PPA containing a new repowerd with a potential fix for the issue here: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2276 IMPORTANT CAVEAT: The changes are experimental. Only try the PPA packages on a development device, not one you care about keeping stable. You may need to reflash a clean image if things go very wrong. To try the updated packages follow the instructions from the link below: https://wiki.ubuntu.com/Process/Merges/TestPlans/repowerd Let me know if/how the fix works for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Fix Committed Status in repowerd: In Progress Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1648169] Re: Close button in switcher is tiny
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/1648169 Title: Close button in switcher is tiny Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: Steps: * right-edge to switcher * hover over a closable surface (not Scopes) Expected: * close button is appropriately sized Current: * tiny close button ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1648169/+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 1647133] Re: dns=dnsmasq does not work any more
One possible issue is the contents of the /etc/resolv.conf (or actually /run/resolvconf/resolv.conf). With NM 1.4.2-2ubuntu4 the /etc/resolv.conf is: nameserver 127.0.0.53 But with NM 1.4.2-2ubuntu3 it is: search dhcp.inet.fi nameserver 127.0.1.1 So where did the line "search dhcp.inet.fi" go? I think this needs to be there in order to a fully working network. -- 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/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1648183] [NEW] Crackling and popping sound when using headphones
Public bug reported: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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/ListH
[Touch-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
The bug is cause by a dnsmasq bug described in the following bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 and is fixed by applying the following path to dnsmasq (2.76): http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b ** Bug watch added: Red Hat Bugzilla #1367772 https://bugzilla.redhat.com/show_bug.cgi?id=1367772 -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in dnsmasq: New Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1644098/+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 1647133] Re: dns=dnsmasq does not work any more
And a little more info: "/etc/NetworkManager/NetworkManager.conf" [main] plugins=ifupdown,keyfile [ifupdown] managed=false "/etc/resolv.conf" # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 -- 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/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1647133] Re: dns=dnsmasq does not work any more
Martin, I installed the package resolvconf. Now the command gives this: "systemctl status resolvconf" ● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2016-12-07 19:23:29 EET; 6min ago Docs: man:resolvconf(8) Main PID: 322 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/resolvconf.service However, there is still something wrong with my network. Certain web pages (mainly in Finland) do not work at all. Now the link /etc/resolv.conf points to ../run/resolvconf/resolv.conf -- 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/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
I don't know whether it is significant but I notice in syslog that for the second connection to the vpn I see the additional line systemd-resolved[1001]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.1.1. and I notice that a similar message is present in the log in comment #1 -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in dnsmasq: New Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1644098/+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 1648173] [NEW] App drawer stays on screen after activating launcher item
Public bug reported: In https://bileto.ubuntu.com/#/ticket/2150 - after fixing bug #1591311 Steps: * press Super+A or long-left-swipe to invoke the app drawer * click on an item in launcher Expected: * drawer is closed, as it is when you launch an item from the drawer Current: * drawer stays on, likely covering part of the activated window ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1648173 Title: App drawer stays on screen after activating launcher item Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: In https://bileto.ubuntu.com/#/ticket/2150 - after fixing bug #1591311 Steps: * press Super+A or long-left-swipe to invoke the app drawer * click on an item in launcher Expected: * drawer is closed, as it is when you launch an item from the drawer Current: * drawer stays on, likely covering part of the activated window ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1648173/+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 1574347] Re: [SRU] Re-read the link type if the name changed
** Changed in: network-manager (Ubuntu) Assignee: jay patel (jay-patel736) => ImhotepOsumare157 (imhoteposumare157) -- 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/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet [Testcase] 1. Boot the system. It should include a wireless device. 2. In a terminal, run 'nmcli dev'. 3. In the correct case, the line for the wireless device should read "wifi" under the TYPE column. In a failure case, it will read "ethernet". After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. --- Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1541351] Re: Bluetooth keyboards which aren't actually keyboards suppress the on-screen keyboard.
*** This bug is a duplicate of bug 1521518 *** https://bugs.launchpad.net/bugs/1521518 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/1541351 Title: Bluetooth keyboards which aren't actually keyboards suppress the on- screen keyboard. Status in unity8 package in Ubuntu: Confirmed Bug description: Associate with your phone a bluetooth button (selfie button) such as this thing:- http://www.amazon.co.uk/Yousave-Accessories-Selfie-Stick- Telescopic/dp/B00QFC6NE4 Here it is connected:- http://people.canonical.com/~alan/screenshots/device-2016-02-03-114940.png Once connected, it's impossible to bring up the OSK in any app or scope. Switch off the bluetooth device, or disconnect it, and the OSK magically works again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1541351/+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 1648168] [NEW] Launcher quicklists are blurry
Public bug reported: Steps: * right-click on a launcher item Expected: * text in the quicklist is sharp Current: * text is blurred, likely not pixel-aligned. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) ** Affects: unity8 (Ubuntu) Importance: High Status: Triaged ** Tags: amd64 apport-bug third-party-packages zesty ** Attachment added: "screenshot20161207_181339831.png" https://bugs.launchpad.net/bugs/1648168/+attachment/4788662/+files/screenshot20161207_181339831.png ** Changed in: unity8 (Ubuntu) Assignee: Lukáš Tinkl (lukas-kde) => (unassigned) -- 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/1648168 Title: Launcher quicklists are blurry Status in unity8 package in Ubuntu: Triaged Bug description: Steps: * right-click on a launcher item Expected: * text in the quicklist is sharp Current: * text is blurred, likely not pixel-aligned. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1648168/+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 1648167] [NEW] Touch window controls dismiss the touch overlay instead
Public bug reported: Steps: * three-finger-tap a window to get the window controls * tap on one of the window control buttons (close/min/max) Expected: * the action is taken Current: * touch controls are dismissed instead No autotest for this, looks like. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) ** Affects: unity8 (Ubuntu) Importance: High Assignee: Lukáš Tinkl (lukas-kde) Status: Triaged ** Tags: amd64 apport-bug third-party-packages 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/1648167 Title: Touch window controls dismiss the touch overlay instead Status in unity8 package in Ubuntu: Triaged Bug description: Steps: * three-finger-tap a window to get the window controls * tap on one of the window control buttons (close/min/max) Expected: * the action is taken Current: * touch controls are dismissed instead No autotest for this, looks like. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1648167/+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 1648169] [NEW] Close button in switcher is tiny
Public bug reported: Steps: * right-edge to switcher * hover over a closable surface (not Scopes) Expected: * close button is appropriately sized Current: * tiny close button ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty ** Attachment added: "screenshot20161207_181433987.png" https://bugs.launchpad.net/bugs/1648169/+attachment/4788666/+files/screenshot20161207_181433987.png ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1648169 Title: Close button in switcher is tiny Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: Steps: * right-edge to switcher * hover over a closable surface (not Scopes) Expected: * close button is appropriately sized Current: * tiny close button ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20161129-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 18:17:15 2016 InstallationDate: Installed on 2016-05-06 (214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1648169/+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 1647133] Re: dns=dnsmasq does not work any more
That is simply: "Unit resolvconf.service could not be found" I believe there is some package(s) that I do not have installed, but I should have? NM 1.4.2-2ubuntu4 needs something to be installed, that NM 1.4.2-2ubuntu3 did not need. -- 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/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1633046] Re: Pressing play/pause hotkey hangs U8 session
** Also affects: media-hub (Ubuntu) Importance: Undecided Status: New -- 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/1633046 Title: Pressing play/pause hotkey hangs U8 session Status in media-hub package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: Log in to a U8 session in 16.10. Press the play/pause hotkey. Note that the session is now hung. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1633046/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
i915 drivers are now in the initramfs, as required. ** Tags added: verification-done -- 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/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in cryptsetup source package in Trusty: Invalid Status in initramfs-tools source package in Trusty: Fix Committed Status in cryptsetup source package in Vivid: Invalid Status in initramfs-tools source package in Vivid: Won't Fix Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1642704] Re: initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly
*** This bug is a duplicate of bug 1496163 *** https://bugs.launchpad.net/bugs/1496163 This duplicate mark is true, but that bug isn't gaining much traction. We really need this fixed. -- 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/1642704 Title: initramfs-tools on Trusty doesn't handle symlinks in newer linux- firmware packages correctly Status in initramfs-tools package in Ubuntu: Confirmed Bug description: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642704/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
resolvconf uploaded to zesty and x/y SRU review queues. Please forward to Debian too. ** Changed in: resolvconf (Ubuntu) Status: Triaged => Fix Committed ** Changed in: resolvconf (Ubuntu) Assignee: (unassigned) => Ryan Harper (raharper) -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) Status in systemd: Fix Released Status in cloud-init package in Ubuntu: Triaged Status in resolvconf package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in resolvconf source package in Xenial: Triaged Status in systemd source package in Xenial: Fix Committed Status in cloud-init source package in Yakkety: New Status in resolvconf source package in Yakkety: Triaged Status in systemd source package in Yakkety: Fix Committed Bug description: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances SRU INFORMATION FOR systemd === Fix: For xenial it
[Touch-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more
What does "systemctl status resolvconf" say? is it not running for you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Triaged Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1105493] Re: network manager runs dnsmasq as user nobody
DNSMASQ runs as user nobody per design of dnsmasq devs. from the manpage: -u, --user= Specify the userid to which dnsmasq will change after startup. Dnsmasq must normally be started as root, but it will drop root privileges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch. -- 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/1105493 Title: network manager runs dnsmasq as user nobody Status in network-manager package in Ubuntu: Confirmed Bug description: Network Manager starts dnsmasq to provide better performing DNS service to the end user; however, it starts dnsmasq as user nobody: $ ps auwwx | grep [d]nsmasq nobody 993 0.0 0.1 33072 1120 ?S12:06 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Generally it's bad form from a security perspective to run daemons as user nobody because a vulnerability in one daemon will possibly allow it, when compromised, to interfere with another daemon that is also running as nobody. The preferred solution is to run it under a service-specific system user. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jan 25 14:17:36 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-25 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 10.0.2.2 dev eth0 proto static 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 16065df63-d4a5-4426-bf03-4b938adcdf28 802-3-ethernet1359152173 Fri 25 Jan 2013 02:16:13 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1105493/+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 1562111] Re: network-manager no longer restarts dnsmasq
DNSMASQ runs as user nobody per design of dnsmasq devs. from the manpage: -u, --user= Specify the userid to which dnsmasq will change after startup. Dnsmasq must normally be started as root, but it will drop root privileges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch. -- 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/1562111 Title: network-manager no longer restarts dnsmasq Status in network-manager package in Ubuntu: New Bug description: restarting Network Manager does not have any effect on it's child dnsmasq (nor does stopping and starting) ubuntu@ubuntu:~$ pidof dnsmasq 2355 ubuntu@ubuntu:~$ sudo systemctl restart NetworkManager ubuntu@ubuntu:~$ pidof dnsmasq 2355 This problem started in 15.10 and still exists in 16.04 beta2 - it works as expected in 14.04. The upshot is you cannot load any extra dnsmasq configuration set in the conf dir /etc/NetworkManager/dnsmasq.d/ because dnsmasq doesn't get restarted. (As a related issue dnsmasq is also running as 'nobody' and I don't think it should, Bug #1105493) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 25 18:13:33 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.107 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 53d8bcbd-4047-4705-904a-60eef9d821c1 802-3-ethernet 1458929440 Fri 25 Mar 2016 06:10:40 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- Mosquitoa88863fb-196e-4000-8103-880e0698d514 802-11-wireless 1458929448 Fri 25 Mar 2016 06:10:48 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Mosquitoa88863fb-196e-4000-8103-880e0698d514 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1562111/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
*** This bug is a duplicate of bug 1500751 *** https://bugs.launchpad.net/bugs/1500751 Checked, and this is fixed in the version in -proposed- from that bug. -- 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/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: New Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1646758] Re: Can't update or install apps
in next update on proposed ** Changed in: canonical-devices-system-image Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646758 Title: Can't update or install apps Status in Canonical System Image: Fix Released Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: bq M10 rc-proposed r243 When trying to update an app this morning, I got an error about destination path not being writable. The app is YouTube by Mateo Salta. Screenshot with the error attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648143] [NEW] tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
Public bug reported: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: tor (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor lxd tor ** Also affects: tor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: New Status in tor package in Ubuntu: New Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:844
[Touch-packages] [Bug 1337873] Re: ifupdown initialization problems caused by race condition
** Changed in: ifupdown (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1337873 Title: ifupdown initialization problems caused by race condition Status in ifenslave package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in ifenslave source package in Precise: Won't Fix Status in ifupdown source package in Precise: Won't Fix Status in ifenslave source package in Trusty: Fix Released Status in ifupdown source package in Trusty: Fix Released Status in ifenslave source package in Vivid: Fix Released Status in ifupdown source package in Vivid: Won't Fix Status in ifenslave source package in Wily: Fix Released Status in ifupdown source package in Wily: Fix Released Status in ifupdown package in Debian: Fix Released Bug description: [Impact] * Lack of proper synchronization in ifupdown causes a race condition resulting in occasional incorrect network interface initialization (e.g. in bonding case - wrong bonding settings, network unavailable because slave<->master interfaces initialization order was wrong * This is very annoying in case of large deployments (e.g. when bringing up 1000 machines it is almost guaranteed that at least a few of them will end up with network down). * It has been fixed by introducing hierarchical and per-interface locking mechanism ensuring the right order (along with the correct order in the /e/n/interfaces file) of initialization [Test Case] 1. Create a VM with bonding configured with at least 2 slave interfaces. 2. Reboot. 3. If all interfaces are up - go to 2. [Regression Potential] * This change has been introduced upstream in Debian. * It does not require any config changes to existing installations. [Other Info] Original bug description: * please consider my bonding examples are using eth1 and eth2 as slave interfaces. ifupdown some race conditions explained bellow. ifenslave does not behave well with sysv networking and upstart network-interface scripts running together. case 1) (a) ifup eth0 (b) ifup -a for eth0 - 1-1. Lock ifstate.lock file. 1-1. Wait for locking ifstate.lock file. 1-2. Read ifstate file to check the target NIC. 1-3. close(=release) ifstate.lock file. 1-4. Judge that the target NIC isn't processed. 1-2. Read ifstate file to check the target NIC. 1-3. close(=release) ifstate.lock file. 1-4. Judge that the target NIC isn't processed. 2. Lock and update ifstate file. Release the lock. 2. Lock and update ifstate file. Release the lock. !!! to be explained !!! case 2) (a) ifenslave of eth0 (b) ifenslave of eth0 -- 3. Execute ifenslave of eth0. 3. Execute ifenslave of eth0. 4. Link down the target NIC. 5. Write NIC id to /sys/class/net/bond0/bonding /slaves then NIC gets up 4. Link down the target NIC. 5. Fails to write NIC id to /sys/class/net/bond0/bonding/ slaves it is already written. !!! # My setup: root@provisioned:~# cat /etc/modprobe.d/bonding.conf alias bond0 bonding options bonding mode=1 arp_interval=2000 Both, /etc/init.d/networking and upstart network-interface begin enabled. Beginning: root@provisioned:~# cat /etc/network/interfaces # /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp I'm able to boot with both scripts (networking and network-interface enabled) with no problem. I can also boot with only "networking" script enabled: --- root@provisioned:~# initctl list | grep network network-interface stop/waiting networking start/running --- OR only the script "network-interface" enabled: --- root@provisioned:~# initctl list | grep network network-interface (eth2) start/running network-interface (lo) start/running network-interface (eth0) start/running network-interface (eth1) start/running --- Enabling bonding: Following ifenslave configuration example (/usr/share/doc/ifenslave/ examples/two_hotplug_ethernet), my /etc/
[Touch-packages] [Bug 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
*** This bug is a duplicate of bug 1500751 *** https://bugs.launchpad.net/bugs/1500751 Trusty is the one I care about, not Zesty. What does a "test case" mean in detail? Happy to help, I just want to know exactly what I need to do. -- 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/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: New Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another
** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-16.12 -- 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/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another Status in systemd: New Status in systemd package in Ubuntu: In Progress Bug description: I have an ipv4 entry for a key host on my network listed in /etc/hosts, for network recovery purposes. This host also has ipv6 connectivity; the ipv6 address is resolvable via DNS, but I do not have it in /etc/hosts. Resolution of hostname should be independent for each address family. Two days ago (I don't know what changed to trigger this), I stopped being able to resolve the ipv6 address for this host. I traced this down to systemd-resolved, returning a lookup failure for the nss request, because the ipv6 address is not listed in /etc/hosts. Removing resolve from /etc/nsswitch.conf restores the correct behavior. Removing the ipv4 entry for the host restores the correct behavior. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 23 08:13:33 2016 InstallationDate: Installed on 2010-09-24 (2252 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-28 (25 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1644330/+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 1384503] Re: rsync fails on large files with compression
** Changed in: rsync (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: rsync (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Trusty: Triaged Bug description: [Status] This issue is currently Incomplete. We're currently blocked on obtaining access to a reliable, and publicly available dataset that can be shared to reproduce the issue. The test is critical to being able to evaluate the impact of the change on other users when assessing if the fix can be SRU'ed to trusty. If you are affected by this bug and can reliably reproduce the issue with a specific dataset that you are willing and permitted to share please comment and specify the dataset location, and how you reproduce the issue. [Original Description] Copying large (>10GB) files with rsync -z (compression) leads to a long hang and eventual error after transferring part of the file. The error is consistent. The file copies at normal speed until it reaches its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another). Then nothing happens for a while (many minutes). Finally, there is an error: [] jh/.VirtualBox/win7/win7.vbox jh/.VirtualBox/win7/win7.vbox-prev jh/.VirtualBox/win7/win7.vdi rsync: [sender] write error: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0] In this case, 6.9 GB of 29 GB transferred. Without -z, it works. See the following upstream report, with a comment at the end from the rsync maintainer: https://bugzilla.samba.org/show_bug.cgi?id=10372 According to this report, version 3.1.0 (included in 14.04) uses a different compression package from prior versions. Prior versions did not have this problem for me using the same command on the same systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04 now, in each case with all updates applied, Intel hardware. Network connection between them is gigabit ethernet through one switch. A shell ssh between them in a terminal works and stays up during the failure, so it is not a network issue. There are no relevant entries in syslog on either machine. There is sufficient capacity on the receiving disk. All filesystems are ext4. rsync command: /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found --exclude=.gvfs --exclude=/nonlaptop /home/ backup.host.edu:/bu/host/home/ (yes, I changed the machine names) Current release (both hosts): Description: Ubuntu 14.04.1 LTS Release: 14.04 Current package (both hosts): rsync: Installed: 3.1.0-2ubuntu0.1 Candidate: 3.1.0-2ubuntu0.1 Version table: *** 3.1.0-2ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.0-2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Thanks, --jh-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init - * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) - + * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. - These uploads address this by replacing the one-off klibc dhcp client - (IPv4-only) with the defacto standard isc-dhcp-client, and thereby - provide both ipv6 and ipv4 DHCP configuration. + These uploads add "ip6=" to the command line syntax to configure ipv6 + using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" + syntax) remain unchanged. + + Valid format for the ip6= command line option is: +ip6=none (or ip6=off or ip6=) -- do not configure ipv6 +ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
** Bug watch added: Debian Bug tracker #847366 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366 ** Also affects: virt-manager via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366 Importance: Unknown Status: Unknown ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366 Importance: Unknown Status: Unknown ** Changed in: virt-manager Importance: Unknown => Undecided ** Changed in: virt-manager Status: Unknown => New ** Changed in: virt-manager Remote watch: Debian Bug tracker #847366 => None ** No longer affects: gtk ** No longer affects: virt-manager ** No longer affects: virt-manager (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** Also affects: gtk+3.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366 Importance: Unknown Status: Unknown -- 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/1550983 Title: Fails to start with "Couldn't open libGL.so.1" (missing dependency?) Status in One Hundred Papercuts: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Unknown Bug description: virt-manager fails to start: $ virt-manager --debug --no-fork [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with command line: /usr/share/virt-manager/virt-manager --debug --no-fork [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) virt-manager version: 1.3.2 [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) virtManager import: Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory $ Installing the 'libgl1-mesa-glx' package resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virt-manager 1:1.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sun Feb 28 19:19:27 2016 InstallationDate: Installed on 2016-02-27 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+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 1646758] Re: Can't update or install apps
Confirming the same problems on mako rc-proposed. I can't update nor install any apps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646758 Title: Can't update or install apps Status in Canonical System Image: New Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: bq M10 rc-proposed r243 When trying to update an app this morning, I got an error about destination path not being writable. The app is YouTube by Mateo Salta. Screenshot with the error attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646758/+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 1646479] Re: Unity8 applications require access to name=com.ubuntu.MenuRegistrar
Moving this to snappy based on IRC conversation. ** Package changed: apparmor-easyprof-ubuntu (Ubuntu) => snapd (Ubuntu) ** Changed in: snapd (Ubuntu) Importance: Undecided => Medium ** Changed in: snapd (Ubuntu) Status: Incomplete => Triaged ** Also affects: snappy Importance: Undecided Status: New ** Changed in: snappy Status: New => Triaged ** Changed in: snappy Importance: Undecided => Medium ** Changed in: snappy Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Tags added: snapd-interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1646479 Title: Unity8 applications require access to name=com.ubuntu.MenuRegistrar Status in Snappy: Triaged Status in snapd package in Ubuntu: Triaged Bug description: All Qt applications running under unity8 require dbus access to name="com.ubuntu.MenuRegistrar" This will enable application menus for unity8 applications. The interface is described here: http://pastebin.ubuntu.com/23563719/ bus=session path="/com/ubuntu/MenuRegistrar" interface="com.ubuntu.MenuRegistrar" To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1646479/+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 1648107] [NEW] $XAUTHORITY should move into $XDG_RUNTIME_DIR
Public bug reported: Historically, the X authority file was placed into $HOME/.Xauthority such that X11 clients on remote servers could access it in environments in which $HOME is located on a network file system. Today, this practice has become an anachronism that causes far more problems than it solves: a) Remote X11 clients are typically started today via "ssh -X", which emulates its own X11 server port $DISPLAY and therefore always creates its own X authority file entry on the remote server. Therefore, there is no longer any practical benefit from having the X authority file located in $HOME. b) If $HOME is on a network file system that implements "root squash", then commands such as "sudo xterm" or "sudo wireshark" won't work to start an X client with root privileges, as root is not able to read ~/.Xauthority via NFS. :-( c) If $HOME is on a network file system with Kerberos authentication, then users can easily get locked out by their screensavers once the Kerberos ticket expires. This is because some screen lockers (e.g., gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome- screensaver/gnome-screensaver-dialog) in order to ask the user of a locked screen for their password. Such a tool needs to access $XAUTHORITY right before it can display the password prompt, which will fail if the user's Kerberos ticket has expired (e.g. because a machine was suspended for 24 hours and therefore the ticket was not refreshed automatically on time). Without the ability to ask for a password, the screensaver then cannot call pam_krb5 to renew the user's Kerberos ticket, and the user remains locked out in a deadlock situation. :-( Both b) and c) are regular reasons for support requests in educational/corporate Linux environments with $HOME on Kerberized NFS. The solution is simple. Instead of $HOME/.Xauthority, just use in future $XDG_RUNTIME_DIR/xauthority as the location of the X authority file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER might be a suitable fallback option.) According to https://standards.freedesktop.org/basedir-spec/basedir- spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for holding the X authority file: it is always located in a local tmpfs filesystem, guaranteed to be accessible only to the current user, and will be wiped when the user has closed all sessions. On modern Linux systems, pam_systemd usually creates XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end. (Note that according to https://standards.freedesktop.org/basedir-spec /basedir-spec-latest.html you should set the "sticky bit" on any files created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.) Feature request: please provide an option for LightDM to do the equivalent of export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority chmod +t $XAUTHORITY and encourage Linux distribution maintainers to set this option by default, such that ~/.Xauthority is no longer used. ** 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/1648107 Title: $XAUTHORITY should move into $XDG_RUNTIME_DIR Status in lightdm package in Ubuntu: New Bug description: Historically, the X authority file was placed into $HOME/.Xauthority such that X11 clients on remote servers could access it in environments in which $HOME is located on a network file system. Today, this practice has become an anachronism that causes far more problems than it solves: a) Remote X11 clients are typically started today via "ssh -X", which emulates its own X11 server port $DISPLAY and therefore always creates its own X authority file entry on the remote server. Therefore, there is no longer any practical benefit from having the X authority file located in $HOME. b) If $HOME is on a network file system that implements "root squash", then commands such as "sudo xterm" or "sudo wireshark" won't work to start an X client with root privileges, as root is not able to read ~/.Xauthority via NFS. :-( c) If $HOME is on a network file system with Kerberos authentication, then users can easily get locked out by their screensavers once the Kerberos ticket expires. This is because some screen lockers (e.g., gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome- screensaver/gnome-screensaver-dialog) in order to ask the user of a locked screen for their password. Such a tool needs to access $XAUTHORITY right before it can display the password prompt, which will fail if the user's Kerberos ticket has expired (e.g. because a machine was suspended for 24 hours and therefore the ticket was not refreshed automatically on time). Without the ability to ask for a password, the screensaver then cannot call pam_krb5 to renew the user's Kerberos ticket, and the user
[Touch-packages] [Bug 1648077] Re: Support for Mozilla Location Service (A-GPS)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1648077 Title: Support for Mozilla Location Service (A-GPS) Status in location-service package in Ubuntu: Confirmed Bug description: Currently, A-GPS is only available on commercial UT-devices through Nokia HERE. This is a real problem for users of community ports (like those provided by ubports.com). Also, the HERE service is closed source and proprietary, that's kind of odd for the free operating system we all want Ubuntu Touch to be. I suggest that we try to implement the Mozilla Location Service, which is a free and open source location service: https://location.services.mozilla.com/ There is a bounty on Bountysource on this: https://www.bountysource.com/issues/39808752-support-for-mozilla- location-service-a-gps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1648077/+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 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- 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/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in Ubuntu on IBM z Systems: Fix Released Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Released Status in libica source package in Xenial: Invalid Status in openssl source package in Xenial: Invalid Status in openssl-ibmca source package in Xenial: Fix Released Status in libica source package in Yakkety: Invalid Status in openssl source package in Yakkety: Invalid Status in openssl-ibmca source package in Yakkety: Fix Released Bug description: [Testcase] * configure ibmca engine as per below instructions * execute openssl engine -c - * it should complete without any loading errors [Impact] * Out of the box stock configuration results in non-usable engine which errors out * Thus currently, without workarounds, the acceleration engine does not work. Meaning regression potential is low Please note this is the first time we are integrating openssl-ibmca, and it is not enabled by default. Hopefully things will be better / more stable going forward. openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise available in the filesystem: $ sudo find / -name "libica.so" 2>/dev/null ubuntu@HWE0001:~$ But there is a different verison of that libica: $ sudo find / -name "*libica.so*" 2>/dev/null /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so.2.6.1 $ So there are right now two workarounds: 1) creating a (symbolic) link from libica.so.2 to libica.so, like $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so that allows openssl to find a library named 'libica.so': 18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support But this could lead to issues in case of any potential functions or interface changes there we introduced with libica.so.2 2) installation of the "libica-dev" package that provides a (development) version of libica.so: $ dpkg -L libica-dev | grep libica.so /usr/lib/s390x-linux-gnu/libica.so $ But the ha
[Touch-packages] [Bug 1646479] Re: Unity8 applications require access to name=com.ubuntu.MenuRegistrar
Jamie, ideally - both. We know this will need to go into $insert_appropriate_snapd_interface, but before then it'd be nice to have on traditional setups, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1646479 Title: Unity8 applications require access to name=com.ubuntu.MenuRegistrar Status in apparmor-easyprof-ubuntu package in Ubuntu: Incomplete Bug description: All Qt applications running under unity8 require dbus access to name="com.ubuntu.MenuRegistrar" This will enable application menus for unity8 applications. The interface is described here: http://pastebin.ubuntu.com/23563719/ bus=session path="/com/ubuntu/MenuRegistrar" interface="com.ubuntu.MenuRegistrar" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1646479/+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
