[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

2020-09-04 Thread cg
I have AMD graphics, and I'm affected by this too.

Ubuntu 20.04.1 LTS
AMD Ryzen 5 3500U
Radeon Vega 8

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2020-08-27 Thread cg
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1809092

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2020-08-27 Thread cg
Sorry, I am new to using launchpad and marked it the status incorrectly.

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1809092

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1176319] Re: gedit automatically detected character encoding in open file dialog box

2013-05-05 Thread cg
Hi,

I have filed a new bug as you instructed with id 699697.
https://bugzilla.gnome.org/show_bug.cgi?id=699697

Thank you.


On Sat, May 4, 2013 at 11:21 PM, Sebastien Bacher seb...@ubuntu.com wrote:

 Thank you for taking the time to report this bug and helping to make
 Ubuntu better. The issue you are reporting is an upstream one and it
 would be nice if somebody having it could send the bug to the developers
 of the software by following the instructions at
 https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
 tell us the number of the upstream bug (or the link), so we can add a
 bugwatch that will inform us about its status. Thanks in advance.

 ** Changed in: gedit (Ubuntu)
Importance: Undecided = Low

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1176319

 Title:
   gedit automatically detected character encoding in open file dialog
   box

 Status in “gedit” package in Ubuntu:
   New

 Bug description:
   Hello,

   In gedit's open file dialog box, there is an option for choosing the
   character encoding. The default option is Automatically Detected
   which I am afraid it doesn't always work.

   I am attaching a file (gr.srt) with encoding (Greek) ISO-8859-7. I
 verified its encoding using the chardet utility in the terminal and I am
 also attaching chardet.png that shows exactly this. If you open this file
 (gr.srt) with gedit and encoding auto detection and you leave your mouse
 over the respective file's tab, a hint will appear reporting the Western
 ISO-8859-15 as the detected encoding. Of course as a result, the file's
 content is unreadable. (Attached geditWrong.png)

   If you open the same file by choosing (Greek) ISO-8859-7 in the open
 file dialog box, the respective hint properly shows the correct encoding
 and the file is readable. (Attached geditCorrect.png).

   Bear in mind that once you have opened the file with ISO-8859-7, it
   will always open correctly even if you choose Automatically
   Detected. It seems that gedit remembers your option and doesn't
   actually try to detect the actual encoding. In order to reset to the
   initial problematic behavior, you have to manually select (Western)
   ISO-8859-15 once. It seems to me that it is very probable that this is
   another issue but yet related and it will also help you to not get
   confused in your tests.

   Finally, I would like to grab this opportunity and ask you to add an
   encoding choice in gedit's menu because in the open file dialog, it is
   quite hidden in the sense that most people open files by double
   clicking them. I even found this option on the net, it didn't even
   cross my mind that such an option would be available there. Also, I
   have found quite many frustration reports on the Internet from people
   who use non Latin alphabets, I have even found a bug report that was
   closed because the reporter unfortunately failed to provide the
   required evidence and instructions.

   Thank you very much.

   P.S
   Since I am only allowed to attach one file, note that all files I have
 mentioned are included in geditEncoding.tar.gz

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1176319/+subscriptions


-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1176319

Title:
  gedit automatically detected character encoding in open file dialog
  box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1176319/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1176319] Re: gedit automatically detected character encoding in open file dialog box

2013-05-05 Thread cg
** Bug watch added: GNOME Bug Tracker #699697
   https://bugzilla.gnome.org/show_bug.cgi?id=699697

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1176319

Title:
  gedit automatically detected character encoding in open file dialog
  box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1176319/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1176319] [NEW] gedit automatically detected character encoding in open file dialog box

2013-05-04 Thread cg
Public bug reported:

Hello,

In gedit's open file dialog box, there is an option for choosing the
character encoding. The default option is Automatically Detected which
I am afraid it doesn't always work.

I am attaching a file (gr.srt) with encoding (Greek) ISO-8859-7. I verified its 
encoding using the chardet utility in the terminal and I am also attaching 
chardet.png that shows exactly this. If you open this file (gr.srt) with gedit 
and encoding auto detection and you leave your mouse over the respective file's 
tab, a hint will appear reporting the Western ISO-8859-15 as the detected 
encoding. Of course as a result, the file's content is unreadable. (Attached 
geditWrong.png)
 
If you open the same file by choosing (Greek) ISO-8859-7 in the open file 
dialog box, the respective hint properly shows the correct encoding and the 
file is readable. (Attached geditCorrect.png).

Bear in mind that once you have opened the file with ISO-8859-7, it will
always open correctly even if you choose Automatically Detected. It
seems that gedit remembers your option and doesn't actually try to
detect the actual encoding. In order to reset to the initial problematic
behavior, you have to manually select (Western) ISO-8859-15 once. It
seems to me that it is very probable that this is another issue but yet
related and it will also help you to not get confused in your tests.

Finally, I would like to grab this opportunity and ask you to add an
encoding choice in gedit's menu because in the open file dialog, it is
quite hidden in the sense that most people open files by double
clicking them. I even found this option on the net, it didn't even cross
my mind that such an option would be available there. Also, I have found
quite many frustration reports on the Internet from people who use non
Latin alphabets, I have even found a bug report that was closed because
the reporter unfortunately failed to provide the required evidence and
instructions.

Thank you very much.

P.S
Since I am only allowed to attach one file, note that all files I have 
mentioned are included in geditEncoding.tar.gz

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: encoding gedit

** Attachment added: geditEncoding.tar.gz
   
https://bugs.launchpad.net/bugs/1176319/+attachment/3664642/+files/geditEncoding.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1176319

Title:
  gedit automatically detected character encoding in open file dialog
  box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1176319/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs