Hi Daniel, thanks very much for having a look. What do you think then
about Jonas Adahl's observations from the syscap files, that "The frame
clocks together dispatches at 1000 Hz at times."? Is this expected to be
triggered by firefox as well, despite the window not being in focus?
Furthermore
Public bug reported:
As requested in the upstream bug report
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file
the downstream issue:
I am experiencing high cpu usage of gnome-shell in situations where I
would not expect it, leading to my fans running more often and wasting
** Tags added: jammy kinetic
--
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/1922559
Title:
osk: umlauts do not work in password prompts
Status in GNOME Shell:
New
Status in
@Daniel: affects 22.04 and 22.10 as well. Behavior additionally
regressed in the way, that it is now impossible to access those
characters, since the popup of the characters is hidden in the
background and when trying to write "ü" by long pressing "u", the popup
appears in the background and on
Would you mind trying flatpaks? Those had working screensharing and do
not work anymore for me with 21.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1950040
Title:
@vanvugt: Thanks for having a look. Have you tried firefox from flatpak or any
other flatpak application?
Also is the "pipewire-media-session" package installed by default? It didn't
seem to be the case for me.
--
You received this bug notification because you are a member of Desktop
Packages,
Tagged regression-release since Wayland Screensharing worked fine in Ubuntu
21.04.
@vanvugt, could you have a look?
** Tags added: regression-release
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Instead of downgrading (see #2) it also helps to install the package
"pipewire-media-session". This looks like a packaging bug somewhere, since that
would need to be a hard dependency somewhere.
Flatpak apps remain broken though w.r.t screen-sharing.
--
You received this bug notification
For Chromium via Flatpak I get
[304:456:1106/144346.048939:ERROR:base_capturer_pipewire.cc(206)] PipeWire
stream state error: wrong resource type/version
[304:456:1106/144346.048966:ERROR:base_capturer_pipewire.cc(193)] PipeWire
remote error: wrong resource type/version
Everything run via flatpak still has broken screensharing, Firefox from
deb package and Google Chrome via deb package work fine with the
downgraded packages from #2.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
Downgrading to the following package versions from Ubuntu 21.04 makes
screen sharing work on Ubuntu 21.10:
gstreamer1.0-pipewire_0.3.24-3_amd64.deb
libpipewire-0.3-0_0.3.24-3_amd64.deb
libpipewire-0.3-modules_0.3.24-3_amd64.deb
libspa-0.2-modules_0.3.24-3_amd64.deb
pipewire_0.3.24-3_amd64.deb
Relevant output in journal:
Nov 06 11:14:08 pc xdg-desktop-por[6355]: Unhandled parent window type
Nov 06 11:14:08 pc xdg-desktop-por[6355]: Failed to associate portal window
with parent window
Nov 06 11:14:08 pc GeckoMain[11893]: gdk_wayland_window_configure: assertion
'height > 0' failed
Public bug reported:
Freshly installed Ubuntu 21.10, screen sharing does not work with any
browser, tested the following options:
- Firefox snap
- Firefox deb
- Chromium snap
- Chromium flatpak
Steps to reproduce:
1. Go to
Public bug reported:
Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4071
A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after
installing the proprietary nvidia drivers. Did not happen with gnome-shell
versions < 40.
Changing display
No longer a problem in Ubuntu 21.04. In gnome settings go to
"Applications", select Remmina and toggle "Inhibit system keyboard
shortcuts". That gives the application permission to grab the keyboard.
** Changed in: remmina (Ubuntu)
Status: Triaged => Invalid
--
You received this bug
Thank you all for sorting this out quickly. I can confirm everything
works fine now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1922423
Title:
Can't connect to
Done: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4040
Thanks for having a look!
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4040
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4040
--
You received this bug notification because you are a member of Desktop
Public bug reported:
When I try to input a german umlaut like "ü" in a gnome-shell password
prompt using the onscreen keyboard, nothing appears in the input field.
In regular applications like gedit umlauts work however, so it seems to
be specific to password prompts.
Couldn't find anything
Public bug reported:
There is a bug fixed upstream
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/64
This makes it impossible to use my VPN connections on Ubuntu 21.04. Please
backport that fix before the release.
** Affects: network-manager-openvpn (Ubuntu)
Importance:
@Daniel Could you triage this to make it in before the release?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1922423
Title:
Can't connect to some OpenVPN providers
** Attachment added: "xinput.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919310/+attachment/5477211/+files/xinput.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "libinput.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919310/+attachment/5477212/+files/libinput.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Hardware: Dell XPS 13 9310 2-in-1 with Dell Premium Active Pen (PN579X).
When using the Wayland session, I can't see a cursor moving when
hovering with the pen. In the Xorg session a mouse cursor is shown that
follows the pen as I hover over the display.
It would be nice to
Thanks Daniel, great work as always! Confirmed that downgrading to gjs
1.67.2-1 and libgjs0g 1.67.2-1 solves the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1918738
Title:
Public bug reported:
Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully
upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter
and Capitalize as well as for collapsing the keyboard do not work. Pressing
them just does nothing.
Related logs in
@seb128: Yes that's still an issue unfortunately (tested with btrfs
subvolume).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1442649
Title:
nautilus trash doesn't include btrfs and
Thanks, will this land in focal too?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1896622
Title:
scp-dbus-service.py crashed with SIGSEGV
Status in
Public bug reported:
I printed something, afterwards I wanted to print again, but the printer did
not receive the print job, so I cancelled the job and tried to start it yet
again. Unfortunately it did not resolve the situation.
So I cancelled the print job and while at it, I changed the
@seb128: Yes, it's really annoying. I have to be really careful not to
zoom too much in and out my documents as everytime it could be the last
time before evince and all it's child windows freezes indefinitely.
It seems to me like it happens in the rendering code. Reproducing
sometimes need
Also note that this deadlock happens both in wayland and xorg gnome
session. The backtrace I generated in
https://gitlab.gnome.org/GNOME/evince/-/issues/1222 was in the xorg
session though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Still happens as of Ubuntu 20.04, I reported it to upstream now:
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1016
** Changed in: gnome-software (Ubuntu)
Status: Expired => Confirmed
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1016
@vanvugt: What would be your proposed way to fix this in Ubuntu if
upstream doesn't change their mind? A new extension? Adding a patch to
the package?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
I am not using the ubuntu modifications of gnome-shell and therefore the
Appearance tab in the gnome-control center is essentially useless, and
what's worse choosing an option in the window colors selection simply
crashes control center.
Therefore it would be appreciated to
** Changed in: evince (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1436555
Title:
evince crashed with SIGSEGV in
@William: I downloaded your pdf and checked: It does not reliably
trigger this issue for me. But I experience the freeze issue almost
daily, it happens randomly while zooming in documents. Sometimes I open
a document and within the first zoom it freezes, sometimes I have to
play around for minutes
Public bug reported:
Take a fresh installation of Ubuntu and remove the package netplan.io.
Now you will observe, that network-manager no longer detects wired connections.
Installing ifupdown instead of netplan does not help this situation.
In debian sid networkmanager detects the wired
Indeed, I forgot to upgrade so I missed the issue. Now that I did I see
the hiss is indeed much louder. Thanks Kai for sending this upstream
already.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
I've had this issue since 2017 all the time. As you can see in the
comments, Kai suggested that this is an hardware issue. He developed a
workaround for the kernel that I tested, however it made the general
output volume significantly lower, see #96, which is the reason this fix
was never shipped.
I have forwarded the info to the Debian maintainers Guido Günther, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698504
He would like to see the patch upstreamed ...
@Till, @shemgp could you please propose your patch to upstream?
Furthermore, could you please arrange with the Debian
For the output volume I made the following observations:
* Even with a volume boost of 150% in Pulseaudio (the maximum), the output
volume is still significantly lower than the unpatched kernel
* With 150% pulseaudio boost, I can hear disortions and crackling, so the sound
quality gets
Kai, I compile my own kernels and I would like to use this right now,
could you please link me the patch? The test kernel floods my syslog
badly with touchpad debug entries (unrelated to this bug).
Now regarding testing: By software boost you mean we should test both:
Microphone software boost
Kai: I do not understand your last comment, could you elaborate? Did you
mean we should test if software boost = pulseaudio boost performs well
enough?
Kai, I am quite happy with
http://people.canonical.com/~khfeng/lp1654448-2/ please link me the
patch as the only drawback would be the lower
Kai, http://people.canonical.com/~khfeng/lp1654448-2/ does not have the
hiss :-).
Would compensating the lower output volume with setting pulseaudio to
100+% make the quality worse? Does setting pulseaudio to e.g. 130%
disort the quality?
--
You received this bug notification because you are a
Could you please post the patch for
http://people.canonical.com/~khfeng/lp1654448-2/ ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek
Kai, Thank you very much for looking into this and answering questions. Kudos!
I think the behavior should remain as it is if the output volume is reduced
that much AND support for microphone devices is crippled.
My arguments: It is still better to hear the hiss when music is at low volume
than
Yeah but I don't think it gets through to the right people. If I read most of
the forums discussions no one acknowledges the problem. Only suggestions are to
install the latest drivers.
The 9360 came out one year after the 9350 and still has the same issue. User's
experiences are not that grave
Kai: I understand what you are saying ... but I would find it great if
you could point that out to Dell ... just because now it is bad, does
not mean it can't be improved in the future. With proper hardware
testing this could have been avoided.
--
You received this bug notification because you
Kai: Yeah but it would be nevertheless good to communicate that to the right
people of Dell.
Is this an integrated component I can't exchange? Is it Intel integrated Audio
or is it an external chip?
Hence I would like to do something on hardware level ... is this not
possible?
--
You
Kai: So you are saying the sound card is buggy on a hardware level? Does
this only affect XPS13's or are other Laptops possibly affected too? I
guess all that are using the same soundcard?
How about communicating this to Dell? Or isn't this their fault? Is the
vendor of the sound card to fault?
Kai: Confirmed my assumption, your patch SIGNIFICANTLY lowers the output
volume!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek
load-module module-echo-cancel aec_method=webrtc sink_name=cancel.out
source_name=cancel.src
set-default-source cancel.src
set-default-sink cancel.out
does not change anything either. To make the hiss disappear I have to
mute the hardware output device.
Would be glad if someone could point out
Regarding the second question: The workaround "amixer -c 0 set
'Headphone Mic Boost',0 1" does lower the output volume significantly.
If your patch does the same as the workaround, then the output volume
would be significantly lower, I have not tested this yet though.
--
You received this bug
Another question: You say your code does the same as the workaround
"amixer -c 0 set 'Headphone Mic Boost',0 1" ... so the output volume is
decreased too with your patch?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in
load-module module-echo-cancel aec_method=webrtc source_name=cancel
set-default-source cancel
does not improve the situation. The hiss remains unchanged for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Thanks very much for the code!! Out of interest, how would you achieve
the noise cancellation with pulseaudio?
I tried
load-module module-echo-cancel source_name=test
set-default-source test
which did not work.
A new device appears called "Built-in Audio Analog Stereo (echo
cancelled with
When you connect the jack you can choose between 3 options normally
(with the kernel in [1] only two now)... isn't it somehow possible to
operate with microphone disabled by default ... but leave the user the
option to use a traditional mircophone? The white noise should then only
be triggered
Yes that solves the issue :-). Could you link me the code changes?
But are you sure you can't fix the support for traditional microphones? :-(
Would be a sad loss, could you elaborate why this is not possible?
--
You received this bug notification because you are a member of Desktop
Packages,
Yes it disappears! (forgot to run alsamixer as root).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
amixer -c 0 set 'Headphone Mic Boost',0 1 does not work, it says
"Headphone Mic Boost" not found, so yes, I am however not familiar with
alsamixer. Where would I find "Headphone Mic Boost"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This time there are no KHFENG entries in dmesg.
** Attachment added: "new.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900217/+files/new.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Same situation :-(. The hiss is cleary audible, no change.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900166/+files/dmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Unfortunately the hiss is still there :-(.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
Status in
Is it already the new one as of now? I have just tried it and it did not
help :-(.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek
I confirm Daniel van Vugt, same for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
Status in Dell
Kai-Heng Feng: Is there anybody still working in this? Are you sure Kailiang
noticed this bug?
Is there anything else I could do for you to help?
** Changed in: dell-sputnik
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages,
I tried blacklisting the snd_hda_codec_realtek module, sound works, but
now I can hear the coil whine, depending on the activity of the cpu/gpu.
Moving the mouse pointer around is clearly audible etc.
--
You received this bug notification because you are a member of Desktop
Packages, which is
@vanvugt: I can clearly reproduce the problem with headphones too, I do
not notice they "hide" anything.
I noticed the hiss listening to music so I can always clearly hear it
and it becomes very apparent in a quiet environment.
On another note, with the workaround in place the audio is way to
Confirming Daniel van Vugt: The kernel
http://people.canonical.com/~khfeng/lp1654448/ does not improve the
situation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
@vanvugt: The earphones I tested (Bose Soundtrue Ultra) are Android
ones. I have also tested headphones with no microphone (Sennheiser
HD202).
@kaihengfeng: I will install Ubuntu from scratch in order to test your
kernelsl
--
You received this bug notification because you are a member of
Regarding the Bose Quiet Comfort ... those are noise cancelling headphones, it
is no surprise to me that those cancel the hiss.
I have tested multiple normal earphones and I can reproduce the issue everytime.
--
You received this bug notification because you are a member of Desktop
Packages,
@spike speigel: The tlp issue in the arch Linux wiki is unrelated. The point I
was that when tlp is installed and no audio is currently playing, tlp turns off
the sound card and thus the hiss disappears.
The second point I was trying to say: Of course the white noise is audible when
nothing is
Addendum to the original description:
Steps to reproduce:
0. Make sure tlp is NOT installed
1. Plug in headphones
2. Make sure volume is not muted!
NOTES:
Ad 0.: tlp configures audio power saving, the hiss is only noticeable when
listening to music.
Ad 2.: If the headphones are muted then
Kai, I have tested the 4.12 mainline kernel. The hiss is clearly audible.
Please make suggestions how I can help you.
My earphones are Bose Soundtrue Ultra, but I guess that wont be helpful
to know.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment removed: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869156/+files/hwinfo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
The mentioned workaround
amixer -c 0 set 'Headphone Mic Boost',0 1
has the drawback of significantly lowering the headphone volume!
You can easily test it listening to audio and switching back to
amixer -c 0 set 'Headphone Mic Boost',0 0
--
You received this bug notification because you are a
** Attachment added: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869156/+files/hwinfo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
** Attachment added: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869155/+files/hwinfo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Wow, thanks for the quick reply, I am willing to provide any information
you need, thanks very much for having a look.
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869101/+files/lshw
--
You received this bug notification because
Subscribed Kai-Heng Feng, the submitter of the linked patch
(https://patchwork.kernel.org/patch/9128611/), maybe he could give a
status update!?
My two machines are affected too (XPS 13 9360), confirming the
workaround from #5
amixer -c 0 set 'Headphone Mic Boost',0 1
--
You received this bug
At comment #15: That is not the point. The ubuntu maintainer of chromium
has deliberately disabled gpu acceleration in the ubuntu build. Hardware
acceleration works fine as well in chromium 43.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Same for me on nouveau:
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration
pitti, awesome as always, thanks, your explanation is right. The missing
policy was the problem. Thanks very much!
For people coming here through googleing, that have that problem in a
chroot, see https://wiki.debian.org/chroot#Configuration
--
You received this bug notification because you are
Just retested today. I have a bash script that debootstraps vivid, chroots into
it and installs ubuntu-desktop.
From my utopic systeme everything is fine, but when the exact same script is
run from the vivid live-cd, it fails with installing modemmanager.
Regarding chroot mounts:
mount --bind
** Summary changed:
- package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 100
+ [systemd] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status
pitti, please have a look, this seems to be related to systemd.
I hit this bug when using debootstrap+chroot (deboostrapping vivid to a new
partition, then chrooting into the tree and then installing ubuntu-desktop):
When the host system is an upstart system (14.10, fully updated), installing
/var/log/apt/history.log of deboostrap system.
** Attachment added: /var/log/apt/history.log of deboostrap system.
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+attachment/4390781/+files/history.log
--
You received this bug notification because you are a member of
/var/log/apt/term.log of deboostrap system.
** Attachment added: /var/log/apt/term.log of deboostrap system.
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+attachment/4390775/+files/term.log
--
You received this bug notification because you are a member of Desktop
This was an apparmor denial in my case, I proposed a fix here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1419294
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
So what is the problem now? It does not work for me, why the incomplete
mark? Which version fixes the problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1414753
Title:
What version is this next version?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1414753
Title:
Chromium browser 39.0.2171.65 does not load policies
Status in
Public bug reported:
Following the information I gathered from
http://www.chromium.org/administrators/linux-quick-start
http://www.chromium.org/administrators/linux-quick-start
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802
I tried to set a simple policy for the
Are there any plans to make this ready for 13.04 raring?
What is missing? I see lots of code requests pending, what is wrong with them?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
In order to enable horizontal scrolling run the following command:
dconf write
/org/gnome/settings-daemon/peripherals/touchpad/horiz-scroll-enabled true
(The setting is still available in dconf editor)
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I am on Ubuntu 13.04 daily build. Vertical edge scrolling is enabled out
of the box, but horizontal is not and there is no way to enable that
through the control center. It would make sense to enable horizontal
edge scrolling too by default or at least give an option to do
The same is true for edge scrolling, which is enabled by default:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1087969
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
I can absolutely confirm this issue. For example, it does not matter
which gtk file manager you use, they are all very slow for opening large
directories (even on ssd) with many files (For Qt based filemangers as
dolphin, this is not a problem). For example take nautilus and try to
open /usr/lib
97 matches
Mail list logo
