[Desktop-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled
Same issue. The workaround in #6 solve it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1805666 Title: Evolution Alarm Notify continues pop-up reminders even though notifications disabled Status in evolution-data-server package in Ubuntu: Invalid Bug description: I have turned off notifications for evolution alarm notify in settings: https://i.imgur.com/BNlfgzA.png But I still get pop-ups from the evolution alarm notify app for calendar events: https://i.imgur.com/BBdr9gm.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 28 11:31:46 2018 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2018-07-14 (136 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042423] Re: openConnection: connect: No such file or directory
Also in 16.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1042423 Title: openConnection: connect: No such file or directory Status in lightdm package in Ubuntu: Confirmed Bug description: I found the line openConnection: connect: No such file or directory in my .xsession_errors file and did a search for it. At the end of that thread it was suggested to report a new bug with the command ubuntu- bug lightdm and so I did. I am having problems with 12.04.1 not running in 3d mode. System upgrader. Computer system: Dell E4310 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Mon Aug 27 22:57:48 2012 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: LC_TIME=en_GB.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-08-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1042423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 156201] Re: gedit handles opening big files badly
Same issue on Ubuntu 16.10. REALLY??? 10 years and it's still happening this issue??! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/156201 Title: gedit handles opening big files badly Status in gedit: Confirmed Status in gedit package in Ubuntu: Triaged Bug description: Binary package hint: gedit Opening big text files (400 MB, 750 MB) in gedit is bad - from a usability standpoint -> There's no progress bar or cancel button for the action, and the load takes a long time. - from a system standpoint: -> In earlier versions, gedit would take so much memory until the system swapped all other applications to disk, and the system became unusable. -> Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but the message "failed to allocate bytes" in the console. Original description: I just opened a 400 MB text file (mbox mail file) in gedit, and it my system has now been unresponsive for minutes. Other editors can open large files without a problem. Also, there's no progress bar or cancel button that would make it easy to see how long gedit is loading the file or to cancel the load. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
Hi! I can confirm that the issue appears when the 'Access your Google Calendar' option is on. Alberto, do you need a new bug to be filled when it seems to be a regression? Regards... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu: Fix Released Status in account-plugins source package in Quantal: Fix Released Status in signon-plugin-oauth2 source package in Quantal: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Fix Released Status in signon-plugin-oauth2 source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
Still happening in 16.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu: Fix Released Status in account-plugins source package in Quantal: Fix Released Status in signon-plugin-oauth2 source package in Quantal: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Fix Released Status in signon-plugin-oauth2 source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp