[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
Thanks for helping me disable the extensions. The bug report at gnome gitlab is here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2905 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2905 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2905 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: New Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
The folder was completely empty (I checked with ls -lsah) but I deleted it anyway and restarted. gsettings list-recursively org.gnome.shell > settings.txt however still produces the same output. I guess that some of those "residue" gnome extensions might be causing the bug I reported however I am now more concerned that there seemingly extensions enabled that neither show up in the extensions settings nor in the extensions folder. Also shouldn't the default extensions be listed under "org.gnome.shell enabled-extensions" as well? Do you know where gsettings is pulling the list of enabled extensions from? Maybe I can dig down from there and get to the bottom of this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5383087/+files/settings.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
(Thanks to everyone who is taking the time out of their day to look into this.) I think I should note that I can't replicate this issue reliably. It happened "at random" and it didn't happen again since I filed this report. It's just that it wasn't the first time it happened and I saw others have similar issues. That is why I reported it. Again I want to preface that the extensions shown in the list are the once which came pre-installed with Ubuntu 18.04 (iirc) and I never touched them. (I have some indicator apps but I assume you don't mean them.) I also don't understand why I should disable stock Ubuntu extensions that provide basic functionality like the dock. Would you consider disabling the dock a solution or do you simply try to pin down the culprit? With that said I can explain the seemingly contractionary pictures. The gnome Tweaks app shows a wrong state. The extensions app shows the correct state. Screenshot attached. This must be a bug in gnome Tweaks. The gsettings file shows something interesting: According to the file I have two extensions active that I can't remember ever installing and that do not show up anywhere: org.gnome.shell enabled-extensions ['update-extensi...@franglais125.gmail.com', 'move_cl...@rmy.pobox.com'] File attached. Could it be that there are extensions active that I or someone living with me installed in the past but don't show up in the extensions settings? If yes how do I remove them for further bug testing? ** Attachment added: "Screenshot from 2020-06-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5383086/+files/Screenshot%20from%202020-06-11.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
The picture in the other issue does indeed look identical to the screen I had however it is a very different issue. 1. I update my system daily by hand. So my system was up to date and the fix of the other issue was installed days ago when my issue occurred. 2. The referenced bug happened after entering a password under certain circumstances. My issue however happened without entering any password whatsoever. I simply moved my mouse to remove fade to black and was presented with the situation as shown in the redacted_apps.png screenshot. Further differences: 3. I don't have automatic lockscreen set like in the referenced issue. 4. My Keyring is unlocked automatically after boot so there was no way that I had a dialogue active "behind" my lockscreen. 5. My lockscreen did unlock after the first time I entered my password. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
This is the log from when I returned to my pc and noticed the dock being accessible on the lock screen and it ends shortly before I actually unlock my pc. So everything you see in here happened while the lock screen was active. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5382120/+files/log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
I actually have no gnome extensions installed other than the ones that come preinstalled with Ubuntu. (Screenshot attached.) I also didn't change any settings concerning extensions. ** Attachment added: "extensions.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1882353/+attachment/5381771/+files/extensions.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/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1882353/+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 1857820] [NEW] e-cal-recur: Ignores recurrence exceptions
Public bug reported: Recurrence exceptions are no longer handled. That is, a recurring appointment is drawn on days that are supposed to be an exception to the recurrence rule. Imagine you have a meeting every Monday at 10 AM but the next meeting got cancelled. You want to remove the cancelled meeting from the calendar without removing all other past and future events. This is no longer possible with 3.34.1 due to a bug. This bug is known and fixed in upstream 3.34.2 however Ubuntu must backport it to the 3.34.1 version shipped with eaon. This is one of multiple upstream bug reports for this: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162 This is the patch for 3.34.x: https://gitlab.gnome.org/GNOME/evolution- data-server/commit/795a6f9f687122f6ce0bcfbf2c45bcd4a33f30a2 (There is a separate patch for 3.35.x but I assume this is not relevant for the current eaon version.) ** Affects: evolution-data-server Importance: Unknown Status: Unknown ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/issues #162 https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162 ** Also affects: evolution-data-server via https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162 Importance: Unknown Status: Unknown -- 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/1857820 Title: e-cal-recur: Ignores recurrence exceptions Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: New Bug description: Recurrence exceptions are no longer handled. That is, a recurring appointment is drawn on days that are supposed to be an exception to the recurrence rule. Imagine you have a meeting every Monday at 10 AM but the next meeting got cancelled. You want to remove the cancelled meeting from the calendar without removing all other past and future events. This is no longer possible with 3.34.1 due to a bug. This bug is known and fixed in upstream 3.34.2 however Ubuntu must backport it to the 3.34.1 version shipped with eaon. This is one of multiple upstream bug reports for this: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162 This is the patch for 3.34.x: https://gitlab.gnome.org/GNOME /evolution-data-server/commit/795a6f9f687122f6ce0bcfbf2c45bcd4a33f30a2 (There is a separate patch for 3.35.x but I assume this is not relevant for the current eaon version.) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1857820/+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 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200
*** This bug is a duplicate of bug 1731459 *** https://bugs.launchpad.net/bugs/1731459 Nope, there is only one model with one chip one the market. The chip is also identical to the CanoScan LiDE 100. (See Screenshot attached.) Please note that this bug is a duplicate of this bug #1731459 (https://bugs.launchpad.net/bugs/1731459) since all GL847 chip bases scanners are affected by this bug. It would be great if you could repost your findings in the main bug report since it is VERY interesting that you have different results with two devices of the same model and also with the more recent git-version of 1.0.27. ** Attachment added: "CanoScan 100/200 Chipset" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+attachment/5032189/+files/Selection_234.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10
** Summary changed: - On Ubuntu 17.10 genesys_gl847 scanners produce a black band in scanned images. + genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1731459 Title: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10 Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1731459] Re: On Ubuntu 17.10 genesys_gl847 scanners produce a black band in scanned images.
** Summary changed: - Black band in scanned images + On Ubuntu 17.10 genesys_gl847 scanners produce a black band in scanned images. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1731459 Title: On Ubuntu 17.10 genesys_gl847 scanners produce a black band in scanned images. Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1731459] Re: Black band in scanned images
Also I went through all changes made between 1.0.25 and 1.0.27 with regards to genesys in general and more specifically gl847 (which is the chip CanoScan LiDE 100 is using) looking for anything related to colour. The only thing I was able to find was this patch changing reallocation of gamma tables: https://anonscm.debian.org/cgit/sane/sane- backends.git/commit/backend/genesys.c?id=5edb87f9ac950473f8c3a57b4071c970887d8440 I'm no expert but this sounds promising and it's the best I can provide helping to fix this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1731459 Title: On Ubuntu 17.10 genesys_gl847 scanners produce a black band in scanned images. Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1731459] Re: Black band in scanned images
I did some testing with different colours. Maybe this helps to pinpoint what's actually going wrong. I also found an interesting correlation with this bug: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1712997 The visual artefacts are very similar however they are not in a straight line and they happen with the old driver (1.0.25) which is otherwise fine. What I wasn't able to confirm yet is if the current stable release of sane-backends 1.0.27 might fix this or not. There are many dependencies which make it impossible for me to replace libase1 with libsane. You can get it here if you are able to work around the dependency issue: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane- release?field.series_filter= btw: This also happens with CanoScan LiDE 200 btw. I marked the report for 200 as a duplicate of this report since yours was reported earlier. ** Attachment added: "color test" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+attachment/5027778/+files/image_error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1731459 Title: Black band in scanned images Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200
*** This bug is a duplicate of bug 1731459 *** https://bugs.launchpad.net/bugs/1731459 ** This bug has been marked a duplicate of bug 1731459 Black band in scanned images -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+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 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200
I did some testing with different colours. Maybe this helps to pinpoint what's actually going wrong. ** Attachment added: "Image Errors with different colors" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+attachment/5027670/+files/image_error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+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 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200
I have a CanoScan LiDE 100 but otherwise the exact same setup. I can fully confirm that this bug is caused by the new ibsane1 1.0.27-1~experimental packages and "fixed" by force replacing all sane packages with the 1.0.25 packages from Ubuntu 17.04. Somebody also posted this on askubuntu: https://askubuntu.com/questions/973526/thick-black-vertical-line-with- canon-lide-100-scanner-in-ubuntu-17-10 So there are multiple users affected indeed. What I wasn't able to confirm yet is if the current stable release of sane-backends 1.0.27 might fix this or not. You can get it here: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane- release?field.series_filter= I also found an interesting correlation with this bug: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1712997 This seems to happen also on the old drivers for this user but the visual artifacts are very similar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+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
