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
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
** 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.launchp
(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
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 e
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/+sou
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-doc
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 mee
*** 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
(htt
** 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-bac
** 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/
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
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
*** 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-backen
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
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://
16 matches
Mail list logo