[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start
attached xorg log after installing xdiagnose ** Attachment added: "xorg.log" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1666059/+attachment/4832789/+files/xorg.log -- 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/1666059 Title: Main virtualbox window resizes itself 3 or 4 times - then no desktop start Status in mesa package in Ubuntu: New Status in virtualbox package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Install virtualbox from repo's. Install Xubuntu or Ubuntu Install virtulabox-guest-utils Reboot - virtual installation starts. Install virtualbox-guest-x11 Reboot Virtual installation starts, see disk clean notice, window then resizes itself a few times - then cursor flashing but no login screen appears ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: virtualbox-guest-x11 5.1.14-dfsg-2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 19 20:34:16 2017 InstallationDate: Installed on 2017-02-19 (0 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1666059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start
** Summary changed: - Main virtualbox window resizes itself 4 or 4 times - then no start + Main virtualbox window resizes itself 3 or 4 times - then no desktop start -- 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/1666059 Title: Main virtualbox window resizes itself 3 or 4 times - then no desktop start Status in mesa package in Ubuntu: New Status in virtualbox package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Install virtualbox from repo's. Install Xubuntu or Ubuntu Install virtulabox-guest-utils Reboot - virtual installation starts. Install virtualbox-guest-x11 Reboot Virtual installation starts, see disk clean notice, window then resizes itself a few times - then cursor flashing but no login screen appears ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: virtualbox-guest-x11 5.1.14-dfsg-2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 19 20:34:16 2017 InstallationDate: Installed on 2017-02-19 (0 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1666059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
@ Robert - grabbed from -proposed. Locking from desktop appears to work as expected. Unlocking from suspend - I get hiccups if I'm a bit quick entering password (bug 1666803) -- 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/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: In Progress Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
** Attachment added: "seat0-greeter.log" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823519/+files/seat0-greeter.log -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
@robert - I've seen reports from xubuntu testers where it was sometimes working. So I tried more on a completely brand new installation. Lock - unlock fails - this continued for 3 attempts at which point I reached desktop. Lock and unlock cycle next time took 2 attempts. Lock and unlock cycle next time took 1 attempt. I was then able to lock and unlock at will. Attached all /var/log/lightdm logs from that session. ** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823518/+files/lightdm.log -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
In my used and abused installation I see similar behaviour. -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
** Attachment added: "x-0_x-1.log" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823520/+files/x-0_x-1.log -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
@Gunnar - thank you -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
really wish people wouldn't fiddle with bug status -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
was going to check the budgie greeter - but that uses lightdm-gtk- greeter and fails the same as with other flavours ** Tags added: budgie ** Summary changed: - Unable to unlock Xubuntu XFCE session after suspend. + Unable to unlock session after suspend using lightdm-gtk-greeter. -- 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/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
Checked with gnome-screensaver and xscreensaver instead of light-locker. In both cases - lock and suspend both work as expected. lock then login as new user fails to allow you back to original use downgrading lightdm to 1.21.1-0ubuntu1 allows lock and login as new user, however both require user to login twice to gain access to locked desktop -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
Greeter log ** Attachment added: "seat0-greeter.log" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4808265/+files/seat0-greeter.log -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
Error in comment #7 1.21.1-0ubuntu2 does not allow locking ** Tags added: lubuntu xubuntu zesty -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
affects lubuntu -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
attached lightdm.log following failure to unlock ** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4805159/+files/lightdm.log -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
however - seems locking fails in vm with 1.21.1-0ubuntu2 -- 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/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.
Downgraded lightdm packages as follows: 1.21.1-0ubuntu1 locking works suspend works 1.21.1-0ubuntu2 locking works suspend works 1.21.2-0ubuntu not downloadable 1.21.3-0ubuntu1 no locking ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1656399 Title: Unable to unlock Xubuntu XFCE session after suspend. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650036] [NEW] Some mkv files report error
Public bug reported: Playing some video files - especially mkv files sees totem report Internal Data Stream error Grabbed http://trailers.divx.com/divx_prod/profiles/WiegelesHeliSki_DivXPlus_19Mbps.mkv to test. running totem from terminal gets: totem (totem:12124): Gtk-WARNING **: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned (totem:12124): Gtk-WARNING **: Calling org.xfce.Session.Manager.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit" with signature "susu" on interface "org.xfce.Session.Manager" doesn't exist (totem:12124): Totem-WARNING **: Failed to reset the playback rate to 1.0 (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): Totem-CRITICAL **: totem_object_empty_menu_section: assertion 'TOTEM_IS_OBJECT (totem)' failed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.2-1 ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8 Uname: Linux 4.9.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 14 21:57:45 2016 InstallationDate: Installed on 2016-06-11 (186 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** 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 gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1650036 Title: Some mkv files report error Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing some video files - especially mkv files sees totem report Internal Data Stream error Grabbed http://trailers.divx.com/divx_prod/profiles/WiegelesHeliSki_DivXPlus_19Mbps.mkv to test. running totem from terminal gets: totem (totem:12124): Gtk-WARNING **: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned (totem:12124): Gtk-WARNING **: Calling org.xfce.Session.Manager.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit" with signature "susu" on interface "org.xfce.Session.Manager" doesn't exist (totem:12124): Totem-WARNING **: Failed to reset the playback rate to 1.0 (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): Totem-CRITICAL **: totem_object_empty_menu_section: assertion 'TOTEM_IS_OBJECT (totem)' failed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.2-1 ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8 Uname: Linux 4.9.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 14 21:57:45 2016 InstallationDate: Installed on 2016-06-11 (186 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1650036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627310] Re: Guest session fails to log out
** Changed in: xfce4-session (Ubuntu) Status: Confirmed => Fix Released -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Fix Released Status in xfce4-session package in Ubuntu: Fix Released Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627310] Re: Guest session fails to log out
** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid ** Changed in: lightdm (Ubuntu) Status: Invalid => Fix Released -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Fix Released Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen
** No longer affects: light-locker (Ubuntu) -- 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/1622303 Title: Fails to unlock/ resumes to black screen Status in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Status in xfce4-session package in Ubuntu: In Progress Status in xubuntu-default-settings package in Ubuntu: Fix Released Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1622303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen
** Package changed: lightdm (Ubuntu) => ubuntu -- 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/1622303 Title: Fails to unlock/ resumes to black screen Status in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Status in xfce4-session package in Ubuntu: In Progress Status in xubuntu-default-settings package in Ubuntu: Fix Released Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1622303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
** No longer affects: xubuntu-default-settings (Ubuntu) -- 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/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627310] Re: Guest session fails to log out
** This bug is no longer a duplicate of bug 1627304 User locking problems - guest login crashing -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen
Reverted to older xubuntu-default-settings - undid https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627304/comments/18 Reverted to light-locker. Everything now works as expected. -- 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/1622303 Title: Fails to unlock/ resumes to black screen Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
@robert-ancell - reverted (Xubuntu) to our old default settings, undid this change and everything works as before. Change to xubuntu-default-settings was something pitti appears to have done -- 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/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
@robert-ancell - tested that on Xubuntu (bug 1627310) works fine there using something other than light-locker (we have a seperate issue there bug 1622303) -- 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/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627310] Re: Guest session fails to log out
*** This bug is a duplicate of bug 1627304 *** https://bugs.launchpad.net/bugs/1627304 test@test-Standard-PC-i440FX-PIIX-1996:~$ dmesg | grep DENIED [ 50.801345] audit: type=1400 audit(1474991831.922:27): apparmor="DENIED" operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1722/fd/2" pid=1722 comm="lightdm-session" requested_mask="c" denied_mask="c" fsuid=996 ouid=996 [ 50.803080] audit: type=1400 audit(1474991831.922:28): apparmor="DENIED" operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1724/fd/2" pid=1724 comm="lightdm-session" requested_mask="c" denied_mask="c" fsuid=996 ouid=996 [ 50.932125] audit: type=1400 audit(1474991832.054:29): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1846 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.941490] audit: type=1400 audit(1474991832.062:30): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1862 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.946784] audit: type=1400 audit(1474991832.066:31): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1866 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.949328] audit: type=1400 audit(1474991832.070:32): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1870 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.951780] audit: type=1400 audit(1474991832.074:33): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1874 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.954141] audit: type=1400 audit(1474991832.074:34): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1878 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 62.395078] audit: type=1400 audit(1474991843.538:35): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2127 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 62.397757] audit: type=1400 audit(1474991843.542:36): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2129 comm="dbus-send" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" test@test-Standard-PC-i440FX-PIIX-1996:~$ ** This bug has been marked a duplicate of bug 1627304 User locking problems - guest login crashing -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) P
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
Sep 23 21:42:38 wolf-wolf kernel: [ 69.411731] audit: type=1400 audit(1474663358.636:31): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=3713 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart- session/999/3321" peer_addr=none peer="unconfined" -- 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/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Incomplete Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
>From Xubuntu, see same symptoms as seen previously - that is, can log in to Guest - logout fails. Dialogue looks ok for us. -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
In Xubuntu we can login to the gues user desktop - but it crashes on logout rather than logging in. -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Also affects: xubuntu-default-settings (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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing
A similar issue exists in Xubuntu. Default xubuntu install however does not allow to resume a locked session at all. We've experimented with changing locker from light-locker to gnome- screensaver and xscreensaver - when using gnome-screensaver we see the same as with the Ubuntu issue. bug 1622303 -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627304] [NEW] User locking problems - guest login crashing
Public bug reported: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-greeter (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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615341] Re: Yakkety desktop fails to start
attached systemd graphical session log just in case ** Attachment added: "systemd-graphical-session.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615341/+attachment/4724974/+files/systemd-graphical-session.log -- 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/1615341 Title: Yakkety desktop fails to start Status in systemd package in Ubuntu: New Bug description: Following a set of updates (attached) Saturday 20th I lost a working desktop. Further to that dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system For Xubuntu (both locally and in installed daily) Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu- session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615341] Re: Yakkety desktop fails to start
** Tags added: mate xubuntu ** Description changed: Following a set of updates (attached) Saturday 20th I lost a working - desktop. Further to that recent dailies for Xubuntu and Mate both fail - to start a working desktop either by: + desktop. + + Further to that dailies for Xubuntu and Mate both fail to start a + working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system + + For Xubuntu (both locally and in installed daily) Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu-session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 -- 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/1615341 Title: Yakkety desktop fails to start Status in systemd package in Ubuntu: New Bug description: Following a set of updates (attached) Saturday 20th I lost a working desktop. Further to that dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system For Xubuntu (both locally and in installed daily) Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu- session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~to
[Touch-packages] [Bug 1615338] Re: Yakkety fails to start desktop
** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1615338 Title: Yakkety fails to start desktop Status in xorg package in Ubuntu: Invalid Bug description: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615341] [NEW] Yakkety desktop fails to start
Public bug reported: Following a set of updates (attached) Saturday 20th I lost a working desktop. Further to that recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu-session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615341 Title: Yakkety desktop fails to start Status in systemd package in Ubuntu: New Bug description: Following a set of updates (attached) Saturday 20th I lost a working desktop. Further to that recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu- session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615338] Re: Yakkety fails to start desktop
Iso Tracker suggest ubuntu-bug syslinux for "... while booting the ISO image:" attached apport file for apport-bug syslinux ** Attachment added: "apport.syslinux.d0h9lir9.apport" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+attachment/4724906/+files/apport.syslinux.d0h9lir9.apport -- 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/1615338 Title: Yakkety fails to start desktop Status in xorg package in Ubuntu: New Bug description: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615338] Re: Yakkety fails to start desktop
** Attachment added: "journalctl from installed system" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+attachment/4724905/+files/journal_dump -- 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/1615338 Title: Yakkety fails to start desktop Status in xorg package in Ubuntu: New Bug description: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615338] [NEW] Yakkety fails to start desktop
Public bug reported: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "apport-bug linux created file from installation" https://bugs.launchpad.net/bugs/1615338/+attachment/4724901/+files/apport.linux-image-4.4.0-9134-generic.t_fy6opk.apport -- 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/1615338 Title: Yakkety fails to start desktop Status in xorg package in Ubuntu: New Bug description: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1592319] Re: systemd-resolved crashed with SIGABRT
*** This bug is a duplicate of bug 1587727 *** https://bugs.launchpad.net/bugs/1587727 ** Information type changed from Private to Public -- 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/1592319 Title: systemd-resolved crashed with SIGABRT Status in systemd package in Ubuntu: New Bug description: seemingly some apparmor fail ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 230-2git1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Jun 14 10:06:04 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-06-11 (2 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. Title: systemd-resolved crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1592319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589098] Re: systemd-resolved crashed with signal 7
*** This bug is a duplicate of bug 1587727 *** https://bugs.launchpad.net/bugs/1587727 ** Information type changed from Private to Public -- 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/1589098 Title: systemd-resolved crashed with signal 7 Status in systemd package in Ubuntu: New Bug description: another resolved bug just showing up ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 230-2git1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Sat Jun 4 14:16:43 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-01-11 (144 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111) MachineType: NOVATECH LTD MBB-44608 ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic root=UUID=0e76f726-36fe-4fff-b2aa-bc812147b087 ro quiet splash vt.handoff=7 Signal: 7 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. Title: systemd-resolved crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1589098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589808] Re: systemd-resolved crashed with SIGSEGV
*** This bug is a duplicate of bug 1587727 *** https://bugs.launchpad.net/bugs/1587727 ** Information type changed from Private to Public -- 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/1589808 Title: systemd-resolved crashed with SIGSEGV Status in systemd package in Ubuntu: Confirmed Bug description: yet another crash for no apparent reason ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 230-2git1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Tue Jun 7 07:08:19 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-01-11 (147 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111) MachineType: NOVATECH LTD MBB-44608 ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic root=UUID=0e76f726-36fe-4fff-b2aa-bc812147b087 ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. Title: systemd-resolved crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1589808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587740] Re: systemd-resolved crashed: Assertion '*_head == _item' failed at ../src/resolve/resolved-dns-transaction.c:94, function dns_transaction_free().
seem to still be seeing this > bug 1589561 bug 1589249 -- 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/1587740 Title: systemd-resolved crashed: Assertion '*_head == _item' failed at ../src/resolve/resolved-dns-transaction.c:94, function dns_transaction_free(). Status in systemd package in Ubuntu: Fix Released Bug description: Reached desktop when error came up. System was just started up https://github.com/systemd/systemd/issues/2942 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 230-1git1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Wed Jun 1 08:48:49 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-05-31 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160529) MachineType: Hewlett-Packard HPE-520sc ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=d38e5967-3b2c-43c7-965f-e90d52f4bb3d ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. Title: systemd-resolved crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/04/2011 dmi.bios.vendor: AMI dmi.bios.version: 7.13 dmi.board.name: 2AB6 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.04 dmi.chassis.asset.tag: CZC122BR03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.13:bd05/04/2011:svnHewlett-Packard:pnHPE-520sc:pvr1.04:rvnPEGATRONCORPORATION:rn2AB6:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HPE-520sc dmi.product.version: 1.04 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
ftr - got an upgraded from 14.04 system here now (vanilla virtual - but even so ...) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1555237 Title: Upgrade from 14.04.4→ 16.04 dies midway taking out the session. Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: STEPS: 1. Install 14.04.4 on a uefi securebooted system 2. update it 3. Install openssh-server for debug access 4. reboot 5. Hit alt+f2 6. Type update-manager -d and hit enter EXPECTED: I expected a smooth transition to 16.04 ACTUAL: System is completely taken out mid way through the process killing the session and x also no tty when hitting ctrl+alt+f1-6 --- TESTS RESULTS (from cyphermox): On amd64 (no EFI) under qemu/libvirt, qxl graphics: - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS - manually upgrading compiz and other packages to 16.04 versions; after adding xenial sources: - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS - xserver-xorg and related: PASS - unity and related: PASS - ubuntu-desktop: PASS - libgl1-mesa-dri: PASS - apt-get dist-upgrade: FAIL (screensaver may have kicked in) - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked fine, but upgrade eventually froze, might well be a different issue) - re-enabling screensaver after upgrade, before reboot: TODO (above failed) On ppc64el: - upgrading ubuntu-server 14.04.4 -> 16.04: PASS --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CrashDB: ubuntu Date: Wed Mar 9 17:01:27 2016 InstallationDate: Installed on 2016-03-04 (5 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1555237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554099] Re: Changing what action for security updates unusable
** Description changed: Open software-properties. Important security updates is not enabled on install. Secondly - it is not possible to change the action to take with security updates even if it is enabled (note: I enabled security updates, reloaded cache and restarted software-properties before trying to change the action) + + eg - the Display Immediately/Download automatically/Download and install + automatically ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-gtk 0.96.18 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 15:35:24 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable Status in software-properties package in Ubuntu: New Bug description: Open software-properties. Important security updates is not enabled on install. Secondly - it is not possible to change the action to take with security updates even if it is enabled (note: I enabled security updates, reloaded cache and restarted software-properties before trying to change the action) eg - the Display Immediately/Download automatically/Download and install automatically ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-gtk 0.96.18 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 15:35:24 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554099] [NEW] Changing what action for security updates unusable
Public bug reported: Open software-properties. Important security updates is not enabled on install. Secondly - it is not possible to change the action to take with security updates even if it is enabled (note: I enabled security updates, reloaded cache and restarted software-properties before trying to change the action) eg - the Display Immediately/Download automatically/Download and install automatically ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-gtk 0.96.18 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 15:35:24 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot_2016-03-07_15-39-41.png" https://bugs.launchpad.net/bugs/1554099/+attachment/4591664/+files/Screenshot_2016-03-07_15-39-41.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable Status in software-properties package in Ubuntu: New Bug description: Open software-properties. Important security updates is not enabled on install. Secondly - it is not possible to change the action to take with security updates even if it is enabled (note: I enabled security updates, reloaded cache and restarted software-properties before trying to change the action) eg - the Display Immediately/Download automatically/Download and install automatically ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-gtk 0.96.18 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 15:35:24 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547793] Re: upowerd crashed with SIGSEGV in g_variant_is_trusted()
@amjjawad - are you seeing the same issue in virtualbox? I'm not that works fine here. If you mean you've got vbox on a laptop - that shouldn't affect this, which is installing to the laptop. That crashes immediately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1547793 Title: upowerd crashed with SIGSEGV in g_variant_is_trusted() Status in Ubuntu Kylin: New Status in Upower: In Progress Status in upower package in Ubuntu: Fix Released Status in upower package in Debian: New Bug description: Crash when connecting laptop to charger. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: upower 0.99.4-1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Feb 20 16:18:04 2016 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2015-04-07 (319 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fdb12e38ee0:mov0x20(%rdi),%eax PC (0x7fdb12e38ee0) ok source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upower StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: upowerd crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1547793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539700] Re: Audio cd's play with background buzzing
I found if I enabled crossfade then played audio it worked, took a reboot to get the issue. ftr - removing gstreamer1.0-plugins-base 1.7.1-1ubuntu1 and installing the wily version gstreamer1.0-plugins-base_1.6.0-1ubuntu1 the issue of 'buzzing' disappears. Same with the clementine playback issue I reported in the older bug I reported at 1537184 -- 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/1539700 Title: gst-base 1.7 update created background buzzing noise with audioconvert Status in alsa-driver package in Ubuntu: Confirmed Status in goobox package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Also affects cdplayer (goobox). Is not seen in audacious or vlc at all (using default audio of pulse Test case: insert audio cd, play in rhymbox or cdplayer What happens: significant background buzzing May be gstreamer issue? Attached is simple recording of what Rb is outputting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1652 F pulseaudio /dev/snd/pcmC1D0p: doug 1652 F...m pulseaudio /dev/snd/controlC1: doug 1652 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 12:00:33 2016 InstallationDate: Installed on 2016-01-14 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160114) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20217, Realtek ALC282, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1539700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544346] Re: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046)
entirely possible - was trying to confirm (or not) bug 1544325 and then this crashed :) Would like to be able to Invalid that one - will respond tomorrow - with hopefully 2 invalids -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1544346 Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) Status in software-properties package in Ubuntu: New Bug description: tried to add https://launchpad.net/~ubuntu-desktop/+archive/ubuntu /gnome-software add-apt bailed on me ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.17 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Wed Feb 10 23:15:10 2016 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2016-02-10 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:ubuntu-desktop/gnome-software ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ubuntu-desktop/gnome-software'] SourcePackage: software-properties Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1544346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544346] Re: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046)
I did obviously wait a while prior to reporting - been running 'dev' versions for some time. jfyi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1544346 Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) Status in software-properties package in Ubuntu: New Bug description: tried to add https://launchpad.net/~ubuntu-desktop/+archive/ubuntu /gnome-software add-apt bailed on me ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.17 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Wed Feb 10 23:15:10 2016 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2016-02-10 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:ubuntu-desktop/gnome-software ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ubuntu-desktop/gnome-software'] SourcePackage: software-properties Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1544346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544346] [NEW] add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046)
Public bug reported: tried to add https://launchpad.net/~ubuntu-desktop/+archive/ubuntu /gnome-software add-apt bailed on me ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.17 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Wed Feb 10 23:15:10 2016 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2016-02-10 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:ubuntu-desktop/gnome-software ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ubuntu-desktop/gnome-software'] SourcePackage: software-properties Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: software-properties (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1544346 Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) Status in software-properties package in Ubuntu: New Bug description: tried to add https://launchpad.net/~ubuntu-desktop/+archive/ubuntu /gnome-software add-apt bailed on me ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.17 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Wed Feb 10 23:15:10 2016 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2016-02-10 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:ubuntu-desktop/gnome-software ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ubuntu-desktop/gnome-software'] SourcePackage: software-properties Title: add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1544346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539700] Re: Audio cd's play with background buzzing
Ok - so possibly not just audio cd's given I see similar without any cd hardware at all, similarly not the clementine issue I reported (bug 1537184) I've been having the issue for a couple of weeks - possibly related to gst changes - changelogs show changes at about the time I saw the issue first, though just assumed it was clementine in dev version at the time. bag, good and ugly saw changes 5/6th Jan, base 11th Jan -- 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/1539700 Title: Audio cd's play with background buzzing Status in alsa-driver package in Ubuntu: New Status in goobox package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: Also affects cdplayer (goobox). Is not seen in audacious or vlc at all (using default audio of pulse Test case: insert audio cd, play in rhymbox or cdplayer What happens: significant background buzzing May be gstreamer issue? Attached is simple recording of what Rb is outputting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1652 F pulseaudio /dev/snd/pcmC1D0p: doug 1652 F...m pulseaudio /dev/snd/controlC1: doug 1652 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 12:00:33 2016 InstallationDate: Installed on 2016-01-14 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160114) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20217, Realtek ALC282, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1539700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539700] Re: Audio cd's play with background buzzing
Is it like this? https://sendvid.com/sa7b0i4n -- 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/1539700 Title: Audio cd's play with background buzzing Status in alsa-driver package in Ubuntu: New Status in goobox package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: Also affects cdplayer (goobox). Is not seen in audacious or vlc at all (using default audio of pulse Test case: insert audio cd, play in rhymbox or cdplayer What happens: significant background buzzing May be gstreamer issue? Attached is simple recording of what Rb is outputting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1652 F pulseaudio /dev/snd/pcmC1D0p: doug 1652 F...m pulseaudio /dev/snd/controlC1: doug 1652 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 12:00:33 2016 InstallationDate: Installed on 2016-01-14 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160114) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20217, Realtek ALC282, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1539700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525150] Re: Ubuntu font missing part of 8 and 3 in hexchat
** Attachment added: "missing 8" https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1525150/+attachment/4533078/+files/ubuntu%20font%208.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1525150 Title: Ubuntu font missing part of 8 and 3 in hexchat Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Not noticed this elsewhere, but in hexchat part of 8 and 3 is missing. Attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 11 10:06:33 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (42 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1525150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525150] [NEW] Ubuntu font missing part of 8 and 3 in hexchat
Public bug reported: Not noticed this elsewhere, but in hexchat part of 8 and 3 is missing. Attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 11 10:06:33 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (42 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-font-family-sources (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "missing 3" https://bugs.launchpad.net/bugs/1525150/+attachment/4533075/+files/ubuntu%20font%203.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1525150 Title: Ubuntu font missing part of 8 and 3 in hexchat Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Not noticed this elsewhere, but in hexchat part of 8 and 3 is missing. Attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 11 10:06:33 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (42 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1525150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
@laney - did that, no change, rebooted just in case, still no change -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
@mpt - bug 1521210 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
@magdalena - I can of course. What to report against though? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
While this appears to only show in LO apps, I also notice that the choice of Ubuntu Light for my desktop gets replaced with Ubuntu Thin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
@ fitojb - thanks - I did see some talk in #ubuntu-desktop yesterday, by the time I saw this it was EOD - so reported it while I remembered ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] Re: Upgraded font looks odd
** Attachment added: "post-upgradefont.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1520772/+attachment/4526689/+files/post-upgradefont.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: Upgraded font looks odd Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520772] [NEW] Upgraded font looks odd
Public bug reported: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-font-family-sources (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "pre-upgradefont.png" https://bugs.launchpad.net/bugs/1520772/+attachment/4526686/+files/pre-upgradefont.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: Upgraded font looks odd Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1520772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497170] Re: New file creation - not opening with file editor
** Tags removed: xubuntu-exp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1497170 Title: New file creation - not opening with file editor Status in GLib: Fix Released Status in One Hundred Papercuts: Confirmed Status in glib2.0 package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Bug description: Create a new file from File - Create Empty File. Open new document: expected behaviour - document opens in text editor actual behaviour - Open With dialogue opens requiring an application to open file. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: thunar 1.6.10-1 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 18 09:05:54 2015 InstallationDate: Installed on 2015-09-17 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-09-17 (1 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) Package: xdg-utils 1.1.0~rc3+git20150907-1ubuntu2 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Tags: wily Uname: Linux 4.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1497170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507333] Re: kernel panic during installation
Not seeing that here with the same image. -- 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/1507333 Title: kernel panic during installation Status in systemd package in Ubuntu: Incomplete Bug description: During the installation using the ISO image, a kernel panic happened. I could only capture a photo of the screen contents. Note that the kernel panic happened without the "wl" kernel module. I only activated it so I could upload this report. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1713 F pulseaudio CasperVersion: 1.365 CurrentDesktop: XFCE Date: Sun Oct 18 16:09:31 2015 LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1) MachineType: Dell Inc. Inspiron 1011 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=de keyboard-configuration/layoutcode?=de RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/29/2009:svnDellInc.:pnInspiron1011:pvrA06:rvnDellInc.:rnCN0Y53:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 1011 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1507333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
On an updated and rebooted system, restore from trash works - the first time. Moving the same file(s) previously restored to trash and then trying to restore again causes the same bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Confirmed Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497170] Re: New file creation - not opening with file editor
** Tags removed: wily ** Tags added: xubuntu-expwily ** Tags removed: xubuntu-expwily ** Tags added: wily xubuntu-exp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1497170 Title: New file creation - not opening with file editor Status in GLib: Confirmed Status in One Hundred Papercuts: Confirmed Status in glib2.0 package in Ubuntu: Fix Committed Status in xdg-utils package in Ubuntu: Invalid Bug description: Create a new file from File - Create Empty File. Open new document: expected behaviour - document opens in text editor actual behaviour - Open With dialogue opens requiring an application to open file. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: thunar 1.6.10-1 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 18 09:05:54 2015 InstallationDate: Installed on 2015-09-17 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-09-17 (1 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) Package: xdg-utils 1.1.0~rc3+git20150907-1ubuntu2 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Tags: wily Uname: Linux 4.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1497170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497170] Re: New file creation - not opening with file editor
updates this morning - new file still appears to be unknown type when created, but does open with text editor on double click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1497170 Title: New file creation - not opening with file editor Status in GLib: Confirmed Status in One Hundred Papercuts: Confirmed Status in glib2.0 package in Ubuntu: Triaged Status in xdg-utils package in Ubuntu: Invalid Bug description: Create a new file from File - Create Empty File. Open new document: expected behaviour - document opens in text editor actual behaviour - Open With dialogue opens requiring an application to open file. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: thunar 1.6.10-1 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 18 09:05:54 2015 InstallationDate: Installed on 2015-09-17 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-09-17 (1 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917) Package: xdg-utils 1.1.0~rc3+git20150907-1ubuntu2 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Tags: wily Uname: Linux 4.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1497170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498975] Re: Vivid to wily upgrade fails for autologin
Upgraded with livecd. Just redid this with the new livecd (ubiquity/user-setup changes) and autologin now works as expected. -- 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/1498975 Title: Vivid to wily upgrade fails for autologin Status in lightdm package in Ubuntu: Invalid Bug description: Installed vivid - with autologin. Completely updated vivid then upgraded to wily with image. System fails to autologin following upgrade to wily. Vivid lightdm.conf: [SeatDefaults] autologin-guest=false autologin-user=test autologin-user-timeout=0 autologin-session=lightdm-autologin Wily lightdm.conf [Seat:*] Xubuntu specific lightdm files in /usr/share/lightdm/lightdm.conf.d appear to have upgraded correctly changing [SeatDefaults] to [Seat:*] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 23 16:50:14 2015 InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922.1) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498975] Re: Vivid to wily upgrade fails for autologin
image upgrade - as noted above :) -- 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/1498975 Title: Vivid to wily upgrade fails for autologin Status in lightdm package in Ubuntu: Invalid Bug description: Installed vivid - with autologin. Completely updated vivid then upgraded to wily with image. System fails to autologin following upgrade to wily. Vivid lightdm.conf: [SeatDefaults] autologin-guest=false autologin-user=test autologin-user-timeout=0 autologin-session=lightdm-autologin Wily lightdm.conf [Seat:*] Xubuntu specific lightdm files in /usr/share/lightdm/lightdm.conf.d appear to have upgraded correctly changing [SeatDefaults] to [Seat:*] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 23 16:50:14 2015 InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922.1) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498975] Re: Vivid to wily upgrade fails for autologin
Yes. -- 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/1498975 Title: Vivid to wily upgrade fails for autologin Status in lightdm package in Ubuntu: New Bug description: Installed vivid - with autologin. Completely updated vivid then upgraded to wily with image. System fails to autologin following upgrade to wily. Vivid lightdm.conf: [SeatDefaults] autologin-guest=false autologin-user=test autologin-user-timeout=0 autologin-session=lightdm-autologin Wily lightdm.conf [Seat:*] Xubuntu specific lightdm files in /usr/share/lightdm/lightdm.conf.d appear to have upgraded correctly changing [SeatDefaults] to [Seat:*] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 23 16:50:14 2015 InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922.1) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498975] [NEW] Vivid to wily upgrade fails for autologin
Public bug reported: Installed vivid - with autologin. Completely updated vivid then upgraded to wily with image. System fails to autologin following upgrade to wily. Vivid lightdm.conf: [SeatDefaults] autologin-guest=false autologin-user=test autologin-user-timeout=0 autologin-session=lightdm-autologin Wily lightdm.conf [Seat:*] Xubuntu specific lightdm files in /usr/share/lightdm/lightdm.conf.d appear to have upgraded correctly changing [SeatDefaults] to [Seat:*] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 23 16:50:14 2015 InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922.1) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1498975 Title: Vivid to wily upgrade fails for autologin Status in lightdm package in Ubuntu: New Bug description: Installed vivid - with autologin. Completely updated vivid then upgraded to wily with image. System fails to autologin following upgrade to wily. Vivid lightdm.conf: [SeatDefaults] autologin-guest=false autologin-user=test autologin-user-timeout=0 autologin-session=lightdm-autologin Wily lightdm.conf [Seat:*] Xubuntu specific lightdm files in /usr/share/lightdm/lightdm.conf.d appear to have upgraded correctly changing [SeatDefaults] to [Seat:*] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 23 16:50:14 2015 InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922.1) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498544] Re: Autologin lost after 15.04 to 15.10 upgrade
This also affects new installs from wily dailies. ** Summary changed: - Autlogin lost after 15.04 to 15.10 upgrade + Autologin lost after 15.04 to 15.10 upgrade ** Summary changed: - Autologin lost after 15.04 to 15.10 upgrade + Autologin lost after 15.04 to 15.10 upgrades and/or 15.10 clean installs -- 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/1498544 Title: Autologin lost after 15.04 to 15.10 upgrades and/or 15.10 clean installs Status in lightdm package in Ubuntu: Confirmed Bug description: Installed 15.04, using autologin. Updated and upgraded 15.04. System autologin works correctly. Upgraded (via image http://iso.qa.ubuntu.com/qatracker/testcases/1498/info) then rebooted. Autologin fails. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 22 16:10:39 2015 InstallationDate: Installed on 2015-09-21 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150921) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498544] Re: Autlogin lost after 15.04 to 15.10 upgrade
/etc/lightdm/lightdm.conf contains [Seat:*] /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf contains [Seat:*] user-session=xubuntu Added autologin-user='username' System autologins correctly. Also seen in Ubuntu Mate and Ubuntu (wily dailies) -- 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/1498544 Title: Autlogin lost after 15.04 to 15.10 upgrade Status in lightdm package in Ubuntu: Confirmed Bug description: Installed 15.04, using autologin. Updated and upgraded 15.04. System autologin works correctly. Upgraded (via image http://iso.qa.ubuntu.com/qatracker/testcases/1498/info) then rebooted. Autologin fails. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 22 16:10:39 2015 InstallationDate: Installed on 2015-09-21 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150921) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484083] Re: Don't work autologin after update lightdm
re-reported at bug 1498544 -- 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/1484083 Title: Don't work autologin after update lightdm Status in One Hundred Papercuts: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in user-setup package in Ubuntu: Fix Released Bug description: Don't work autologin after update lightdm ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.15.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3 Uname: Linux 4.1.0-3-lowlatency x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 12 14:20:00 2015 InstallationDate: Installed on 2015-04-23 (110 days ago) InstallationMedia: SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1484083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1498544] [NEW] Autlogin lost after 15.04 to 15.10 upgrade
Public bug reported: Installed 15.04, using autologin. Updated and upgraded 15.04. System autologin works correctly. Upgraded (via image http://iso.qa.ubuntu.com/qatracker/testcases/1498/info) then rebooted. Autologin fails. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 22 16:10:39 2015 InstallationDate: Installed on 2015-09-21 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150921) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1498544 Title: Autlogin lost after 15.04 to 15.10 upgrade Status in lightdm package in Ubuntu: New Bug description: Installed 15.04, using autologin. Updated and upgraded 15.04. System autologin works correctly. Upgraded (via image http://iso.qa.ubuntu.com/qatracker/testcases/1498/info) then rebooted. Autologin fails. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 22 16:10:39 2015 InstallationDate: Installed on 2015-09-21 (0 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150921) LightdmConfig: [Seat:*] SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1498544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484083] Re: Don't work autologin after update lightdm
Xubuntu Wily editing /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf with the autologin details works -- 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/1484083 Title: Don't work autologin after update lightdm Status in One Hundred Papercuts: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in user-setup package in Ubuntu: Fix Released Bug description: Don't work autologin after update lightdm ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.15.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3 Uname: Linux 4.1.0-3-lowlatency x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 12 14:20:00 2015 InstallationDate: Installed on 2015-04-23 (110 days ago) InstallationMedia: SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1484083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484083] Re: Don't work autologin after update lightdm
Xubuntu Wily Daily Choose autologin during install. System doesn't autologin. /etc/lightdm.conf is populated only with [Seat:*] completing the conf with user-session and autologin-user to suit and it works properly. -- 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/1484083 Title: Don't work autologin after update lightdm Status in One Hundred Papercuts: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in user-setup package in Ubuntu: Fix Released Bug description: Don't work autologin after update lightdm ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.15.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3 Uname: Linux 4.1.0-3-lowlatency x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 12 14:20:00 2015 InstallationDate: Installed on 2015-04-23 (110 days ago) InstallationMedia: SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1484083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419384] Re: testcase of lubuntu's lightDM needs updating
** Package changed: lightdm (Ubuntu) => ubuntu-manual-tests -- 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/1419384 Title: testcase of lubuntu's lightDM needs updating Status in Ubuntu Manual Tests: New Bug description: The testcase for Lubuntu's lightDM is a little confusing. What is was instructing to test could not be found on Lubuntu 15.04 64bit. "This test will check that you can change a session correctly" "When logging out of the session, a greeting window appears. However, the screen that did appear did not have the word "greeting" on it". Instead the logout screen said, "Logout Lubuntu 15.04 session?". Instead of saying "greeting" screen, it should say "Logout screen". "From session menu (gear icon), choose any session" On the login screen, there is no "gear" icon associated with the session selecter. The only icon I saw, was the LXDE logo. "This test will check that localisation changes are applied correctly" None of the localization language changes applied successfully. After chooing, English_Austria, from the langauge selector, and logged in, the language I was using was English-English(US). "From Localisation menu (flag icon) choose one of the available languages" There was no flag icon next to the langauge selector. Again, I am running the 64bit version of Lubuntu 15.04. I would be more than happy to help update this testcase. lightdm: Installed: 1.13.1-0ubuntu2 Candidate: 1.13.1-0ubuntu2 Version table: *** 1.13.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid 3.18.0-9-generic #10-Ubuntu SMP Mon Jan 12 21:41:54 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sat Feb 7 21:13:27 2015 InstallationDate: Installed on 2015-01-25 (14 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150123) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1419384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428727] Re: dbus gave an error when trying to install language translation components
Does this still happen with Wily?
** Changed in: dbus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1428727
Title:
dbus gave an error when trying to install language translation
components
Status in dbus package in Ubuntu:
New
Bug description:
After installer the new daily image of Lubuntu 15.04, upon reboot, a
window appeared informing me that that language I was using (english-
us) was missing some language translation components. The displayed a
button "run this action now" to install the missing components. After
runing through all the steps that the wizard walked me through, I got
this error "org.freedesktop.PolicyKit.Error.Failed: ('system-bus-
name', {'name': ':1.56'}): org.debian.apt.install-or-remove-
packages". Not sure that to make of this error or what part of the
system it is referring to. I will make an educated guess based on
oservation that the installer did not get the required permission to
install the needed pacakages, yet it never asked for any. Also, I
don't know what package to install manually. Sorry for not giving a
screen shot of the window that appeared.
Installed: 1.8.12-1ubuntu3
Candidate: 1.8.12-1ubuntu3
Version table:
*** 1.8.12-1ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
100 /var/lib/dpkg/status
Distributor ID: Ubuntu
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
Codename: vivid
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dbus 1.8.12-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
ApportVersion: 2.16.2-0ubuntu1
Architecture: i386
Date: Thu Mar 5 11:21:28 2015
InstallationDate: Installed on 2015-03-05 (0 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150303)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1428727/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419384] Re: testcase of lubuntu's lightDM needs updating
** Changed in: lightdm (Ubuntu) Status: Incomplete => 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/1419384 Title: testcase of lubuntu's lightDM needs updating Status in lightdm package in Ubuntu: New Bug description: The testcase for Lubuntu's lightDM is a little confusing. What is was instructing to test could not be found on Lubuntu 15.04 64bit. "This test will check that you can change a session correctly" "When logging out of the session, a greeting window appears. However, the screen that did appear did not have the word "greeting" on it". Instead the logout screen said, "Logout Lubuntu 15.04 session?". Instead of saying "greeting" screen, it should say "Logout screen". "From session menu (gear icon), choose any session" On the login screen, there is no "gear" icon associated with the session selecter. The only icon I saw, was the LXDE logo. "This test will check that localisation changes are applied correctly" None of the localization language changes applied successfully. After chooing, English_Austria, from the langauge selector, and logged in, the language I was using was English-English(US). "From Localisation menu (flag icon) choose one of the available languages" There was no flag icon next to the langauge selector. Again, I am running the 64bit version of Lubuntu 15.04. I would be more than happy to help update this testcase. lightdm: Installed: 1.13.1-0ubuntu2 Candidate: 1.13.1-0ubuntu2 Version table: *** 1.13.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid 3.18.0-9-generic #10-Ubuntu SMP Mon Jan 12 21:41:54 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sat Feb 7 21:13:27 2015 InstallationDate: Installed on 2015-01-25 (14 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150123) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1419384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456730] Re: Hangs on shutdown after installing and running serviio
Reinstalled to /opt Added /lib/systemd/system/serviio.service with [Unit] Description=Serviio Media Server After=syslog.target local-fs.target network.target [Service] Type=simple User=serviio Group=serviio ExecStart=/opt/serviio/bin/serviio.sh ExecStop=/opt/serviio/bin/serviio.sh -stop KillMode=none Restart=on-abort [Install] WantedBy=multi-user.target Enabled and started service. Small script to start the console added to startup #!/bin/sh /opt/serviio/bin/serviio-console.sh exit 0 No further issues with shutdowns or reboots (http://wiki.serviio.org/doku.php?id=howto:linux:install:ubuntu15-04) -- 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/1456730 Title: Hangs on shutdown after installing and running serviio Status in systemd package in Ubuntu: Confirmed Bug description: Ran serviio during the vivid cycle with no problem - either using systemd or upstart. Installed wily. Grabbed,extracted serviio from http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz Installed openjdk-8-jre. Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio- console.sh to run at start. Reboot using systemd,serviio starts. Reboot hangs for 90s. Kill java tasks associated with serviio - reboot takes place in time expected. Boot with upstart - reboot takes place in time expected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 219-9ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 19 18:19:40 2015 InstallationDate: Installed on 2015-05-12 (6 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456730] Re: Hangs on shutdown after installing and running serviio
I've found that the hang actually only occurs when serviio console is running. Just having running serviio - reboot works as expected. -- 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/1456730 Title: Hangs on shutdown after installing and running serviio Status in systemd package in Ubuntu: Confirmed Bug description: Ran serviio during the vivid cycle with no problem - either using systemd or upstart. Installed wily. Grabbed,extracted serviio from http://download.serviio.org/releases/serviio-1.5.2-linux.tar.gz Installed openjdk-8-jre. Set ~/serviio-1.5.2/bin/serviio.sh and ~/serviio-1.5.2/bin/serviio- console.sh to run at start. Reboot using systemd,serviio starts. Reboot hangs for 90s. Kill java tasks associated with serviio - reboot takes place in time expected. Boot with upstart - reboot takes place in time expected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 219-9ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 19 18:19:40 2015 InstallationDate: Installed on 2015-05-12 (6 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic root=UUID=6bcbfcc1-c493-4dbe-9421-ef270047a82a ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 835532] Re: lightdm does not keep numlock status on boot
that workround appears to be working here -- 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/835532 Title: lightdm does not keep numlock status on boot Status in LightDM GTK+ Greeter: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Oneiric: Won't Fix Bug description: when booting or logging out, the numlock status 'on' is not kept for password or pin input via numpad. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Sat Aug 27 12:22:27 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-08-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/835532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 835532] Re: lightdm does not keep numlock status on boot
following todays lightdm update - the workround to get numlock at login screen fails ** Tags added: wily xubuntu -- 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/835532 Title: lightdm does not keep numlock status on boot Status in LightDM GTK+ Greeter: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Oneiric: Won't Fix Bug description: when booting or logging out, the numlock status 'on' is not kept for password or pin input via numpad. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Sat Aug 27 12:22:27 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-08-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/835532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
