[Bug 896595] Re: Ubuntu does not remember LID brightness

2014-08-13 Thread Pierre Equoy
P.S.: it looks like there was a similar issue in earlier versions of Ubuntu, but a fix was released... I don't know if this issue is related: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137598 -- You received this bug notification because you are a member of Ubuntu

[Bug 896595] Re: Ubuntu does not remember LID brightness

2014-08-13 Thread Pierre Equoy
The problem still happens with Ubuntu 14.04. I'm using an Asus K43SD (Intel® Pentium(R) CPU B970 @ 2.30GHz × 2 and GeForce 610M/PCIe/SSE2 GPU). Steps to reproduce: 1. Using Settings Brightness Lock (or Brightness Indicator

[Bug 1588266] [NEW] Almost no info about Krita snap in Ubuntu Software

2016-06-02 Thread Pierre Equoy
Public bug reported: Krita 3.0 was released [1] and it was packaged as a snap which is available in Ubuntu Software. However, when a user looks for "krita" in Ubuntu Software, (s)he will find one package without an icon, without screenshots, without user reviews... and with a scary "non-free"

[Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

2019-09-30 Thread Pierre Equoy
$ sudo lshw -C video *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 04 width: 64 bits

[Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

2019-09-30 Thread Pierre Equoy
Upstream issue opened here: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1736 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1736 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1736 -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

2019-09-30 Thread Pierre Equoy
@Daniel, I couldn't reproduce this issue on Wayland. However, I can reproduce it in the login screen (see attached snapshot). ** Attachment added: "osk-login.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845623/+attachment/5292981/+files/osk-login.jpg -- You received this

[Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

2019-09-30 Thread Pierre Equoy
Update: I can reproduce this also on the "Ubuntu on Wayland" session: 1. Open gedit and position the window somewhere in the middle-bottom of the screen 2. Swipe the touchscreen up to open OSK 3. Press the arrow down key on the OSK to hide the keyboard. → sometimes, two black rectangles remain

[Bug 1845601] Re: Images blurry in Background selection screen when scaling > 100%

2019-09-27 Thread Pierre Equoy
** Attachment added: "scaling300.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845601/+attachment/5291696/+files/scaling300.png ** Description changed: - Image: 19.10 beta (20190926.1) - Device: XPS 13 7390 + Image: 19.10 beta –

[Bug 1845601] Re: Images blurry in Background selection screen when scaling > 100%

2019-09-27 Thread Pierre Equoy
** Attachment added: "scaling200.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845601/+attachment/5291695/+files/scaling200.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in

[Bug 1845601] [NEW] Images blurry in Background selection screen when scaling > 100%

2019-09-27 Thread Pierre Equoy
Public bug reported: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce: 0. Go to Settings > Devices > Displays and make sure the scaling is 200% or more 1. Go to Settings > Background Expected

[Bug 1845623] [NEW] on screen keyboard leaves dark marks on screen after being hidden

2019-09-27 Thread Pierre Equoy
Public bug reported: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce: 1. Make the on-screen keyboard appear by tapping on a text field on doing a swipe up on the screen with your finger (see

[Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

2019-09-27 Thread Pierre Equoy
** Attachment added: "osk-issue.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845623/+attachment/5291740/+files/osk-issue.mp4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

2019-11-17 Thread Pierre Equoy
** Attachment added: "pactl_list_before_switching_output_device_back_and_forth.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log -- You received this bug notification because you are

[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

2019-11-17 Thread Pierre Equoy
** Attachment added: "pactl_list_after_switching_output_device_back_and_forth.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log -- You received this bug notification because you are a

[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

2019-11-17 Thread Pierre Equoy
I ran the following steps: 1. Power laptop on with bluetooth turned off 2. Turn BT on in gnome settings and set my BT headphones in pairing mode 3. Pair the headphones. 4. In Sound settings, it looks like the selected device is the BT headphones, but if I play something it outputs on the laptop

[Bug 1871536] Re: "Ubuntu Software" icon absent from dash after installing 20.04 beta

2020-04-08 Thread Pierre Equoy
** Tags added: ce-qa-concern -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871536 Title: "Ubuntu Software" icon absent from dash after installing 20.04 beta To manage

[Bug 1871536] [NEW] "Ubuntu Software" icon absent from dash after installing 20.04 beta

2020-04-08 Thread Pierre Equoy
Public bug reported: Ubuntu: 20.04 (beta image) Summary === After a fresh install, the "Ubuntu Software" icon is absent from the dash. To find it, user has to click "Show Applications" at the bottom left and search for "Ubuntu Software". Steps to reproduce == 1. Install

[Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store

2020-04-06 Thread Pierre Equoy
Installed focal fossa beta this morning on a XPS 13 (9300), and facing the same issue. The first thing I usually do is to install GNOME Tweaks, and this doesn't show in Snap Store. Tried snap-store rev336 (installed by default) and rev344 (from edge channel): same result. -- You received this

[Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses

2020-06-01 Thread Pierre Equoy
If that can be of any help, I have the following use case: In addition to the default Firefox launcher, I created two other .desktop files: - One called "Wayland Firefox #1" to run Firefox on Wayland with user profile #1 - The other called "Wayland Firefox #2" to run Firefox on Wayland

[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-06-02 Thread Pierre Equoy
Hi Salima, this bug has been identified as happening only for people who were upgrading from a previous version of Ubuntu (that came with a previous version of Pulseaudio). Daniel Van Vugt found a workaround (check comments 18 and 19 above), and a fix has been made by the Pulseaudio developers

[Bug 1935818] Re: Black screen if PAM session fails to initialize completely

2021-07-15 Thread Pierre Equoy
Verified OK on focal-proposed using gdm3 3.36.3-0ubuntu0.20.04.4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1935818 Title: Black screen if PAM session fails to initialize

[Bug 1967448] [NEW] All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-03-31 Thread Pierre Equoy
Public bug reported: Summary === Device with nvidia GPU, using proprietary drivers, wayland activated by default. By default, the scaling is set to 200% (the screen is UHD). If selecting 300%, all the windows close down, as well as the desktop icons (Home) as long as the mouse cursor is in

[Bug 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-03-31 Thread Pierre Equoy
You can clearly see what's going on in the attached video. ** Attachment added: "lp1967448_scaling300.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967448/+attachment/5575424/+files/lp1967448_scaling300.mp4 -- You received this bug notification because you are a member of

[Bug 1967450] [NEW] When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

2022-03-31 Thread Pierre Equoy
Public bug reported: Steps = - In Settings > Display, activate Fractional Scaling, and set it to 175%. - Deactivate fractional scaling and press Apply Expected results The screen goes back to 200% integer scaling Actual results == Only the upper left quarter

[Bug 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

2022-03-31 Thread Pierre Equoy
The video shows what happens when user is using 175% fractional scaling and then deactivate Fractional Scaling: - only the upper left part of the screen is used - a popup asks if user wants to keep or revert the changes - if user clicks Revert, it doesn't actually revert back to Fractional

[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

2022-03-31 Thread Pierre Equoy
Just for the record, I see the same issue with a Dell Precision 7760 (CID 202103-28858) when running 22.04 beta on Wayland. I was told the HDMI connector was wired directly to the Nvidia GPU, so gnome-shell crashes when I connect an external monitor there, but even after logging back in, the

[Bug 1959362] [NEW] "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy
Public bug reported: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy
** Attachment added: "lspci-k.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557896/+files/lspci-k.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy
** Attachment added: "journalctl_lastboot.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557897/+files/journalctl_lastboot.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy
After upgrading to the last version of the packages: gnome-shell41.3-1ubuntu1 mutter-common 41.3-1ubuntu1 the issue is gone and I can see the option when right-clicking on a desktop launcher. ** Changed in: oem-priority Status: