** Tags added: quantal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to indicator-weather in Ubuntu.
https://bugs.launchpad.net/bugs/856172
Title:
indicator-weather crashed with SIGSEGV in
dbusmenu_menuitem_build_variant()
Status in
I'm seeing this several times a day in Quantal. I'll try with Valgrind,
give me some time ..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/410534
Title:
gnome-settings-daemon is automatically respawning once killed, so I'm
not sure how to attach Valgrind to it (or how to stop it from
respawning). I'm searching the web for info, but if someone sees this
please drop me a hint to speed things up, thanks.
** Changed in: gnome-settings-daemon
I ran g-s-d through valgrind for 2 days now, and the issues seems to
have happened twice during the night, which is consistent with what I
though was my experience without valgrind as well. May have something to
do with turning off or locking the screen when the laptop is not in use
- there is
I forgot to mention that these logs are from one overnight run, I
discarded the logs from the first night.
** Tags added: amd64
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Desktop
** Attachment added: gnome-settings-daemon-with-valgrind-debug.log
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/410534/+attachment/3340540/+files/gnome-settings-daemon-with-valgrind-debug.log
--
You received this bug notification because you are a member of Desktop
Also somehow the dashes in front of the debug option where lost when
copying the valgrind command from the terminal. For the sake of
correctness her it is again, sorry for spam:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40
** Tags added: quantal
** Tags added: precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-volume-manager in Ubuntu.
https://bugs.launchpad.net/bugs/85291
Title:
filesystems are never fsck'ed if they live on removable USB
Public bug reported:
In bug #771757, the following is reported:
Using an Android device, Shotwell scans the entire directory for pictures. It
also picks up pictures used by apps. Whereas it should only pick up pictures
taken by the camera and sent by bluetooth.
(...)
As it is right now,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/860281
Title:
Always showing Open Shotwell button for SD Card storage can be
harmful
Status in “nautilus” package in Ubuntu:
New
** Description changed:
- In bug #771757, it is reported,
+ In bug #771757, the following is reported:
Using an Android device, Shotwell scans the entire directory for pictures.
It also picks up pictures used by apps. Whereas it should only pick up pictures
taken by the camera and sent by
Thanks for the quick reply. I agree that working around the problem in
Nautilus would be awkward.
In comment #2 of the Shotwell bug #771757 there is some background info
taken from the upstream reports (and links to those reports). It seems
that the problem really is in gPhoto and Android.
Recently I had to support an Ubuntu-using friend whose external FAT disk
was not mounting because it had previously been unplugged without
unmounting. I told him repeatedly about the need to unmount, but
sometimes he still forgets or it just happens by accident. This is a
casual user who does not
I just reported bug #855080 (which was immediately marked as a
duplicate). I can reproduce the issue as follows:
1. Start Language Support control center applet.
2. It tells me that thunderbird-locale-en-us and thunderbird-locale-en are not
installed and if I want to install them now or be
Re my previous comment #3: This is on up-to-date Oneiric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/713346
Title:
gnome-language-selector crashed with
*** This bug is a duplicate of bug 713346 ***
https://bugs.launchpad.net/bugs/713346
** Description changed:
Started Language Support control center applet.
- It told me that some Thunderbird language files are not installed and if I
wanted to install them now or be reminded later - I
An alternative but similar reproduction (also involving Cancel on the
password screen) is given in bug #758036 (duplicate of this one)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
I'm the OP and it works again for me in Oneiric without the xorg.conf
option. Same MacBook Pro 5.3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/726692
Title:
Screen
Damn, sorry, it's not fixed for me after all. Once again I got fooled by
the bubble appearing - but without the option, the brightness does not
change. This is all in an installed Oneiric by the way, I will try to
test with a live CD.
--
You received this bug notification because you are a
This is still the same in a new install of Quantal (and IIRC it also
was the same in Precise. However, I had not made a reinstall of Precise,
but upgraded from Oneiric, so I didn't have to actually do anything to
make it work, and therefore I am not sure)
** Tags added: quantal
** Changed in:
Public bug reported:
When you hold the Super key and the overlay with the keyboard shortcut
opens:
Under Workspaces it says:
Ctrl + Alt + Left + Arrow Keys: Switches Workspaces
Shift + Ctrl + Alt + Left + Arrow Keys: Moves focused window to another
workspace
The shortcuts are wrong, the +
I can confirm that the update fixed the problem.
** Changed in: unity (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
Public bug reported:
Both issues are fixed in 1.10.5
http://sourceforge.net/p/liferea/bugs/1098/
http://sourceforge.net/p/liferea/bugs/1089/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: liferea 1.10.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux
As this machine is a MacBook Pro, I use the icc file copied from OS X.
Attached.
** Attachment added: icc file
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1325673/+attachment/4124292/+files/Color%20LCD-0610--9CB1--04272C40.icc
--
You received this bug
Public bug reported:
Added a color profile as an .icc file to System Settings Color.
The choice is accepted and the screen color changes.
However, apparently the choice does not get saved: every time I log out I need
to apply the choice again.
I have used a color profile since 2009 in all
Ah! The log always contains as the only entry:
(unity-settings-daemon:13702): color-plugin-WARNING **: failed to
connect to device: Failed to connect to missing device
/org/freedesktop/ColorManager/devices/cups_Hewlett_Packard_HP_LaserJet_Professional_P_1102w
I have a printer of that type (color
I'm not using Wayland but X though, would it still be libinput?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1764097
Title:
'Apple touchpad bcm5974' is
Oh and is there a link to your upstream report, mailing list, or
similar? Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1764097
Title:
'Apple touchpad
In my defense, the second paragraph seems to say that filing against
xserver-xorg-input-synaptics is ok and bug triagers would assign it as
needed. I really tried :) Thank you
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Indeed, running "sudo libinput debug-events --verbose" results in:
event6 POINTER_MOTION +11.04s5.07/ -9.23
event6 POINTER_MOTION +11.05s 16.95/ -2.91
event6 POINTER_MOTION +11.06s 13.15/ -4.05
event6 - palm: touch size exceeded
event6 - palm: palm detected
** Tags added: cosmic
--
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/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
Status in caribou package in
** Tags added: cosmic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1720089
Title:
Desktop isn't part of "places" (left bar) in artful
Status in nautilus package in Ubuntu:
Still the same in Cosmic. In the upstream bug it does not seem that they
want to add it back by default (as expected really), so I'd think it's
up to Ubuntu if files on desktop remain in contrast to upstream.
"António Fernandes @antoniof · 8 months ago
Developer
The Desktop folder should become
I still have the same machine (upgraded/reinstalled to each Ubuntu
version since) and the problem has not happened in agesa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
Same for me on Cosmic 18.10, fresh install and up to date. I works in X
session.
I can repro it also with a single file.
nautilus version 1:3.26.4-0ubuntu3
** Tags added: cosmic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The Ubuntu help for 18.04 says that you need to activate it in the
Accessibility settings, and "When you next have the opportunity to type, the
on-screen keyboard will open at the bottom of the screen."
https://help.ubuntu.com/stable/ubuntu-help/keyboard-osk.html
Neither is true for me:
1. I
I notice that the release notes for Gnome 2.28 say "The new keyboard
automatically activates when a text area is selected". If this worked,
no activation button would be needed as far as I can tell, and I suppose
this is why there is none. However as I said in my previous comment this
is not the
Gnome 2.28 release notes: https://help.gnome.org/misc/release-
notes/3.28/
--
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/1760399
Title:
New On-screen keyboard cannot be manually
It seems to me that either the bug title is overly specific or the issue is
slightly different with Gnome 3.30 in Cosmic.
In Cosmic it happens for single files as well, but only when dragging between
desktop and a nautilus window. It's fine to drag between nautilus windows, and
you can drag
There is an extension to show a panel button to trigger it:
https://extensions.gnome.org/extension/1061/on-screen-keyboard-button/
Unfortunately, its panel button itself does not react to touch at least
for me (on Cosmic, Gnome 3.30, Wayland), which kind of defeats the
purpose
That said, in
** Tags added: cosmic
** Tags removed: highdpi
** Tags added: highdpii
** Tags removed: highdpii
** Tags added: highdpi
--
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/1687246
** Tags added: touch universalaccess
--
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/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
Status in
Just realized that Gnome 3.30 and/or the new theme in Cosmic shows all
"Places" icons in black & white, so bookmarking makes no difference to
this. Though the inconsistency with the colorful icon in the Home folder
remains
--
You received this bug notification because you are a member of Desktop
So after much hair pulling I contacted the author of the above mentioned
Gnome extension and he set me on the right track (thank you):
1. Auto-summon of OSK only works with application/toolkit support. Text
widgets in alien (non-Gnome or non-Gtk?) toolkits don't summon the OSK
(Gnome, Firefox,
Duh. In the above comment, it should have been:
"1. (**Chrome** [not Gnome], Firefox, Qt, whatever other toolkits...)
--
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/1760399
Title:
** Tags removed: universalaccess
--
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/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
Status in caribou
Bug report for Ubuntu documentation:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548
--
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/1760399
Title:
New
Public bug reported:
The new OSK does not auto-activate reliably by selecting any text widget as the
Gnome 3.28 release notes claim:
"The new keyboard automatically activates when a text area is selected, ..."
-- https://help.gnome.org/misc/release-notes/3.28/
This does not work with text
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1740599
Title:
Selecting multiple files and dragging them to file manager is broken
in a Wayland
Bug report for discoverability:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551
--
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/1760399
Title:
New On-screen
** Description changed:
- The docs give an incorrect description:
+ The docs give an incorrect or at least incomplete and misleading
+ description:
"The on-screen keyboard is automatically enabled if you use a touchscreen
1. Open the Activities overview and start typing Universal Access.
** Description changed:
The new OSK does not auto-activate reliably by selecting any text widget as
the Gnome 3.28 release notes claim:
"The new keyboard automatically activates when a text area is selected, ..."
-- https://help.gnome.org/misc/release-notes/3.28/
This does not work
They had both been there from the start, but I typoed it into an ii when
adding "cosmic" tag and so I restored the original
--
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/1687246
Filed as https://gitlab.gnome.org/GNOME/gnome-shell/issues/555
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/726692
Title:
Screen backlight
Got instructions from upstream. Probably not a gnome-shell issue but I
will need a few days to run tests and figure out where the problem ist
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the airplane mode
Bios version is the latest from Asus
** Summary changed:
- Airplane mode key on Asus UX561UD laptop not working under X or Wayland but
working on console
+ Airplane mode key on Asus UX561UD laptop not working in gnome-shell (X or
Wayland) but working on console
** Summary changed:
- Airplane
Forgot to add: Nvidia binary drivers are installed but Nvidia is
switched off via Prime setting in nvidia-settings. Running with Intel
drivers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
In case it matters, the keyboard backlight is filed as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791372
--
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/1791367
Title:
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
** Description changed:
Report created by following
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected
Let me know if anything is wrong or if I can give more info
Touchpad worked perfectly
** Attachment added: "xev.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116386/+files/xev.log
** Summary changed:
- 'Apple touchpad bcm5974' stops being reponsive until finger is lifted after
moving cursor a bit in 'Apple MacBookPro5,4
Public bug reported:
Touchpad worked perfectly in Ubuntu 17.10 when using one and two fingers
clicks, two finger scrolling, and tapping. (I don't know if multitouch
worked, but IIRC it did in the past with Unity)
After upgrading to Bionic Beaver it frequently becomes unresponsive,
during which I
** Attachment added: "evtest"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116385/+files/evtest
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in
** Attachment added: "xinput"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116384/+files/xinput
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in
** Description changed:
+ Report created by following
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
+ Let me know if anything is wrong or if I can give more info
+
Touchpad worked perfectly in Ubuntu 17.10
No worries, as the Dell shows it seems not a no-brainer anyway, so
better to postpone. Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1791367
Title:
Airplane mode key
Thank you. I had written bug #1792813 about the sensors not being found
with kernel 4.18. This is fixed in the mainline 4.19 (see the other
report).
The incorrect automatic back rotation also happens with 4.19. However,
note that what exactly happens depends on whether the keyboard vs
display
Thanks Efthimios.
I am still a little unclear about what the intended behavior is. Should it auto
open when touching a text field e.g. in Chrome? And are you using X or Wayland
and it you enable the OSK in Universal Access?
Thanks. FWIW, for me on Cosmic it is still as described in the
I am not the OP, but I have the same resolution, 3840x2160 on 15.6"
display. Using Firefox 63 (as of today's update) on Cosmic, I still have
to set layout.css.devPixelsPerPx to 2.5 in about:config for a usable
Firefox. In both X and Wayland.
--
You received this bug notification because you are
** Tags removed: verification-needed-cosmic
** Tags added: verification-failed-cosmic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed
Added comment to the other bug #1740894: Same issue on the Dell as we
had here, the new update to 2.23-1 from -proposed breaks disabling the
airplane mode on the Dell XPS 15 9575.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Some feedback for Cosmic:
FWIW, I can confirm that the update did NOT break the keyboard backlight
key on Dell XPS 15 9575, where it had already worked flawlessly out-of-
the-box with Cosmic since installation in early September (contrary to
the bug description above stating that "keyboard
A few weeks ago I submitted the similar Bug #1791367 for airplane mode
key not working on Asus ZenBook Flip UX561UD. We did some tests updating
xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on
the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1
where it had
Public bug reported:
Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in
order to pass KEY_RFKILL to userspace.
Despite the issue described in bug #1740894, on Dell XPS 15 9575 the
airplane mode key actually worked flawlessly out-of-the-box after
installing Cosmic at beginning
@Gunnar: Sure, happy to sacrifice my airport key :)
New bug #1800727 for the XPS.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to
FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575
--
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/1797178
Title:
gnome-shell activities / application icon touches
** Changed in: firefox (Ubuntu)
Status: Incomplete => Confirmed
--
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/1407882
Title:
Firefox won't automatically adjust the toolbar /
I cannot confirm this on my machine. I do not know if what I see it
intended behavior, but what I see is still not what either the Gnome
2.28 release notes or the Ubuntu help say should happen.
When I enable the OSK in universal access, the OSK opens way too often but not
always when it should.
To be clear, the above debugging output is with xkb-data
2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of
airplane mode by the dedicated key being broken
$ aptitude show xkb-data
Package: xkb-data
Version: 2.23.1-1ubuntu1.18.10.1
State: installed
--
You
@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a
regression with xkb-data 2.23.1-1ubuntu1.18.10.1.
On this machine, the airplane mode key worked perfectly out-of-the-box
(i.e., the key enabled AND disabled the airplane mode) with the
development version of Cosmic, using xkb-data
As an additional check I once more installed the SRU version (and
rebooted):
$ apt-cache policy xkb-data
xkb-data:
Installed: 2.23.1-1ubuntu1.18.10.1
Candidate: 2.23.1-1ubuntu1.18.10.1
Version table:
*** 2.23.1-1ubuntu1.18.10.1 500
500 http://de.archive.ubuntu.com/ubuntu
@Sebastian:
I reinstalled the non-SRU version:
$ apt-cache policy xkb-data
xkb-data:
Installed: 2.23.1-1ubuntu1
Candidate: 2.23.1-1ubuntu1.18.10.1
Version table:
2.23.1-1ubuntu1.18.10.1 500
500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
And your fix helps:
Still with SRU version installed:
$ cat /sys/class/dmi/id/modalias
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:
So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb:
@Sebastien:
Yes, enable/disable airplane mode works from gnome-control-center. It
also works to disalbe it from the Gnome panel manu. (Remember that it
previously also could be enabled and disabled with the dedicated Fn+Pos1
key as long as xkb-data was 2.23).
As for the verification-failed: I
** Description changed:
On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the
available scaling options in the gnome-control-center (version:
1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200,
300, and 400%. This is insufficient as 200% is too small and
@Sebastien: Thank you very much. With the SRU version installed (I hope
that's right):
sudo evemu-record
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: Sleep Button
/dev/input/event3: Power Button
/dev/input/event4: AT
I see the same behavior on a display with the same dimensions on a different
laptop:
Asus ZenBook Flip 15 UX561UD
15.6 inch 16:9, 3840 x 2160 pixel, 282 PPI
On both the Dell and the Asus:
Without the experimental setting, options offered are 100, 200 (too small), 300
(too large), 400%.
With the
Test result on the Asus ZenBook Flip UX561UD:
Sadly no improvement with the upgraded xkb-data 2.24 from the ppa. Behavior is
completely the same as with the standard 2.23.1, the airplane mode key does not
work in gnome-shell but works on the console.
--
You received this bug notification
For my 15" display with 3840*2160, without the workaround I get 100, 200 (too
small), 300 (too large), and 400. Is it intentional that with the experimental
workaround from the first comment enabled, I have 125, 150, 175 and 200% but
nothing above it?
The maximum of 200% is too small and I use
** Description changed:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
- scaling options in the Gnome 3.30.1 (Cosmic) display settings are
- limited to 100, 200, 300, and 400%. This is insufficient as 200% is too
- small and 300% is too large. The missing fractional scaling
Daniel, new gnome-control-center bug #1795483
--
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/1687246
Title:
GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Public bug reported:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
scaling options in the Gnome 3.30.1 (Cosmic) display settings are
limited to 100, 200, 300, and 400%. This is insufficient as 200% is too
small and 300% is too large. The missing fractional scaling options are
Anything I can do?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1791367
Title:
[FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not
working in gnome-shell (X
No stop, disregard, SORRY!!!
I don't know how, but I messed up, the update was not installed and I misread
some check.
Now I definitely do have the update installed and IT WORKS on the Asus.
It still breaks the Dell though :)
--
You received this bug notification because you are a member of
** Description changed:
- The docs give an incorrect or at least incomplete and misleading
+ The docs seem to give an incorrect or at least incomplete and misleading
description:
"The on-screen keyboard is automatically enabled if you use a touchscreen
1. Open the Activities overview and
Thanks, Gunnar. I could not test it yet on the Asus from this bugreport,
it will take a few days until I can get my hands on this one.
However, I tested with my own Dell XPS 15 9575 and it breaks the
Airplane mode switch there, which works perfectly with the standard xkb-
data=2.23.1-1ubuntu1
1 - 100 of 174 matches
Mail list logo
