[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
The accountsservice bug has now been closed as "RESOLVED FIXED", so if it does really fix the problem then we should backport the fix in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599295] Re: Apport should not just silently fail when it detects the specific crash report has already been uploaded
Really? Well, I'm certain that it always has done for me... So many times have I had it upload data to LP and where the error is set as the title for the report. Isn't this https://bugs.launchpad.net/ubuntu/+source/gnome- photos/+bug/1568043 what normally should happen? Or when does this happen and when does it just submit it somewhere else? Also, where exactly did it submit my report to? Shouldn't it have asked at least for my comment on exactly what I was doing at the time as the crash dump may not always be enough? Where can I access previous reports on Ubuntu GNOME? They don't seem to be in the same place. In fact I don't remember ever seeing them in the gnome-control-center. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1599295 Title: Apport should not just silently fail when it detects the specific crash report has already been uploaded Status in Apport: Invalid Status in apport package in Ubuntu: Invalid Bug description: I have recently been having some trouble with Apport, I asked it to submit a crash report however there was a problem and it never launched the browser page. Now every time I try to manually submit the .crash file I get an error saying that the crash report has been already submitted (this is logged in syslog and not anywhere obvious). When I use the GUI, and when I use the apport-cli program and ask it to submit a report now on the matter it just silently exists without telling me anything. So how am I even meant to know what the URL is that it has been submitted to? So I think that Apport should really not just silently fail and should instead tell the user that the crash has already been submitted and then actually give them the URL to get to it because otherwise I don't know how one is expected to find it unless they get the Apport's signature generator working manually or something. I am running Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1599295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599635] Re: Console font width should be consistent on startup
Ok, well: 1) Why didn't this issue affect anyone before? Did Linux simply not set a new one or anything different from the bold? 2) What about having a compromise and just allowing the user to configure what they want Linux to change the font to, if anything? That would do it for me if I could at least change it back to how it was and not have Linux changing it to something I can barely read and don't want. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1599635 Title: Console font width should be consistent on startup Status in Ubuntu GNOME: New Status in console-setup package in Ubuntu: New Bug description: When I start my machine the console output is shown (so no splash screen, just the console output about my system starting up), and I have noticed that since upgrading to 16.04 from 15.10 (and I noticed that this happened about half way through the upgrade process as well) that on every startup for the first 5 seconds or something the text is what I would describe as "bold", but then after that it suddenly becomes just "normal" and much thinner. In fact I find it harder to read in this thinner state and would much prefer the thicker one. So here is what I would like to see: 1. For the text width to be consistent throughout the startup (for it to either start off as bold and stay as bold, or start off as thin and stay as thin). 2. For the user to perhaps also be given the option to decide in their configuration whether or not they want the text to be thin or bold. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1599635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599635] Re: Console font width should be consistent at startup
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Console font width should be consistent at startup + Console font width should be consistent on startup -- 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/1599635 Title: Console font width should be consistent on startup Status in Ubuntu GNOME: New Status in systemd package in Ubuntu: New Bug description: When I start my machine the console output is shown (so no splash screen, just the console output about my system starting up), and I have noticed that since upgrading to 16.04 from 15.10 (and I noticed that this happened about half way through the upgrade process as well) that on every startup for the first 5 seconds or something the text is what I would describe as "bold", but then after that it suddenly becomes just "normal" and much thinner. In fact I find it harder to read in this thinner state and would much prefer the thicker one. So here is what I would like to see: 1. For the text width to be consistent throughout the startup (for it to either start off as bold and stay as bold, or start off as thin and stay as thin). 2. For the user to perhaps also be given the option to decide in their configuration whether or not they want the text to be thin or bold. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1599635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599295] Re: Apport should not just silently fail when it detects the specific crash report has already been uploaded
Related: Bug #1599297 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1599295 Title: Apport should not just silently fail when it detects the specific crash report has already been uploaded Status in Apport: New Status in Ubuntu GNOME: New Status in apport package in Ubuntu: New Bug description: I have recently been having some trouble with Apport, I asked it to submit a crash report however there was a problem and it never launched the browser page. Now every time I try to manually submit the .crash file I get an error saying that the crash report has been already submitted (this is logged in syslog and not anywhere obvious). When I use the GUI, and when I use the apport-cli program and ask it to submit a report now on the matter it just silently exists without telling me anything. So how am I even meant to know what the URL is that it has been submitted to? So I think that Apport should really not just silently fail and should instead tell the user that the crash has already been submitted and then actually give them the URL to get to it because otherwise I don't know how one is expected to find it unless they get the Apport's signature generator working manually or something. I am running Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1599295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599297] [NEW] One should be able to request the URL for a specific crash report
Public bug reported: As I said in Bug #1599295, when one submits a crash report and it for some reason fails to open a browser tab/window with the reporting bit one is unable to find the URL to go to as Apport just silently fails (though does log something to syslog). So I think that as well as the other bug being fixed, it would be really good if one could specify a crash signature or a .crash file and then ask Apport to provide the URL to the uploaded contents where one can then properly report the crash in question (perhaps this could be done by a command-line option or something). I am running Ubuntu GNOME 16.04 with GNOME 3.20. ** Affects: apport Importance: Undecided Status: New ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1599297 Title: One should be able to request the URL for a specific crash report Status in Apport: New Status in Ubuntu GNOME: New Status in apport package in Ubuntu: New Bug description: As I said in Bug #1599295, when one submits a crash report and it for some reason fails to open a browser tab/window with the reporting bit one is unable to find the URL to go to as Apport just silently fails (though does log something to syslog). So I think that as well as the other bug being fixed, it would be really good if one could specify a crash signature or a .crash file and then ask Apport to provide the URL to the uploaded contents where one can then properly report the crash in question (perhaps this could be done by a command-line option or something). I am running Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1599297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599295] [NEW] Apport should not just silently fail when it detects the specific crash report has already been uploaded
Public bug reported: I have recently been having some trouble with Apport, I asked it to submit a crash report however there was a problem and it never launched the browser page. Now every time I try to manually submit the .crash file I get an error saying that the crash report has been already submitted (this is logged in syslog and not anywhere obvious). When I use the GUI, and when I use the apport-cli program and ask it to submit a report now on the matter it just silently exists without telling me anything. So how am I even meant to know what the URL is that it has been submitted to? So I think that Apport should really not just silently fail and should instead tell the user that the crash has already been submitted and then actually give them the URL to get to it because otherwise I don't know how one is expected to find it unless they get the Apport's signature generator working manually or something. I am running Ubuntu GNOME 16.04 with GNOME 3.20. ** Affects: apport Importance: Undecided Status: New ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1599295 Title: Apport should not just silently fail when it detects the specific crash report has already been uploaded Status in Apport: New Status in Ubuntu GNOME: New Status in apport package in Ubuntu: New Bug description: I have recently been having some trouble with Apport, I asked it to submit a crash report however there was a problem and it never launched the browser page. Now every time I try to manually submit the .crash file I get an error saying that the crash report has been already submitted (this is logged in syslog and not anywhere obvious). When I use the GUI, and when I use the apport-cli program and ask it to submit a report now on the matter it just silently exists without telling me anything. So how am I even meant to know what the URL is that it has been submitted to? So I think that Apport should really not just silently fail and should instead tell the user that the crash has already been submitted and then actually give them the URL to get to it because otherwise I don't know how one is expected to find it unless they get the Apport's signature generator working manually or something. I am running Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1599295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
It should also be noted that this issue does not seem to affect gnome- shell areas, that is it is not seemingly present in the Activities Overview nor the Top Bar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Unknown Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
Upstream said it's likely to be a driver problem, where should I report this issue then? And is there any way to reload the driver or something to fix this issue without having to completely restart the machine as it is a bit annoying? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Unknown Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
This issue has now occurred again after awakening from a suspend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Unknown Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Changed in: accountsservice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
Oh, oh dear, so I'm guessing the upstream bug should be reopened then? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Confirmed Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
Actually, I remember when the bug occurred going into the gnome-tweak- tool and changing the theme as well as turning the dark theme off. But neither change made any difference to the fonts problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Confirmed Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Description changed: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. - I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and - Ubuntu GNOME 15.10 with GNOME 3.18. + I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, + Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME + 3.20. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Confirmed Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
It seems as though the GNOME upstream change if applied to the 'unity- control-center' will also fix the problem as it is the same file, same code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Confirmed Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and Ubuntu GNOME 15.10 with GNOME 3.18. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
I will test it and get back to you when it next occurs, but Firefox doesn't use the dark theme, it simply refuses as Mozilla decided not to get it to use it. And that's where I first noticed the issue so does that count? ** Changed in: ubuntu-gnome Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Confirmed Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend
** Bug watch added: GNOME Bug Tracker #768115 https://bugzilla.gnome.org/show_bug.cgi?id=768115 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=768115 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Unknown Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596698] Re: Strange font issue after awake from suspend
** Attachment added: "Settings_Text_Issue.png" https://bugs.launchpad.net/ubuntu-gnome/+bug/1596698/+attachment/4691289/+files/Settings_Text_Issue.png ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Strange font issue after awake from suspend + Strange font issue after awakening from suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1596698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1592177] Re: Built-in search almost impossible to use in GTK file chooser
Right, sorry, I was having some issues connecting to the upstream bugzilla, but all sorted now. ** Bug watch added: GNOME Bug Tracker #767736 https://bugzilla.gnome.org/show_bug.cgi?id=767736 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=767736 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Built-in search almost impossible to use in GTK file chooser Status in GTK+: Unknown Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
