[Desktop-packages] [Bug 1902385] [NEW] At times I have an app. menu that opens and never closes
Public bug reported: It has happened twice in the last little bit where I opened a menu on an icon in the dock and the menu remains opened "forever" (until next reboot). Opening other menus from other icons in the dock works as expected. In most cases, the menu that's stuck is "transparent" to clicks, that is, when I try to click a menu item, the thing behind the menu gets clicked. When I'm able to click on an item in the menu (it turns orange when I do that successfully) then the mouse pointer is stuck over that item and that's it... nothing happens. Using Cmd-Tab to switch between windows waken the mouse up so I could use it again. I tried to restart the GDM3, the dock & menu came back as it was before the restart. sudo systemctl restart display-manager I tried once to Log Out (instead of rebooting) and the graphical interface didn't come back. I tried to restart the GDM from another computer (remotely through SSH) and the screen flashed a bit but it went right back to the boot console. So in other words the Log Out failed. Probably waiting on something that has a deadlock? The only way I've found to fix the issue is to reboot the computer (which I do not like to do too much... plus it takes about 3 min. with my monster server). See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon- menu-gets-stuck-open-any-way-to-fix-that-without-having-to ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:09:43 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Attachment added: "Sample of menu that was stuck earlier." https://bugs.launchpad.net/bugs/1902385/+attachment/5429843/+files/menu-stuck.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1902385 Title: At times I have an app. menu that opens and never closes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: It has happened twice in the last little bit where I opened a menu on an icon in the dock and the menu remains opened "forever" (until next reboot). Opening other menus from other icons in the dock works as expected. In most cases, the menu that's stuck is "transparent" to clicks, that is, when I try to click a menu item, the thing behind the menu gets clicked. When I'm able to click on an item in the menu (it turns orange when I do that successfully) then the mouse pointer is stuck over that item and that's it... nothing happens. Using Cmd-Tab to switch between windows waken the mouse up so I could use it again. I tried to restart the GDM3, the dock & menu came back as it was before the restart. sudo systemctl restart display-manager I tried once to Log Out (instead of rebooting) and the graphical interface didn't come back. I tried to restart the GDM from another computer (remotely through SSH) and the screen flashed a bit but it went right back to the boot console. So in other words the Log Out failed. Probably waiting on something that has a deadlock? The only way I've found to fix the issue is to reboot the computer (which I do not like to do too much... plus it takes about 3 min. with my monster server). See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon- menu-gets-stuck-open-any-way-to-fix-that-without-having-to ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:09:43 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1855489] Re: Chromium auto-restart feature breaks many features
*** This bug is a duplicate of bug 1616650 *** https://bugs.launchpad.net/bugs/1616650 Okay, another updated happened today (version 79.0.3945.79) and I can confirm that it creates the issue where I lose the dot under the Gnome icon. So bug $1616650 definitely looks like the solution to this problem. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: Incomplete Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I insist that changing the Download folder had no effects. That's not the issue in this case. Also, I could download files and they would go in my ~/Downloads folder as expected. No problem on that one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+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 1855489] Re: Chromium auto-restart feature breaks many features
Well, I can't really confirm whether it is a refresh (which I called auto-restart) after an auto-update or a an actual crash... but for sure the window does not change yet it gets disconnected from the Gnome Desktop (and that has happened many times now). At least I'll post to confirm that the history fails next time that happens and I'll check the versions to see whether it happens when an upgrade happens. However, the problem doesn't look like bug #1616650 in terms of functionality, the tabs all remain in place and work just fine without having to restart for many days after it gets disconnected from Gnome. That being said, the read-only folder (point 2) sounds like that could be part of the issue. I'm also not so sure that there was an update. I'll now pay attention to the exact version and see whether it changes next time the dot under the icon disappear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: Incomplete Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I
[Desktop-packages] [Bug 1855489] [NEW] Chromium auto-restart feature breaks many features
Public bug reported: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I insist that changing the Download folder had no effects. That's not the issue in this case. Also, I could download files and they would go in my ~/Downloads folder as expected. No problem on that one. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: auto-restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: New Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the
[Desktop-packages] [Bug 1079190] Re: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly
I got here because of a question asked on the Ubuntu stack here: https://askubuntu.com/questions/115333/how-do-i-disable-the-sleep- button-on-my-keyboard My keyboard Sleep button is right next to the Esc key. It's just too close and way to easy to end up clicking on it. It would be nicer to have the keys in the usual Keyboard Shortcuts window. It sounds like this should be an easy one since it's very much the same as the other keys... right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1079190 Title: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: My keyboard has a "sleep" button on it. I wish to reassign it to open a terminal rather than shut down my computer. To do so, I click on gnome-control-center -> keyboard -> shortcuts -> launchers -> Launch Terminal, then I press the "sleep" button on my keyboard. The "sleep" button appears to be properly assigned to run the terminal command. However, when I press the "sleep" button now, I would expect it to launch a terminal. Instead it puts the computer to sleep. Digging further, it appears that the power buttons on the computer (including those on the keyboard) are controlled by the following dconf settings: org.gnome.settings-daemon.plugins.power button-hibernate org.gnome.settings-daemon.plugins.power button-power org.gnome.settings-daemon.plugins.power button-sleep org.gnome.settings-daemon.plugins.power button-suspend If I use dconf-editor to set these values to 'nothing', then the "sleep" button on my keyboard opens the terminal as expected. The gnome-control-center keyboard shortcuts GUI does not disable the power settings for this button automatically for me. The gnome-control-center keyboard shortcuts GUI should know about and manage the org.gnome.settings-daemon.plugins.power button settings. It should allow the buttons to be re-assigned like other keyboard buttons. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Thu Nov 15 08:33:50 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2012-10-31 (14 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-11-01 (14 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1079190/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
I rebooted on Ubuntu 16.04 (4.4.0-142-generic) and it worked as expected once gpm was turned off. I used the following command to prevent gpm from starting on a reboot and messing up the login screen: sudo systemctl mask gpm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: New Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
I have the exact same problem on Ubuntu 16.04 (vmlinuz-4.4.0-142-generic). I will try to turn off GPM and see how my console functions without it. What a surprise though! Not being able to log in the simplest console. Not something I've seen in ages... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: New Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)
Sure, I don't think anyone has ever looked in this problem, unfortunately. Although "it works for me" now, doesn't mean it's fixed. That's all I'm saying. The code of Thunderbird is huge so I was never able to look enough through it and understand where the problem could be. Anyway, it can be closed since I'm good with the current version and now I make sure I keep compacting my folders... Thank you, Alexis -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/675673 Title: One junk email repeat thousand of times (until thunderbird is stopped) Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird It is the 3rd time that this happens. I do not know why it would happen, but at some point Thunderbird reads an email, decides that it is Junk mail, and moves it to the Junk folder. Then it repeats it over and over again until stopped by closing Thunderbird (the first time, it duplicated the email 5,501 times). When I restart Thunderbird, the problem doesn't repeat itself. I have used Thunderbird for some time now and it is only recently that this behavior started. It happened 3 times now and each time I can tell that it is one single email being duplicated over and over again. Since I do not know why it happens, I have no clue how to reproduce it. I was thinking that it could have something to do with my filters. If it is possible to export those, I'd be glad to post them here. Otherwise, Thunderbird connects to Postfix to download the emails and that works just fine. Just in case, I verified that the email wasn't duplicated on the server and sure enough it isn't. Thank you. Alexis ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.10+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-hostname 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-server x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Nov 15 10:03:14 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/675673/+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 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)
I don't recall having that bug happen to me for some time. However, it stops only because I understood what was causing some other problem. You have a feature called "Compact Folders" which is bogus and I think that when that other problem occurs, this very bug happens. I have had it with Thunderbird about 2 years ago (when I finally understood that I really had to compact folders.) The problem with compacting folders was that if a local file grows beyond 2Gb, its size is (most certain) viewed as being negative, which then prevents the auto-compaction from happen. As a result, the file continues to grow "forever"--or more precisely until it reaches 4Gb or whatever the limit is on your OS/Filesystem. Once that limit is reached, then you start seeing this very bug appearing. I guess something doesn't know how to get rid of that email and it the code generates an error on the save which tells another piece of code to try again and hence loops forever and adds new emails all the time. I'm pretty such that the file that caused the problem was the one representing the Junk folder on my Local Folders. When I deleted that file, the problems stopped and by making sure I run the compact folders once in a while, the size is kept in check. So, it's not fixed if that file size / compact test is not fixed. Actually, compact should become mandatory once the file is over 1Gb. Who needs that much data in emails?! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/675673 Title: One junk email repeat thousand of times (until thunderbird is stopped) Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird It is the 3rd time that this happens. I do not know why it would happen, but at some point Thunderbird reads an email, decides that it is Junk mail, and moves it to the Junk folder. Then it repeats it over and over again until stopped by closing Thunderbird (the first time, it duplicated the email 5,501 times). When I restart Thunderbird, the problem doesn't repeat itself. I have used Thunderbird for some time now and it is only recently that this behavior started. It happened 3 times now and each time I can tell that it is one single email being duplicated over and over again. Since I do not know why it happens, I have no clue how to reproduce it. I was thinking that it could have something to do with my filters. If it is possible to export those, I'd be glad to post them here. Otherwise, Thunderbird connects to Postfix to download the emails and that works just fine. Just in case, I verified that the email wasn't duplicated on the server and sure enough it isn't. Thank you. Alexis ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.10+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-hostname 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-server x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Nov 15 10:03:14 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/675673/+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 1720908] [NEW] Firefox cannot load Flash because of libxul broken dependency
Public bug reported: When I start Firefox version 56 in my console and then go to a page using Adobe Flash, I get the following errors: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (94): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (41): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Each time the problem is the same: gdk_screen_get_monitor_workarea is undefined. Gnome marked that function as deprecated, but Firefox version 55 worked just fine, whereas Firefox 56 fails with Flash. https://developer.gnome.org/gdk3/stable/GdkScreen.html#gdk-screen-get- monitor-workarea ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexis24733 F pulseaudio /dev/snd/controlC0: alexis24733 F pulseaudio BuildID: 20170928135459 Channel: Unavailable CurrentDesktop: Unity Date: Mon Oct 2 17:05:32 2017 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2010-12-27 (2471 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-33216e86-e3b0-440b-a25a-2754b1171002 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20170928135459 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-05-20 (500 days ago) dmi.bios.date: 09/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P55A-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1720908 Title: Firefox cannot load Flash because of libxul broken dependency Status in firefox package in Ubuntu: New Bug description: When I start Firefox version 56 in my console and then go to a page using Adobe Flash, I get the following errors: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (94): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (41): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Each time the problem is the same: gdk_screen_get_monitor_workarea is undefined. Gnome marked that function as deprecated, but Firefox version 55 worked just fine, whereas Firefox 56 fails with Flash.
[Desktop-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
There is information about KWallet. https://wiki.archlinux.org/index.php/KDE_Wallet It is marked as optional because it is allowed to fail as it does when you are running with Gnome (unity uses Gnome by default). So this is not a bug. You make comment out the lines as shown in #19 but you may regret it if you switch to KUbuntu one day... -- 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/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) 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/1309535/+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 1250814] Re: CCSM fails to read current Desktop Size values
*** This bug is a duplicate of bug 1294341 *** https://bugs.launchpad.net/bugs/1294341 The Desktop Size is still affected. But the command: gsettings get org.compiz.core:/org/compiz/profiles/unity/plugins/core/ hsize Seems to work for me. I currently use 2x2 and the command lines give me 2 and 2 as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1250814 Title: CCSM fails to read current Desktop Size values Status in Compiz: In Progress Status in “compiz” package in Ubuntu: In Progress Bug description: Version: Ubuntu 13.10 64-bits Opening the General Options - Desktop Size tab of CompizConfig Settings Manager (CCSM) does not display the (correct) current values for Horizontal-, Vertical Virtual Size and Number of Desktops. The Horizontal Virtual Size is displayed as 1 irrespecitive of the actual value. And worse, just visiting this Desktop Size tab page sets the Horizontal Virtual Size to this unintended value of 1 even if this field is not touched. Not a big problem of course if you are aware of this behavior but it can lead to unexpected changes in workspace settings if you are not. Reproduction: I ran into this problem after installation 13.10. Easiest reproduction however is from a very clean starting point: - create a bootable USB stick following the instructions of http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows - boot the USB stick and select 'Try Ubuntu' - install CompizConfig Settings Manager with Ubuntu Software Center - run CompizConfig Settings Manager and select General Options - Desktop Size ( Not sure if this is the right place to report this problem. Sorry for that) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1250814/+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 1294341] Re: Some of the input fields are blank in CompizConfig Settings Manager
I suppose this was not back ported to 13.10, correct? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1294341 Title: Some of the input fields are blank in CompizConfig Settings Manager Status in Compiz: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Bug description: [Impact] Users trying to use Compiz Config Settings Manager (CCSM) cannot see some of the fields' values. Also, due to this issue, some values will automatically reset to a value not set by the user. This can cause much user frustration when trying to set values in CCSM and can cause behaviors not intended by the user. [Test Case] To reproduce: * Open CCSM by either typing ccsm in the command line or finding it in the Dash. * Browse different settings and notice some of the values are missing in the input boxes. For example, General Options-Edge Trigger Delay is blank. [Regression Potential] None identified. Original Description: Input fields of some of the parameters in CompizConfig Settings Manager are blank. It is possible to modify them by typing a value or by pressing up/down buttons next to the input field. But leaving the particular plugin and returning back leads to the input fields being blank again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compizconfig-settings-manager 1:0.9.11+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 19 00:14:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-01-27 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) MachineType: TOSHIBA Satellite U400 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=ade20c72-1376-4808-b6fb-4b0c1cdba8c8 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V3.00 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV3.00:bd07/12/2008:svnTOSHIBA:pnSatelliteU400:pvrPSU40E-02000FRU:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40E-02000FRU dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 18 23:43:31 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14145 vendor SEC xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294341/+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 967091] Re: Wrong tint in flash when it uses video acceleration
I had that problem on one of my computers where I installed the CUDA development system. The CUDA installs its own libraries and the libvdpau_nvidia.so library was not getting used! I used the following command to remove the offensive vdpau library: sudo rm /usr/lib/libvdpau.so /usr/lib/libvdpau.so.1 /usr/lib/libvdpau.so.304.54 /usr/lib/libvdpau_trace.so Then I restarted my browser and it worked like a charm. You should have another library named: /usr/lib/libvdpau_nvidia.so If not, then you probably will have problems... FYI, I had CUDA installed with: cuda_5.0.35_linux_64_ubuntu11.10-1.run When running 12.04 and it worked fine. When I upgraded to 13.04 I decided to remove CUDA for the time being and still had that color problem. I found the solution (a mention of that library) from this Adobe bug report: https://bugbase.adobe.com/index.cfm?event=bugid=3109467 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/967091 Title: Wrong tint in flash when it uses video acceleration Status in Adobe Flash Plugin Tools: New Status in VDPAU vendor-independent libraries: Fix Released Status in “adobe-flashplugin” package in Ubuntu: Won't Fix Status in “apparmor” package in Ubuntu: Invalid Status in “libvdpau” package in Ubuntu: Fix Released Status in “adobe-flashplugin” source package in Precise: Won't Fix Status in “apparmor” source package in Precise: Fix Released Status in “libvdpau” source package in Precise: Fix Released Status in “adobe-flashplugin” source package in Quantal: Won't Fix Status in “apparmor” source package in Quantal: Invalid Status in “libvdpau” source package in Quantal: Fix Released Status in “adobe-flashplugin” source package in Raring: Won't Fix Status in “apparmor” source package in Raring: Invalid Status in “libvdpau” source package in Raring: Fix Released Status in “flashplugin-nonfree” package in Debian: New Bug description: Using Ubuntu 11.10 64 bit, nvidia binary driver, youtube videos show blue faces after the upgrade to flashplugin 11.2. Didn't occur with 11.1. See example at: http://i.imgur.com/S58GP.jpg SRU description [IMPACT] * Flash videos have the wrong tint (blue faces) on Precise when using nvidia-current or nvidia-current-updates. * This effectively renders Flash videos unwatchable for all LTS users with an NVidia video card. [TESTCASE] * Install nvidia-current, view any Flash video on YouTube, eg. https://www.youtube.com/watch?v=dkVBXW4JeUI. * Reproducable with various Nvidia video cards from at least the GeForce 8 series up to the GeForce 600 series. * Screenshot included in Aloysius' original bug description. [Regression Potential] * While Stephen Warren's patch is not exactly a one-liner, it is rather straightforward and only changes libvdpau's behaviour for Flash. * On the off-chance that this change causes instability, it can be easily disabled via vdpau_wrapper.cfg. * The patch is widely tested, is included in upstream since 0.5 and has been backported for 0.4.1 by the Debian team. The fix is included in Quantal (0.4.1-6ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/967091/+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 1230172] Re: gnome-calculator menu unreachable when global menu is off
I have the same problem. I cannot use the global menus because I setup my X environment to focus the window my mouse goes over. That really does not work with global menus since I lose those menus as soon as I move the mouse over another window (although Atl-F10 can help, it's not easy to type that one!) So... the gnome-calculator is reduced to a totally unusable simplistic calculator! And there are no command line options from what I can see that would allow me to change the settings. However, as a temporary solution, if we could change the current settings and get a better rendering, it would be great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1230172 Title: gnome-calculator menu unreachable when global menu is off Status in “gnome-calculator” package in Ubuntu: New Bug description: The Ubuntu's new Enhanced Menu project[1] aims to add the option of choosing whether you want the Global menu or not. Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be missing the indicator-appmenu (and dependencies). And without those, there was no global menu. That wasn't a problem for me, until I found out that I couldn't put the gnome-calculator back into PROGRAMMING mode because it had no menu to do so [2]. I tried to hack around a bit in the code, but I didn't get very far. See patch attempt in [2]. Kind regards, Walter Doekes OSSO B.V. [1] https://bugs.launchpad.net/unity/+bug/682788 [2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1230172/+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
