I was looking at the wrong beast.
Upgrading kernel solved the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1858200
Title:
pulseaudio produces garbage on HDMI after
Public bug reported:
After upgrading from 19.04 to 19.10, the sound output to HDMI is
garbage.
The sound is great on local output, on bluetooth headphones, etc. But
when outputting to a HDMI TV it is garbage.
I tried different users with the same problem.
If I boot on Windows, the output is
Yes
Em sex, 16 de nov de 2018 07:25, Daniel van Vugt <
daniel.van.v...@canonical.com escreveu:
> Is this bug still a problem in the latest updates to 18.04?
>
> ** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
>
> ** Also affects: gnome-shell (Ubuntu)
>Importance: Undecided
>
Public bug reported:
When changing the default sink (builtin audio) to USB audio (PCM2902)
headphone, all desktop uses the new default sink.
All but Chromium (and Chrome).
For both Chromium (and Chrome), I have to change the output device in the
application tab (PA). As soon as the audio
I created inside /etc/x11/xorg.conf.d/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1761773
Title:
Touch Screen stop working on 18.04 beta1
Status in xorg package in Ubuntu:
New
I have a lot of computers in my office that needs this drive to work.
Neither Nouveau or VESA works with them.
If this decision persists I will have to move to another distribution (which I
hope to avoid).
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
After upgrading my office machines to 18.04, some machines did not start
the GDM3.
After some testing the problem was that the ones that it did not work,
had SDDM installed too (KDE environment in those machines).
The upgrade were from 17.10 and 16.04.
Note that
The simplest solution was to add the configuration:
Section "InputClass"
Identifier "NextWindows 1900 HID Touchscreen"
MatchUSBID "1926:0003"
Driver "evdev"
EndSection
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Removing xserver-xorg-input-libinput did the tricky.
Now it uses evdev. However, that shouldn't need be necessary.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1761773
Title:
Touch
The problem might also involve udev, as by these lines:
[ 800.429] (II) event5 - NextWindow Touchscreen: is tagged by udev as: Tablet
[ 800.429] (EE) event5 - NextWindow Touchscreen: libinput bug: missing
tablet capabilities: btn-stylus resolution.Ignoring this device.
[ 800.429] (II)
Upgraded to beta 2 and the same issue continues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1761773
Title:
Touch Screen stop working on 18.04 beta1
Status in xorg package in
Public bug reported:
The touch screen on a HP TouchSmart works fine on other releases.
On the beta of 18.04 it stopped to work.
Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen
On 16.04 it is recognized as TOUCHSCREEN by X.org.
On 18.04 beta 1, it is recognized as mouse.
** Attachment added: "X.org logs from 16.04 (Install Media Try Ubuntu option)
where it works"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+attachment/5104182/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
Just did a full upgrade to 16.04.
cups is 2.1.3-4
libreoffice is 1:5.1.2-0ubuntu1 (5.1.2.2)
The scenario:
1 - Cups is my localhost:
raul@nostromo:~$ cat /etc/cups/client.conf
raul@nostromo:~$ lpstat -a
EPSON_L355_Series accepting requests since Sáb 23 Abr 2016 17:22:15
I did some digging and the printer list is pulled when I first hit
CONTROL-P (File->Print).
So, if I change the client.conf before trying to use the printer, it will get
the current list even after it has started up.
It will not update any time later on.
--
You received this bug notification
** Attachment added: "1-Libre Office Writer 5.1.2.2 on 16.04 Printer Dialog 1"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+attachment/4646398/+files/LO51-Printer_Dialog_1.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment added: "2-Libre Office Writer 5.1.2.2 on 16.04 Printer Dialog 2 -
After LO Restart"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+attachment/4646405/+files/LO51-Printer_Dialog_2.jpg
--
You received this bug notification because you are a member of Desktop
It still happens on 16.04.
Please see bug
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339 .
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/911235
Title:
Public bug reported:
When Libreoffice is started it reads the printer list and saves it.
When there is a change related to cups (new printers) or change the cups
server, libreoffice needs to be restarted (all insteances) to acknowledge the
new printers.
When I change offices, I need to update
This still happens on 15.10 and libreoffice 5.x up to today.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/911235
Title:
[Upstream] LibreOffice doesn't update printer list on
Public bug reported:
There are a few serious packaging problems with akonadi:
1 - akonadi-server depends on akonadi-backend-mysql.
It can also work with postgresql and sqllite, but mysql is mandatory, it
should be optional.
2 - akonadi-backend depends on either mysql-server-core-5.5 or
This tool is very important and it is already built, but not packaged:
http://askubuntu.com/questions/380844/intel-virtual-output-command-for-saucy-13-10-with-dual-monitor-setup-and-hybrid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Same here.
The problem is related to Oxygen indeed. (as #7 pointed)
Changing the gtk theme to something else solved the problem.
Happened with: oracle's java 6,7,8 and openjdk 7.
Tested on all version of ApacheDS (Directory Studio) from 1.5 to 2.0.
-rsd
--
You received this bug notification
Public bug reported:
If I plug my modem on a USB 3 instead of a USB 2 it fails to do the
switch.
It will work fine if I:
1 - extract /usr/share/usb_modeswitch/configPack.tar.gz from
usb-modeswitch-data to /etc/usb_modeswitch.d/
2 - run the command:
sudo usb_modeswitch -v 19d2 -p
This is the kernel log on a USB 3:
usb 3-2: new high-speed USB device number 21 using xhci_hcd
usb 3-2: New USB device found, idVendor=19d2, idProduct=2000
usb 3-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 3-2: Product: ONDA CDMA Technologies MSM
usb 3-2: Manufacturer:
This is the lsusb -v for the modem on the USB3 before usb_modeswitch:
-- 8 ---
Bus 003 Device 021: ID 19d2:2000 ZTE WCDMA Technologies MSM
MF627/MF628/MF628+/MF636+ HSDPA/HSUPA
Device Descriptor:
bLength18
This are the lsbusb on the USB 2 before and after udev/usb_modeswitch:
Bus 002 Device 019: ID 19d2:2000 ZTE WCDMA Technologies MSM
MF627/MF628/MF628+/MF636+ HSDPA/HSUPA
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
This is the usb_modeswitch output on the USB 3:
$ sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c
/etc/usb_modemswitch.d/19d2\:2000 -W
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.3 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW
Finally, this is the same usb_modeswitch, but now on the USB2 (without
udev, for comparison):
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.3 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
This is a dup of 979697
using
options usb-storage delay_use=3
solves the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1094973
Title:
udev + usb_modeswitch fails
*** This bug is a duplicate of bug 992639 ***
https://bugs.launchpad.net/bugs/992639
I think it is the other way around as this one is older and have the
solution.
#992639 even refers to the solution here.
--
You received this bug notification because you are a member of Desktop
Packages,
Created with a right click on konqueror
** Attachment added: test file
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873792/+attachment/2610013/+files/test.odt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/873792
Title:
libreoffice spellchecker/autocorrect does not work when document is
created in the file manager
Status in
33 matches
Mail list logo
