Was a bug report sent to the developers? I'm asking, because I couldn't
find a correlating bug report on:
https://bugzilla.gnome.org/browse.cgi?product=evince
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
@Sebastien Bacher
Why only "low"? It obviously affects every non-English user and seems easy to
fix. Imho, it should be at least medium, if not high.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Same here with a fresh installed Ubuntu 18.04...
--
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/1767817
Title:
Full text search does not work
Status in nautilus package in Ubuntu:
Please change it to "confirmed". That's still a relevant issue.
--
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/1698083
Title:
Middle-click titlebar actions (like maximizing
Still in English in Ubuntu 17.10 ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1491787
Title:
System language isn't applied to gnome-control-center in Gnome-Shell
Full text search should work out of the box. Every modern OS has this.
IMHO, the importance should be changed to "high" instead of "low"!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Why is this another bug?
--
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/1698083
Title:
Middle-click titlebar actions (like maximizing vertically) don't work
in Wayland sessions
I'm using Ubuntu 17.10 and this bug is still present with Xorg AND
Wayland.
Apps with a "normal" GTK titlebar (the narrow one), like Firefox, are
working according to the settings in Gnome Tweak. So a double- or
middle-click on the titlebar maximizes the window f.i. vertically. But
when an app
Same here on Ubuntu 18.10 with gnome-disks 2.7.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1571268
Title:
No SMART data for USB disks in gnome-disk-utility
Status in
I've opened another issue regarding this notebook. It's about
overheating. Would be very helpful, if you could share your experience
here: https://askubuntu.com/questions/1087672/unusually-hot-asus-ux391ua
--
You received this bug notification because you are a member of Desktop
Packages, which
Still no sound, even on Ubuntu 18.10.
--
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/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Status in
BTW, can somebody confirm that this ZenBook S UX391UA on Ubuntu 18.04
runs quite hot, even while doing normal "office stuff"?
At some point the preinstalled thermald daemon even forcefully shuts
down Ubuntu, preventing it from overheating. "Package temperature above
threshold, cpu clock
I even installed Windows on an external drive, because the author of
this thread (https://askubuntu.com/questions/986140/no-sound-output-
ubuntu-17-10-asus-zenbook-13) assumed that a proper shutdown of Windows
could solve this issue for Linux users, but it didn't help either.
--
You received
This also happens on Manjaro, see https://forum.manjaro.org/t/alc294
-analog-audio-card-detected-but-no-sound-internaly-or-
headphones/54089/16
Did somebody already find a solution or knows how to debug this
properly?
--
You received this bug notification because you are a member of Desktop
Can somebody confirm that the above mentioned procedure also works with
an UX391UA.
It does NOT work on my UX391UA.
--
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/1784485
Title:
@Karen Chaltikian
Good news! Although I've tried this on my UX391UA, but without success.
Can you describe your procedure step-by-step?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Some additional sysinfo with inxi:
System:Host: mir Kernel: 4.20.0-042000-generic x86_64 bits: 64 Desktop:
Gnome 3.30.1
Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine: Type: Laptop System: ASUSTeK product: ZenBook S UX391UA v: 1.0
serial:
Mobo: ASUSTeK model:
@VanVan
That's strange!
To be on the safe side, I even did a fresh Ubuntu 18.10 installation and
updated to the 4.20 kernel with UKUU, but I still don't have sound.
Neither from the internal, nor the external speakers. I've played around
with alsamixer in the terminal – without success.
Can
@Santiago Londoño
Or you could have used UKUU: https://github.com/teejee2008/ukuu
Too bad that the 4.20 kernel doesn't contain the fix for the UX391UA :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Even after installing Nautilus 3.30 from the staging Gnome PPA
(https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging?field.series_filter=cosmic),
the full text search isn't working in Nautilus, but does in the terminal
(tracker search xyz).
Ubuntu devs, please have a look on that.
Installed 4.20.0-rc7 kernel through UKUU, but still no sound on ASUS
UX391U :/
--
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/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294,
@Greg (buchovagabond)
Without adding those 3 patches and the SND_PCI_QUIRK(0x1043, 0x10a1,
"ASUS UX391UA", ALC294_FIXUP_ASUS_SPK) tweak to to
/sound/pci/hda/patch_realtek.c ?
So only updating with UKUU will work?
--
You received this bug notification because you are a member of Desktop
@Ben
patch_realtek.c is missing under
/lib/modules/4.20.0-042000rc7-generic/kernel/sound/pci/hda/ after
installing 4.20.0-rc7 kernel.
Can't find it elsewhere either.
How do you properly applied those 3 patches?
And the proper command is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
@Ben
Thanks!
Patching and compiling the kernel is out of my league. I prefer the
user-friendly and "foolproof" way through the Kernel Update Utility for
Ubuntu (UKUU), mentioned above. Afaik, I can't edit the patch_realtek.c
file when doing so with UKUU.
Do you know if it's already planned to
I have a ASUS UX391UA and finally want to get the sound working.
Is it theoretically possible to apply the above mentioned fix using the
Kernel Update Utility for Ubuntu (https://github.com/teejee2008/ukuu)?
What's the proper way to apply the following patches afterwards?
Thanks Pawel!
--
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/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Status in alsa-driver package in
Nope, see previous posts.
--
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/1767817
Title:
Full text search does not work
Status in nautilus package in Ubuntu:
Confirmed
Bug
27 matches
Mail list logo
