[Desktop-packages] [Bug 2060412] [NEW] Gnome3 apps very slow
Public bug reported: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2060412 Title: Gnome3 apps very slow Status in gnome-shell package in Ubuntu: New Bug description: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
> if there is an active IPv6 regular (non-loopback) interface with an IPv6 address and network connection, then connection attempts to ::1 seem to hang and timeout Probably it uses the default route to send packets to ::1, which is deemed not to receive any response. > I haven't seen any other daemons with issues from this. Maybe they are using IPv4 for loopback? Probably ** Description changed: - Ubuntu 22.04.3 LTS + Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
Ok, I better understand why this has never shown up in most situations.
> my system has functional IPV4 and IPV6
Well, it still behaves oddly on the ip6-localhost case:
> connect(3, {sa_family=AF_INET6, sin6_port=htons(4101),
sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "::1", _addr),
sin6_scope_id=0}, 28) = -1 ETIMEDOUT (Connection timed out)
That's really not supposed to time out, and rather just immediately
return a "connection refused". Do you have some firewall rules on the lo
interface? I'm surprised that this doesn't pose troubles to other
system-/session-wide daemons.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/2039374
Title:
xbrlapi causes long delay in GUI login
Status in brltty package in Ubuntu:
New
Bug description:
Ubuntu 22.04.3 LTS
xbrlapi 6.4-4ubuntu3
After logging in to the GUI, there is a delay of over 2 minutes before
the desktop environment loads (screen will be black with a mouse
cursor)
This is caused by /etc/X11/Xsession.d/90xbrlapi
The script runs xbrlapi, which hangs for 2 minutes or so, presumably
because it is trying to connect to a BrlAPI server that doesn't exist
on my machine.
I guess this packages was installed by orca, because I did not
directly install it myself and I don't need it.
Did not happen before 22.04
Others have this issue:
https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
This is very surprising: what xbrlapi tries to connect to by default is a local socket in /var/lib/BrlAPI/0 so that should be completely independent from TCP/IP networking configuration, and should be either succeeding or failing immediately. Just to be sure: Does /var/lib/BrlAPI/0 exist? Is brltty running on your system? If you have a brltty daemon running it'd be useful to check for its logs. Perhaps you can log into a text console and run strace on the stuck xbrlapi command: strace -p $(pidof xbrlapi) so we get to know what it is stuck on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Concerning 1a86:7523, the udev rules file in ubuntu indeed seems to be
missing the manufacturer filter:
debian/brltty.udev.rules says:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
while it should be:
ENV{PRODUCT}=="1a86/7523/*", ATTRS{idVendor}=="1a40", ATTRS{idProduct}=="0101",
ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
This needs to be fixed in the various ubuntu brltty versions, starting
from 6.4.
BTW, for 403/6001 I see there
Ubuntu disable those to avoid conflicts, https://launchpad.net/bugs/1958224
But the line with the manufacturer filter should *not* be disabled, it properly
filters-in the producer of the Braille devices.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
Status in brltty package in Ubuntu:
Fix Released
Status in brltty source package in Jammy:
Fix Released
Status in brltty package in Debian:
Confirmed
Bug description:
* Impact
The brltty udev rules are claiming generic devices IDs which makes
some other devices like Arduino cards not able to interact with the
serial port anymore
* Test Case
Try to use an Arduino over a cp210x or FTDI serial port, it should be
able to talk to the computer
- upgrades from focal/impish to the SRU version should have no
question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- upgrades from brltty 6.4-4ubuntu2
1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is
connectect at the time of the upgrade it should prompt with the debconf question
1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should
be generated
1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not
installed
2. if no matching device is connected
there should be no debconf question nor
/etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- installing brltty when it was not installed
no question and no config generated
* Regression potential
If the debconf logic is wrong users could be prompted with the
question when not needed or not prompted when they should. If the udev
rules was incorrect or wrongly installed it could lead to have brltty
not starting when it should
---
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
brltty: Installed: 6.4-2ubuntu1
brltty appears once again to be claiming cp210x devices with the
vendor/product ID of:
idVendor=10c4, idProduct=ea60
Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60,
bcdDevice= 1.00
[ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
[ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs
[ 999.215978] usb 3-6.3: SerialNumber: 0005
[ 999.234070] usbcore: registered new interface driver usbserial_generic
[ 999.234081] usbserial: USB Serial support registered for generic
[ 999.235262] usbcore: registered new interface driver cp210x
[ 999.235272] usbserial: USB Serial support registered for cp210x
[ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected
[ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
[ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
[ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input42
[ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty'
sets config #1
[ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 999.995066] cp210x 3-6.3:1.0: device disconnected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1186702]
This has been fixed with 1bc454a2c0cb0dd69512d69ddd2123a44814197e . -- 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/1186702 Title: WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out- of-the-box Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Libreoffice is able to open documents located on a WebDAV server if provided with an URL starting with the vnd.sun.star.webdav protocol. (for instance: vnd.sun.star.webdav://example.com/webdav/my-document.odt ) Unfortunately, after installing Libreoffice on Ubuntu these URL aren't still handled correctly. Whether you click on a link in your browser or you try to open the URL from the command line with xdg-open vnd.sun.star.webdav://... you get a message saying that this protocol is unknown. What I expected was that LibreOffice would start and would open the document. A workaround is to create a Desktop file with the following informations: [Desktop Entry] Name=WebDav LibreOffice Exec=/usr/bin/libreoffice %u Type=Application Terminal=false Categories=System; MimeType=x-scheme-handler/vnd.sun.star.webdav; and then to copy it in /usr/share/applications Afterwards you have to run sudo update-desktop-database so that Ubuntu will take the new protocol into account. A more definitive solution would be to modify the libreoffice-base Desktop file that comes with libreoffice (also located in /usr/share/applications) to add the MimeType properties described above. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Jun 2 11:51:56 2013 InstallationDate: Installed on 2013-05-12 (20 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1186702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Hello,
beattie, le mar. 20 sept. 2022 15:21:36 -, a ecrit:
> can't find anything in the udev,
That's be in ./lib/udev/rules.d/85-brltty.rules, this line:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
> I think somebody did not do their testing.
Not many people have a CH340/CH341-based adapter to notice the issue.
Samuel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990189
Title:
brlttty claiming CH341 usbtty device blocking access
Status in brltty package in Ubuntu:
New
Bug description:
While this problem seems to have been fixed for FTDI and CP210 based
devices CH340/CH341 based (and possibly other USB serial adapters) are
unusable except by brltty.
[139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using
xhci_hcd
[139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86,
idProduct=7523, bcdDevice= 2.63
[139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
[139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
[139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
[139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input24
[139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while
'brltty' sets config #1
[139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected
from ttyUSB0
[139100.786136] ch341 1-2.1.2:1.0: device disconnected
[143917.740171] usb 1-2.1.2: USB disconnect, device number 17
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: brltty 6.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 19 12:01:21 2022
InstallationDate: Installed on 2022-08-23 (27 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
The simple workaround is to remove the package, or remove the entry from the udev file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Ok. That'd be tricky to filter. Fortunately with brltty 6.5 such generic entries are kept apart so that they can be packaged separately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990189] [NEW] brlttty claiming CH341 usbtty device blocking access
Hello, beattie, le lun. 19 sept. 2022 19:07:54 -, a ecrit: > [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, > idProduct=7523, bcdDevice= 2.63 Could you run lsusb -v so we get more information on how the generic bridge announces itself? Samuel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
** Summary changed: - My machine as Wi-Fi Hotspot broken after upgrade to 22.04 + My machine has Wi-Fi Hotspot broken after upgrade to 22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
I have a similar issue. Here is what happens : I can connect to the hotspot just fine, but the connected devices don't have access to internet (tested with an android device and a windows device). I tried all the wifi security options one by one, and there is the same behavior with each of them. The hotspot worked fine with Ubuntu 21.10. Hope this helps and sorry for the noise if it's unrelated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@Dave @XA Okay. It worked for me though. Just hope it wasn't a temporary fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Run this command: sudo apt remove gstreamer1.0-vaapi Got my solution from this article, check it out too. https://www.makeuseof.com/things-to-do-after-upgrading-to-ubuntu-2204-lts/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> it's a bit unclear to me which entries there should be considered 'generic USB IDs'? They are marked "Generic Identifier", that's 0403:6001 10C4:EA60 10C4:EA80 > I also don't understand why those rules are debian specific See the diff between ./debian/brltty-udeb.udev.rules and ./Autostart/Udev/device.rules.in Note that in debian we use the udev rules *only* inside the installer. The current strategy in Debian is that in the installer we use udev rules to autodetect braille devices. But in the installed system we don't: when the user installs brltty, the user means that they have a Braille device and want to probe it, whether it uses a generic USB ID or not, i.e. we always start brltty > How does upstream handle the devices? When brltty is started it just always probes all devices. Its udev rules file always starts brltty, be it generic IDs or not. > We should stop installing brltty by default going forward That would align with the way it happens in Debian yes. Ideally the udev rules would be split so that the non-generic pieces get always installed to start brltty, and the generic pieces are installed only when necessary. That's a matter of actually spending time on implementing it. > we aren't going to respin ISOs on old serie for such changes and that wouldn't be a solution for already installed systems... Yes, rather disable the generic udev rules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
orca only suggests brltty, it's the *-desktop packages which seem to be recommending brltty. If Ubuntu really wants to install brltty by default, it should disable the udev entries for the generic USB IDs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970039] Re: cannot disable Remote Desktop in Ubuntu 22.04
I uninstalled gnome-remote-desktop and it seems to be disabled, but I haven't actually checked the network connections. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970039 Title: cannot disable Remote Desktop in Ubuntu 22.04 Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: 1. Go to Settings 2. sharing 3. Disable Remote Desktop and Sharing 4. Restart PC problem: Remote Desktop is enabled. seems to be connected with RDP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970121] [NEW] sharing enabled by default on 22.04
Public bug reported: After install and first boot, sharing is enabled by default in Ubuntu 22.04. It should be disabled initially. I used the minimal install function and it seems to be related to gnome-remote-desktop. ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public ** Package changed: ubiquity (Ubuntu) => gnome-remote-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970121 Title: sharing enabled by default on 22.04 Status in gnome-remote-desktop package in Ubuntu: New Bug description: After install and first boot, sharing is enabled by default in Ubuntu 22.04. It should be disabled initially. I used the minimal install function and it seems to be related to gnome-remote-desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970011] [NEW] pulseaudio running but can't hear any sound
Public bug reported: ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 23 00:50:09 2022 InstallationDate: Installed on 2022-04-06 (16 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1970011 Title: pulseaudio running but can't hear any sound Status in pulseaudio package in Ubuntu: New Bug description: ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 23 00:50:09 2022 InstallationDate: Installed on 2022-04-06 (16 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1970011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968385] [NEW] [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: Can't hear any sound on my inbuilt speaker (but it works with lubuntu). Currently using xubuntu. Also cannot hear any sound in my headphones when plugged in, although volume control recognizes that headphones have been plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 8 18:54:56 2022 InstallationDate: Installed on 2022-04-06 (2 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1968385 Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Can't hear any sound on my inbuilt speaker (but it works with lubuntu). Currently using xubuntu. Also cannot hear any sound in my headphones when plugged in, although volume control recognizes that headphones have been plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 8 18:54:56 2022 InstallationDate: Installed on 2022-04-06 (2 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968338] [NEW] package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit s
Public bug reported: my computer froze, i rebooted, and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.99.9.8 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 13:07:14 2022 ErrorMessage: new software-properties-common package pre-removal script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968338 Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 Status in software-properties package in Ubuntu: New Bug description: my computer froze, i rebooted, and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.99.9.8 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 13:07:14 2022 ErrorMessage: new software-properties-common package pre-removal script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968109] [NEW] "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
Public bug reported: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screen record of the process I do in Ubuntu Studio 21.10 to get my Wi-Fi driver working, but fails in 22.04." https://bugs.launchpad.net/bugs/1968109/+attachment/5577783/+files/vokoscreenNG-2022-03-18_16-35-55.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources Status in software-properties package in Ubuntu: New Bug description: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1954413] Re: firefox snap cannot be started: firefox already running
I have a similar issue (let me know if I should open a new bug): launching firefox for the first time (ie. while it's not running) works fine. But, once it's running, any further invocation of firefox fails with the "Firefox is already running..." dialog - for example, clicking on a url in a terminal, or running `firefox https://example.com`. -- 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/1954413 Title: firefox snap cannot be started: firefox already running Status in firefox package in Ubuntu: Invalid Bug description: On my lapttop version 747 of the Firefox app is installed. Whenever I try to launch /snap/bin/firefox I get a popup that Firefox is already running. ps -aux does not show any such process. Rebooting and deleting lock files in ~/.mozilla does not solve the problem. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1954413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
Yes, unfortunately there is no way to fix it in that case. The udev rules properly avoid starting brltty when the iManufacturer field is changed from FTDI to the actual manufacturer of the device, but not when it is left to FTDI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: New Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> In this case, brltty appeared (or at least the device claim) after a dist-upgrade Ah, do you happen to have a log of that dist-upgrade, so we can determine what brought it in? > It still feels very bad form for a vendor device to use the default VID/PID of the underlying converter chip Yes. Unfortunately that's what they have done, those devices are out there, and people have already bought them (and they cost a lot of money) :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Debian is installing the brltty package only when brltty was used during installation. Brltty gets started during installation either through the udev rules, or started manually from the kernel command line. The finish-install script just checks out /var/run/brltty.pid to determine whether a brltty is running. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964808] [NEW] Wifi keeps disconnecting
Public bug reported: I have a box with 802-11n and I run into a problem with my Lenovo laptop : - when I change the wifi password, it connects immediately and works well - the next time (for example after switching the airplane mode on and off), it fails and the network manager keeps asking me the password again and again Please notice that I have no problem with other wifi access points (when going in other places with my laptop), and my box works well with every other devices (ubuntu laptops, android phones) but mine ! My laptop runs an updated 20.04.4, but the problem first came when I was on 21.04. I then made a fresh install of 21.10 and then a fresh install on 20.04 just to make sure the kernel was not involved. Even tried the last Intel Clear Linux without success. As a workaround, I tried to stop and restart wpa_supplicant: sudo systemctl disable --now wpa_supplicant.service sudo systemctl enable --now wpa_supplicant.service but this did not solve the problem. I also contacted the support of my ISP and they made a clear reset of my box without success. Here is what I see in dmesg : [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3) [ 4203.378464] wlp4s0: authenticated [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3) [ 4203.387408] wlp4s0: RX AssocResp from e4:9e:12:8c:8e:1a (capab=0x1411 status=0 aid=6) [ 4203.391628] wlp4s0: associated [ 4203.399358] wlp4s0: deauthenticating from e4:9e:12:8c:8e:1a by local choice (Reason: 17=IE_DIFFERENT) And here is the restult of lspci : 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88) 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1964808 Title: Wifi keeps disconnecting Status in network-manager package in Ubuntu: New Bug description: I have a box with 802-11n and I run into a problem with my Lenovo laptop : - when I change the wifi password, it connects immediately and works well - the next time (for example after switching the airplane mode on and off), it fails and the network manager keeps asking me the password again and again Please notice that I have no problem with other wifi access points (when going in other places with my laptop), and my box works well with every other devices (ubuntu laptops, android phones) but mine ! My laptop runs an updated 20.04.4, but the problem first came when I was on 21.04. I then made a fresh install of 21.10 and then a fresh install on 20.04 just to make sure the kernel was not involved. Even tried the last Intel Clear Linux without success. As a workaround, I tried to stop and restart wpa_supplicant: sudo systemctl disable --now wpa_supplicant.service sudo systemctl enable --now wpa_supplicant.service but this did not solve the problem. I also contacted the support of my ISP and they made a clear reset of my box without success. Here is what I see in dmesg : [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3) [ 4203.378464] wlp4s0: authenticated [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3) [ 4203.387408]
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Yes, but it is meant to be so: the Seika Braille device is announced as such, so we have to recognize such devices in brltty, otherwise the Seika Braille devices would not work at all. The question is rather: why is brltty installed on your system? It is supposed to be installed only if you installed your system with a Braille device connected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Ah, the patch is already in brltty 6.4 actually, so no change on the Debian side actually :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Ok, thanks! The corresponding commit upstream is e6ed2372887ac0106db8854f70e9b2fdcadec74f, attached here, could somebody check that this fixes the build issue on Ubuntu? I'll then integrate the patch in Debian as well. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+attachment/5541197/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
> it is probably newer python versions being stricter with the use of non existing options? The --without-viavoice is not passed to the python bindings, so that cannot be the problem. That said I have now dropped the option from debian/rules, thanks :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950488] Re: brltty ftbfs in jammy
Please provide the whole build log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
Just woke up from a suspend once again and still getting this issue. The most recent log lines are May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Starting Sound Service... May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Started Sound Service. May 19 17:30:27 skainswo-X58A-UD3R pulseaudio[1811]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: ALSA woke us up to write new data to the device, but there was actually nothing to write. May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. But these logs are from two days ago... -- 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/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend Status in alsa-driver package in Ubuntu: New Bug description: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
As a quick update, I managed to kill all of the spurious pulseaudio processes that had been lying around as a result of `pulseaudio -k && pulseaudio --start` and got the systemd pulseaudio process back on its feet. Then I confirmed that the audio worked, suspended my system, and woke it up again and the audio still works! Therefore I suspect that pulseaudio processes started by the user in terminal sessions (daemonized) do not survive the suspend/resume cycle for some reason(?). How the systemd pulseaudio process failed to begin with remains the larger issue, however. -- 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/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend Status in alsa-driver package in Ubuntu: New Bug description: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928996] [NEW] [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
Public bug reported: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "pulseaudio-logs.zip" https://bugs.launchpad.net/bugs/1928996/+attachment/5498825/+files/pulseaudio-logs.zip -- 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/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend Status in alsa-driver package in Ubuntu: New Bug description: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test
[Desktop-packages] [Bug 1916722] Re: Pulseaudio fails to start after reboot if home partition is encrypted
Hi Anton, As a workaround, you can try to edit the systemd file "/usr/lib/systemd/user/pulseaudio.service" and add the line: ``` RestartSec=2s ``` Your [Service] section would look like to this: ``` [Service] ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal LockPersonality=yes MemoryDenyWriteExecute=yes NoNewPrivileges=yes Restart=on-failure RestartSec=2s RestrictNamespaces=yes SystemCallArchitectures=native SystemCallFilter=@system-service # Note that notify will only work if --daemonize=no Type=notify UMask=0077 ``` Samuel -- 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/1916722 Title: Pulseaudio fails to start after reboot if home partition is encrypted Status in pulseaudio package in Ubuntu: New Bug description: It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main user too early, before user logs in and the home partition is decrypted. Probably pulseaudio should not start as main user before login of this user. Starting pulseaudio manually after login works. grep 'pulseaudio' /var/log/syslog Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 1. Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 3. Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 4. Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request repeated too quickly. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 'service-start-limit-hit'. Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection refused Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: Connection refused Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed to add PIDs to scope's control group: No such process Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed with result 'resources'. Feb 2
[Desktop-packages] [Bug 1085]
Yea, I realized that edit as new works for my purposes after writing the above comment. The show source feature displays things correctly, UTF-8 characters should be encoded during transmission and thus should be encoded in the source but the address input field does not handle that kind of encoding. Is there any way to add this workaround to these bugs in a little more visible location? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: control+a does not select all the text in the full header window WORKAROUND: use View|Message Source instead of View|Headers|All To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085]
While waiting for this to be fixed could we have a button "new email to all recipients", possibly behind the "more" menu/button, since that probably is one main use of the copy feature. By the way, the workaround to open the source and copy / paste from there does not work well when UTF8 characters are involved. Pasting what is copied from the message source into the address field does not convert the encoded character back, it shows the encoding. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: control+a does not select all the text in the full header window WORKAROUND: use View|Message Source instead of View|Headers|All To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
It seems I have to insist again: patch https://launchpadlibrarian.net/405256420/patch should definitely really really be applied. As explained in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146/comments/73 that script should really *not* pass --force to setupcon. There is no reason for that except that it was copy/pasted from the Debian installer, where it is needed due to the use of bterm. On Ubuntu it should really not be used. Can somebody at last apply that patch that has been waiting for 2 years? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Lucid: New Status in kbd source package in Lucid: New Status in xorg-server source package in Lucid: New Status in console-setup source package in Maverick: New Status in kbd source package in Maverick: New Status in xorg-server source package in Maverick: New Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in linux source package in Disco: Won't Fix Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded
[Desktop-packages] [Bug 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04
I guess this is due to the following change in at-spi2-atk: * Meson: don't hard-code shared_library (!19). which made meson emit a lot of new libraries in Requires.private of atk- bridge-2.0.pc, and thus the -dev package now has to add them in Depends. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1882966 Title: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04 Status in at-spi2-atk package in Ubuntu: Confirmed Bug description: The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter packages makes it impossible to build Orca Master in Ubuntu-MATE 20.04. Reproduction steps: 1. You need to have Ubuntu-MATE 20.04 with the latest updates; 2. Install the following packages: git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev libatspi2.0-dev libatk-bridge2.0-dev 3. Clone the Orca repository: git clone https://gitlab.gnome.org/GNOME/orca.git 4. Navigate to the cloned repository: cd orca 5. Run the command: ./autogen.sh The command output ends with the following lines: checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS and ATKBRIDGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are forcibly downgraded to version 2.34.1-3, this error disappears. Many thanks for fixing this issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 New Install from netboot method ubuntu 20.04 focal same error, I did everything, but nothing worked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
I have experienced the same inconsistencies as reported by OP between Ubuntu 20.04 guest and hosts. The guest is connected through SPICE. On top of that, the clipboard has been working unreliably within the host system (i3). For example, I often have to copy multiple times the same text to have it enter the system clipboard. Moreover, calls to clipboard with CTRL+V can take a few seconds. When the guest is powered off, the issue does not resurface. I have tried to reproduce the issue with Debian 10 and other guests, with no “luck”. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries
Hi, is there any updates for this? I see this issue in xubuntu 20.04 (and previously 19.10). It clogs up the .xsessions-errors file periodically until I run out of disk space. A temporary fix is to write a cron job to empty this file if it exceeds some threshold -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries Status in network-manager-applet package in Ubuntu: Confirmed Bug description: I hope I am in the right place for this. My .xsession-errors file is filled with entries in the following format, in that order/sequence, over and over and continuously: (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which has a parent Ubuntu MATE 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1755305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries
Hi, is there any updates for this? I see this issue in xubuntu 20.04 (and previously 19.10). It clogs up the .xsessions-errors file periodically until I run out of disk space. A temporary fix is to write a cron job to empty this file if it exceeds some threshold -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries Status in network-manager-applet package in Ubuntu: Confirmed Bug description: I hope I am in the right place for this. My .xsession-errors file is filled with entries in the following format, in that order/sequence, over and over and continuously: (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which has a parent Ubuntu MATE 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1755305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Have the same issue on a lot of laptop in my company, we have a webteam that work with Ubuntu and i update all machines for the last version 19.10, after this update all laptops don't have a internal micro. Model: HP 830 G6 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Have the same issue on a lot of laptop in my companie, we hame a webteam that work with Ubuntu and i update all machines for the last version 19.10, after this update all laptops don't have a internal micro. Model: HP 830 G6 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825741]
I can't reproduce this with current master and Unity environment. Which DE are you using? Can you try with a recent daily build? -- 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/1825741 Title: [upstream] Multiple instances of global menu entries Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Triaged Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113420] Re: Alt+ window menu shortcuts cannot be disabled
A little workaround that I found the alt-r key does not trigger for me the HUD. So I reprogrammed my keyboard alt-l to be alt-r as well. works for me. I hope it helps until this is fixed/changed. NOTE. I do have a programmable keyboard. I do not know if it works with software keymapping solution -- 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/1113420 Title: Alt+ window menu shortcuts cannot be disabled Status in Unity: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I find the key ergonomically very useful (it can be pressed with a thumb without moving any of the "letter" fingers) and I would like to use it for many custom keyboard shortcuts (there is a reason why it plays such a big role in Emacs and the whole OS X for that matter). Currently, though, is hardcoded to activate window menu entries (such as +F for the file menu, +E for the edit menu) and there is no way to surpass this functionality in all the applications. Personally, I find these shortcuts quite useless - they take you to "copy", "paste", and "open file" which have standard shortcuts anyway (with the exception of preferences, which for some reason don't have a standardized shortcut even though that's often the only thing a person looks for up there). Expected behaviour - What I would like to see is a global option to disable these alt+ menu shortcuts to free up the key for other uses (similar to the option already available in gnome-terminal, only global). Preferably, activating this option would also remove the first-letter underlining in the menu to indicate to users that they can't acess it through shortcuts. To reproduce: - - in Unity settings -> keyboard -> Shortcuts -> Launchers change the "Launch terminal" shortcut to ALT+T - hit -t, new terminial pops up - start Thunderbird or Okular, both of which have a "Tools" menu - note -t now opens the Tools menu - kill the application - hit -t, nothing happens (I marked nautilus for apport to collect my version numbers, but this affects most applications - didn't know what the right target is) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 2 13:22:32 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'931x626+1+80'" b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationDate: Installed on 2012-10-19 (106 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1113420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825741]
*** Bug 122287 has been marked as a duplicate of this bug. *** -- 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/1825741 Title: [upstream] Multiple instances of global menu entries Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Triaged Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825741]
Regression caused by https://cgit.freedesktop.org/libreoffice/core/commit/?id=3bedbfd9b3cee5a8d2da6ee0486859bd725979ba (bug 121555) -- 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/1825741 Title: [upstream] Multiple instances of global menu entries Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: Triaged Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790979] Re: Unable to change disk decryption passphrase
This bug occurred for me with a fresh installation of Ubuntu 19.04. I created a new installation of Ubuntu 19.04 on a empty disk and checked the box to encrypt the installation. After the installation I tried to change the password and got locked out. This is the output of sudo cryptsetup luksDump /dev/sda3 after the failed attempt to change my password: LUKS header information Version:2 Epoch: 4 Metadata area: 16384 [bytes] Keyslots area: 1678 [bytes] UUID: 233e3965-3d97-4619-969e-ab9ef9b379d8 Label: (no label) Subsystem: (no subsystem) Flags: (no flags) Data segments: 0: crypt offset: 16777216 [bytes] length: (whole device) cipher: aes-xts-plain64 sector: 512 [bytes] Keyslots: Tokens: Digests: 0: pbkdf2 Hash: sha256 Iterations: 37406 Salt: ec 30 aa 1b 97 ef d1 a5 fb b4 1f ba 58 a9 f6 6d e9 d8 c4 73 b4 1b b9 c0 52 ff bf 2f e9 93 d8 47 Digest: f3 dd bb 32 f3 69 45 26 76 86 9a c4 4c d4 41 d4 67 bc f1 10 b3 65 87 d6 3b 51 1d 52 f1 d6 1d 9f -- 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/1790979 Title: Unable to change disk decryption passphrase Status in gnome-disk-utility package in Ubuntu: Confirmed Status in gnome-disk-utility package in Arch Linux: New Bug description: Versions: Ubuntu 18.04 LTS gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 -- What I'm trying to do: Change the disk decryption passphrase of key in any slot other than slot 0 while there is an existing key in slot 0 (e.g. changing the disk decryption passphrase of slot 1) using gnome-disk-utility. Ran "Disks" > Selected my encrypted device partition > Clicked the gear icon > Selected "Change passphrase" > Entered the passphrase I wanted to change > Entered the passphrase I wanted to change to and confirmed it > clicked "Change". -- What I expected to happen: After clicking "Change" I expected to get no errors and have the passphrase I wanted to change to be valid to decrypt the disk. In the event of an error I expected the passphrase I was trying to change to still be valid to decrypt the disk. -- What is happening: I get an error message pop-up: Error changing passphrase Error changing passphrase on device /dev/sda2/:Failed to add the new passphrase: Invalid argument (udisks-error-quark, 0) And the key that I was trying to change gets deleted with no new key being added. -- (Before trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt: 89 e5 16 e5 e0 5d f5 63 f6 ba 2b f1 df e8 e6 1d 11 52 27 39 ff 87 4c 70 ab b7 49 a2 97 e0 46 41 MK iterations:101875 UUID: c5754fe4-0835-431f-996b-e2202c380d05 Key Slot 0: ENABLED Iterations: 42 Salt: cb 25 fd 7d 14 ca af f1 6a 57 b9 b7 b8 7a 45 76 9e 9b 3f ef 6a 3a e7 f6 18 24 7a 6e bb 0d 36 78 Key material offset:8 AF stripes: 4000 Key Slot 1: ENABLED Iterations: 2074334 Salt: c2 cc 91 12 25 f4 80 21 d2 fa 91 44 ef 02 04 3e 6d d8 85 ef b2 39 fb c2 94 f1 62 ee db 79 3c ed Key material offset:264 AF stripes: 4000 Key Slot 2: ENABLED Iterations: 2090878 Salt: 47 fa 77 b7 f8 31 dc 48 ab 58 f7 25 a4 d5 c7 be 35 a3 83 6a 4d 1d bb 24 1c 38 12 2d f1 15 40 7f Key material offset:520 AF stripes: 4000 Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED -- (After trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt:
Re: [Desktop-packages] [Bug 1826944] Re: green bars in ubuntu videos
Hi, I fixed the my problem with this command: sudo apt-get remove gstreamer1.0-vaapi. On Mon, Apr 29, 2019 at 10:25 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please: > > 1. Attach a screenshot or photo of the problem. > > 2. Tell us which video player apps are affected. > > 3. Try this: > >sudo apt install mpv > >and then use 'mpv VIDEOFILE.mp4'. Does it have the same problem? > > 4. Run: > >vainfo > vainfo.txt > >and send us the resulting file 'vainfo.txt'. > > > ** Package changed: xorg (Ubuntu) => totem (Ubuntu) > > ** Changed in: totem (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1826944 > > Title: > green bars in ubuntu videos > > Status in totem package in Ubuntu: > Incomplete > > Bug description: > When I try to play a .mp4 video in Ubuntu Video, I get a screen with > green bars all over. The problem does not occur when I switch to my > nvidia graphics card. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > Uname: Linux 5.0.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Apr 29 19:02:44 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] > Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] > [1043:1590] > InstallationDate: Installed on 2019-04-28 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > MachineType: ASUSTeK COMPUTER INC. GL753VE > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic > root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/16/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: GL753VE.307 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: GL753VE > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ROG > dmi.product.name: GL753VE > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1826944/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1826944 Title: green bars in ubuntu videos Status in totem package in Ubuntu: Incomplete Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti
[Desktop-packages] [Bug 1826944] [NEW] green bars in ubuntu videos
Public bug reported: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- 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/1826944 Title: green bars in ubuntu videos Status in xorg package in Ubuntu: New Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
But scripts changing between scancode and ascii/unicode (such as for some terminal emulation, dosbox, etc.) would break. I'm not saying they are widespread, but I have seen this kind of use, and requiring such flag will suddenly break them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
How will kbd_mode know whether it's safe or not? Adding a -f option to kbd_mode will at best break some *other* existing scripts, while this very script should really definitely *NOT* pass -f to setupcon. That is the nonsense which needs to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
That is when updating the console-setup package, yes. As mentioned on https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146/comments/73 that's because its config script passes --force to setupcon, it really shouldn't, as mentioned there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xorg can't do anything about intercepting Alt-key, it's the kernel which takes the shortcut away. Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source /console-setup/+bug/520546/comments/66 « proposed fix: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch. » Can somebody with t he proper rights do something about this? That patch exists since months now... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Is there really any reason why keyboard-configuration.postinst passes --force to setupcon? In Debian we do this in the Debian installer because it is running within a bterm and thus can't detect it's running on the Linux console. But we never do this for an installed system. Apparently Ubuntu took that code snipped and dropped the check for being running within the Debian installer, and thus erroneously run with --force when DISPLAY is empty (typically from unattended upgrades and such), with the resulting observed effects of this bug report. I guess Ubuntu wants to apply the attached patch ** Attachment added: "proposed fix" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+attachment/5227479/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 571956] Re: sd_generic breaks speech-dispatchter
Charlie: do you have the espeak package installed? It is needed to have espeak-generic working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/571956 Title: sd_generic breaks speech-dispatchter Status in Speech Dispatcher: New Status in speech-dispatcher package in Ubuntu: Triaged Bug description: Binary package hint: speech-dispatcher The Lucid version of speech-dispatcher running the sd_generic module interface currently breaks speech out from speechd. Steps to reproduce uncomment espeak generic from ~/.speech-dispatcher/speechd.conf restart speech-dispatcher run orca from the terminal and pick espeak generic from the voice engine list. Watch the terminal. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: speech-dispatcher 0.6.8~unofficial~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Fri Apr 30 01:06:22 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: PATH=(cusUser Name, no user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: speech-dispatcher To manage notifications about this bug go to: https://bugs.launchpad.net/speech-dispatcher/+bug/571956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
** Attachment added: "File dialog in home folder" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+attachment/5202301/+files/chromium-snap-open-file.png -- 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/1798450 Title: [snap] File dialogs show snap's home directory instead of user's Status in chromium-browser package in Ubuntu: New Bug description: How to reproduce: - Find a web page that has a file chooser (you can just paste `` into an empty HTML page) - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798450] [NEW] [snap] File dialogs show snap's home directory instead of user's
Public bug reported: How to reproduce: - Find a web page that has a file chooser (you can just paste `` into an empty HTML page) - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1798450 Title: [snap] File dialogs show snap's home directory instead of user's Status in chromium-browser package in Ubuntu: New Bug description: How to reproduce: - Find a web page that has a file chooser (you can just paste `` into an empty HTML page) - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750243] Re: [snap] StartupWMClass missing in .desktop file
I've got the same issue in the Ubuntu 18.10 beta. snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Also, Chromium's "Add shortcut..." function (which is broken in the Chromium snap, but the deb version does it as well) makes use of the StartupWMClass for Chromium extensions and web apps: `StartupWMClass=crx_okkolgldfknecfjnhhglfopimelbaceh` And thus, when no "pure" Chromium window is opened but a Chromium web app is, opening Chromium will cause the Gnome shell to group the two icons under the name of the app (as it's the same executable without a distinguishable StartupWMClass, if I'm right). With `StartupWMClass=chromium` added to /var/lib/snapd/desktop/applications/chromium_chromium.desktop it works as expected. ** Attachment added: "Alt-tab menu showing a window of Chromium grouped with the Chromium web app "Twitter"" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1750243/+attachment/5202300/+files/chromium-no-startupwmclass.png -- 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/1750243 Title: [snap] StartupWMClass missing in .desktop file Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium Snap Version 64.0.3282.167 How to reproduce: In Gnome: Add the Chromium Snap to the left launcher panel. Start the Chromium Snap. Actual behavior: The Chromium snap starts and creates a new symbol in the launcher panel. Desired behavior: The Chromium snap should start using the symbol which is already pinned to the launcher panel. In Budgie: The Chromium Snap cannot be pinned to the panel at all. Possible solution: Add StartupWMClass= ... to the .desktop launcher of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1750243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792820] [NEW] help you me
Public bug reported: I don#t know what i am doing. How can I help you? help you me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 22:33:39 2018 DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d] InstallationDate: Installed on 2016-10-16 (700 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X102BA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago) dmi.bios.date: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X102BA.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X102BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X102BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 3 23:15:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1792820 Title: help you me Status in xorg package in Ubuntu: New Bug description: I don#t know what i am doing. How can I help you? help you me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 22:33:39 2018 DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d] InstallationDate: Installed on 2016-10-16 (700 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X102BA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago) dmi.bios.date: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X102BA.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X102BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X102BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
Dell XPS 15 9560 Ubuntu 18.04.1 4.15.0-32-generic Speakers work fine. Headphones are detected when plugged in and sound no longer plays from the speakers, but no sound comes through the headphones. -- 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/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
>From the upstream policykit bug entry, it is actually a misuse of the policykit API from brltty. I have uploaded a fix in Debian's brltty 5.6-5. Ubuntu should definitely include the policykit-fix patch contained in that 5.6-5 version as an update to ubuntu 18.04, otherwise all blind users will have the issue, thus unable to use the graphical desktop. ** Package changed: policykit-1 (Ubuntu) => brltty (Ubuntu) ** Changed in: brltty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in brltty package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Yes, disabling that patch fixes the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
This is most probably due to the introduction of Fix-CVE-2018-1116 -Trusting-client-supplied-UID.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
I can confirm the same issue on Debian: upgrading from version 0.105-20 to version 0.105-21 brings the same issue. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1116 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Note: to reproduce the issue, one just needs to install an Ubuntu 18.04 system, start brltty by hand as root with: sudo brltty -b no then try to connect to it as normal logged-in user through brlapi: python3 >>> import brlapi >>> b = brlapi.Connection() which shouldn't raise an exception. Logs can be seen in /var/log/syslog (unfortunately the current package source code only prints errno instead of the GError). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
This seems to be an issue within policykit itself. Printing the actual error shows: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: process with PID 12570 has been replaced >From reading the source code, it seems that policykit is checking the start time of the program and finds a mismatch. It happens that orca is run as a Python script, so I thought that might be due to the script startup procedure, but starting a C brlapi client gives the same issue. At any rate, really looks like not an issue in brltty itself. ** Package changed: brltty (Ubuntu) => policykit-1 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in policykit-1 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Well, this is not a real solution, we need to fix polkit, otherwise all users will have the same issue, and we don't want to make them all revert back to file-based authentication. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in brltty package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1140716]
I doesn't seem to be getting mentioned Gnome crashes on my sandybridge anymore with mainline kernels, that is currently 4.11 and I think even with 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default centos 7 kernels I am definitely getting very frequent GPU crashes that brings down Gnome. So it is either fixed for good, or it become much rarer. The issue I am/was experiencing happens when Gnome is running, it does not happen when only GDM is loaded. System load seems to not have effect on the bug triggering, seems to happen any time, on idle, or when machine is loaded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in DRI: Won't Fix Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in linux source package in Precise: Fix Committed Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in mesa source package in Precise: Triaged Status in linux source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux package in Debian: New Status in linux package in Fedora: Won't Fix Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [] ? __switch_to+0x12b/0x420 [26285.658612] [] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [] process_one_work+0x12a/0x420 [26285.658629] [] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [] worker_thread+0x12e/0x2f0 [26285.658636] [] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [] kthread+0x93/0xa0 [26285.658644] [] kernel_thread_helper+0x4/0x10 [26285.658649] [] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer
[Desktop-packages] [Bug 1041790]
I doesn't seem to be getting mentioned Gnome crashes on my sandybridge anymore with mainline kernels, that is currently 4.11 and I think even with 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default centos 7 kernels I am definitely getting very frequent GPU crashes that brings down Gnome. So it is either fixed for good, or it become much rarer. The issue I am/was experiencing happens when Gnome is running, it does not happen when only GDM is loaded. System load seems to not have effect on the bug triggering, seems to happen any time, on idle, or when machine is loaded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in xf86-video-intel: Won't Fix Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476088] Re: Rhythmbox can't resume play on (m4a) podcast
The problem is still present in Rhythmbox 3.4.2 on Ubuntu 18.04 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1476088 Title: Rhythmbox can't resume play on (m4a) podcast Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Triaged Bug description: I'm subscribed to a number of podcasts that are hosted and served by Apple iTunes. As such, the file format is m4a, which may be the root of this problem. Once the podcast is playing, I'll pause playback using either the controls that appear when clicking the volume control in the Unity system tray, or by just using the regular playback controls in Rhythmbox. To resume playback I press the play button, but play does not resume. I must move the scrubber to a new location before playback will resume. Ubuntu 14.04.2 LTS rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Version table: *** 3.0.2-0ubuntu2 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1476088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Hi,
I do confirm proposed worked also for me on a Dell XPS 15 9530.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Committed
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1766951] [NEW] package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrad
Public bug reported: I was trying to update Ubuntu and it wouldnt stop crashing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 14:45:00 2018 DuplicateSignature: package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ... dpkg: error processing archive /var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:i386 InstallationDate: Installed on 2018-04-12 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gst-plugins-base0.10 Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1766951 Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins- base0.10-0:i386 Status in gst-plugins-base0.10 package in Ubuntu: New Bug description: I was trying to update Ubuntu and it wouldnt stop crashing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 14:45:00 2018 DuplicateSignature: package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ... dpkg: error processing archive /var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:i386 InstallationDate: Installed on 2018-04-12 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gst-plugins-base0.10 Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/1766951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759009] [NEW] software bug
Public bug reported: I ran the installed x diagnosis software. The software found the bug. I have no idea what the problem is. My Ubuntu Apps application will not work. I tried removing and reinstall the application but it still will not work. I installed gnome-software as a work around but that doesn't seem to work either. I believe my Ubuntu 16.04 lts original installation is faulty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 12:02:22 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e] InstallationDate: Installed on 2018-03-23 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Precision M4700 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=6126fabd-0eaf-4345-ac41-42b5013ac682 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 082H3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/09/2017:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn082H3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1759009 Title: software bug Status in xorg package in Ubuntu: New Bug description: I ran the installed x diagnosis software. The software found the bug. I have no idea what the problem is. My Ubuntu Apps application will not work. I tried removing and reinstall the application but it still will not work. I installed gnome-software as a work around but that doesn't seem to work either. I believe my Ubuntu 16.04 lts original installation is faulty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 12:02:22 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e] InstallationDate: Installed on 2018-03-23 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Precision M4700 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
lasakro, stu: which USB ID does your device have? (otherwise we can't know what to fix in brltty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1485373] Re: Missing dependency - gnome-disk-utility needs cryptsetup
*** This bug is a duplicate of bug 1310174 *** https://bugs.launchpad.net/bugs/1310174 Present in 17.10 -- 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/1485373 Title: Missing dependency - gnome-disk-utility needs cryptsetup Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: gnome-disk-utility version 3.14.0 as installed on Ubuntu Mate 15.04 from the Ubuntu repositories installs the following package: The following extra packages will be installed: cracklib-runtime libcrack2 libpwquality-common libpwquality1 The following NEW packages will be installed: cracklib-runtime gnome-disk-utility libcrack2 libpwquality-common libpwquality1 gnome-disk-utility allows the user to create an encrypted file system. If the user attempts to create an encrypted partition where no partition exists, the program will crash. If the user attempts to format an existing partition as "Type: Encrypted, compatible with Linux systems (LUKS + Ext4)" the following error message is presented: Error creating LUKS device: Error spawning command-line `cryptsetup luksFormat ""/dev/sdb1""': Failed to execute child process "cryptsetup" (No such file or directory) (g-exec-error-quark, 8) (udisks-error-quark, 0) If the cryptsetup package is installed with apt-get the issue is resolved and gnome-disk-utility will create or format a partition/file system as LUKS + Ext4. Cryptsetup should be installed as a dependency when installing gnome- disk-utilities. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-disk-utility (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: i386 CurrentDesktop: MATE Date: Sun Aug 16 16:16:30 2015 InstallationDate: Installed on 2015-08-11 (5 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1485373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
I don't know how ubuntu manages that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
I have pushed the AT_SPI_BUS removal patch to branch https://code.launchpad.net/~samuel-thibault/lightdm-gtk-greeter/at-spi- bus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Still now news on this and #1366534 ? This is really hurting users... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1006754] Re: Archive Manager cannot open docx files
Upstream bug is here: https://bugzilla.gnome.org/show_bug.cgi?id=685896 ** Bug watch added: GNOME Bug Tracker #685896 https://bugzilla.gnome.org/show_bug.cgi?id=685896 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1006754 Title: Archive Manager cannot open docx files Status in File Roller: New Status in file-roller package in Ubuntu: Confirmed Bug description: In Ubuntu 12.04, Archive Manager fails to open a .docx or .odf files. In previous versions of Ubuntu (11.04, 11.10) this action is possible, AM can open a such files for viewing its content if user chose to right click->open with archive manager. Since .docx and .odf files are XML documents, user should be able to view the content of the file (images, text and stuff are all compressed in a single file with docx/odf extension). But in 12.04 the Archive Manager is unable to open files with that extensions, declaring "Archive type not supported". This bug is identical to bug #973675 (for 12.04 beta) which was converted to question #192668 which has expired. In my opinion it is still a bug however. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1006754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
The problem is happening here too. thanks jingles it worked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Just to confirm that the approch proposed by Luke is sound. Removing the AT_SPI_BUS property would really be the safest for the user session: even if systemd doesn't manage to properly clean the at-spi dbus, at least the session isn't exposed to its existence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718321] [NEW] package texlive-latex-extra-doc (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/share/doc/texlive-doc/latex/shipunov/altve
Public bug reported: Não entendi o porque de dar esse problema ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-latex-extra-doc (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 19 02:18:31 2017 ErrorMessage: não pode copiar dados extráidos para './usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf' para '/usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: texlive-extra Title: package texlive-latex-extra-doc (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf' para '/usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1718321 Title: package texlive-latex-extra-doc (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/share/doc /texlive-doc/latex/shipunov/altverse-ex2-ru.pdf' para '/usr/share/doc /texlive-doc/latex/shipunov/altverse-ex2-ru.pdf.dpkg-new': fim de ficheiro ou stream inesperado Status in texlive-extra package in Ubuntu: New Bug description: Não entendi o porque de dar esse problema ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-latex-extra-doc (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 19 02:18:31 2017 ErrorMessage: não pode copiar dados extráidos para './usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf' para '/usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: texlive-extra Title: package texlive-latex-extra-doc (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf' para '/usr/share/doc/texlive-doc/latex/shipunov/altverse-ex2-ru.pdf.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1718321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
I followed Julien Scordia #83 and upgraded to 17 loosing the LTS. Problem solved with this version, no issue in two month. -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Confirmed Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697692] [NEW] package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Public bug reported: I have no further details since I don't know the precise thing that has failed. I hope the logs are enough for you, sorry not to be more helpful. Thank you a lot! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 13 14:23:13 2017 DpkgTerminalLog: dpkg: error processing package libpoppler-qt5-1:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2017-06-01 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: poppler Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1697692 Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in poppler package in Ubuntu: New Bug description: I have no further details since I don't know the precise thing that has failed. I hope the logs are enough for you, sorry not to be more helpful. Thank you a lot! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 13 14:23:13 2017 DpkgTerminalLog: dpkg: error processing package libpoppler-qt5-1:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2017-06-01 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: poppler Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1697692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Hi, I was having the same issue, but the fix suggested by Juan Hernandez at #32 seems to have worked! I had to install xserver-xorg-core before I could install xserver-xorg- input-libinput, but it seems to work now! -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664320] Re: xbrlapi loopback interface abuse
Hello, This was reported in debian http://bugs.debian.org/851623 , and that led to upstream fix https://github.com/brltty/brltty/commit/0a5341121ba8f4de24407ce2a4d5369dadf5d099 ** Bug watch added: Debian Bug tracker #851623 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851623 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1664320 Title: xbrlapi loopback interface abuse Status in brltty package in Ubuntu: New Bug description: Xbrlapi creates new TCP connections in port 4101 at loopback interface. These are closed instantly because there is no service listening at 4101 on the lo interface. Xbrlapi should not do that if there is no braille device. This might pose a security risk, but I have not verified it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xbrlapi 5.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 13 19:25:58 2017 InstallationDate: Installed on 2015-07-31 (562 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: brltty UpgradeStatus: Upgraded to yakkety on 2016-11-01 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1664320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664055] [NEW] Simple Scan keeps crashing. I don't know what's going on.
Public bug reported: It's on my userside only I want it fixed. How can it be fixed? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CurrentDesktop: Unity Date: Sun Feb 12 12:27:00 2017 InstallationDate: Installed on 2015-09-12 (518 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Gigabyte Technology Co., Ltd. H81M-S1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=ea6cfc38-278c-4ea6-8b63-1807c476901e ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-10-20 (115 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FF dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFF:bd06/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-S1 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1664055 Title: Simple Scan keeps crashing. I don't know what's going on. Status in simple-scan package in Ubuntu: New Bug description: It's on my userside only I want it fixed. How can it be fixed? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CurrentDesktop: Unity Date: Sun Feb 12 12:27:00 2017 InstallationDate: Installed on 2015-09-12 (518 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Gigabyte Technology Co., Ltd. H81M-S1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=ea6cfc38-278c-4ea6-8b63-1807c476901e ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-10-20 (115 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FF dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFF:bd06/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-S1 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1664055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)
This can probably be closed. After receiving my tablet back from BQ with the s/n, mac addresses, etc. reset, I haven't had this problem since. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1607684 Title: wifi networks not remembered correctly (ubuntu touch, bq M10) Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have a M10, on ubuntu touch OTA-12 (and same issue previously on OTA-11). The issue is that it doesn't remember wifi networks properly. To explain: 1. turn on tablet 2. select my wifi network from the list 3. enter password and click connect 4. reboot device 5. select my wifi network from the list 6. enter password and click connect . . . 30. go to wifi settings -> previous networks 31. view long list that looks like: MyWifinetwork1 MyWifinetwork2 MyWifinetwork3 MyWifinetwork4 ... What it should do (and did some time ago), is see that MyWifinetwork was saved in previous networks and automatically connect using the saved password/settings. So, I'm wondering is this a bug, something badly configured in my wifi network (although other devices remember it fine), or something else? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476088] Re: Rhythmbox can't resume play on (m4a) podcast
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=775781 ** Bug watch added: GNOME Bug Tracker #775781 https://bugzilla.gnome.org/show_bug.cgi?id=775781 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1476088 Title: Rhythmbox can't resume play on (m4a) podcast Status in rhythmbox package in Ubuntu: New Bug description: I'm subscribed to a number of podcasts that are hosted and served by Apple iTunes. As such, the file format is m4a, which may be the root of this problem. Once the podcast is playing, I'll pause playback using either the controls that appear when clicking the volume control in the Unity system tray, or by just using the regular playback controls in Rhythmbox. To resume playback I press the play button, but play does not resume. I must move the scrubber to a new location before playback will resume. Ubuntu 14.04.2 LTS rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Version table: *** 3.0.2-0ubuntu2 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1476088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476088] Re: Rhythmbox can't resume play on (m4a) podcast
The problem is still present in Rhythmbox 3.3-1ubuntu7 on Ubuntu 16.04.1 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1476088 Title: Rhythmbox can't resume play on (m4a) podcast Status in rhythmbox package in Ubuntu: New Bug description: I'm subscribed to a number of podcasts that are hosted and served by Apple iTunes. As such, the file format is m4a, which may be the root of this problem. Once the podcast is playing, I'll pause playback using either the controls that appear when clicking the volume control in the Unity system tray, or by just using the regular playback controls in Rhythmbox. To resume playback I press the play button, but play does not resume. I must move the scrubber to a new location before playback will resume. Ubuntu 14.04.2 LTS rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Version table: *** 3.0.2-0ubuntu2 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1476088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
Hello, I have the same issue. I reported a bug and made it duplicate of this one, including full ubuntu-bug xorg data. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288 ** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Confirmed Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626288] Re: X fonts and widgets disappear after suspend/resume cycle
*** This bug is a duplicate of bug 1434351 *** https://bugs.launchpad.net/bugs/1434351 I wanted to add my report to an existing bug : https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351 using exactly the same title and based on https://help.ubuntu.com/community/ReportingBugs info, I expected the launchpad to propose me to add to it instead of creating a new one. ** This bug has been marked a duplicate of bug 1434351 X fonts and widgets disappear after suspend/resume cycle -- 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/1626288 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: New Bug description: not all the time, but at some suspend/resume operations fonts disapear from gnome terminal, nm-applet and soffice which then show spaces and underscore placeholders instead of characters. google chrome, thunderbird, firefox, virtualbox are not affected. As it happens not at each suspend resume I find it hard to diagnose what is going wrong. next time I will launch more apps to see wich ones are affected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... CompizPlugins: (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running CompositorRunning: None CurrentDesktop: i3 Date: Wed Sep 21 23:41:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:6504] InstallationDate: Installed on 2016-07-27 (56 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook W65_67SZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05SB.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 21 23:08:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5941 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626288] [NEW] X fonts and widgets disappear after suspend/resume cycle
*** This bug is a duplicate of bug 1434351 *** https://bugs.launchpad.net/bugs/1434351 Public bug reported: not all the time, but at some suspend/resume operations fonts disapear from gnome terminal, nm-applet and soffice which then show spaces and underscore placeholders instead of characters. google chrome, thunderbird, firefox, virtualbox are not affected. As it happens not at each suspend resume I find it hard to diagnose what is going wrong. next time I will launch more apps to see wich ones are affected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... CompizPlugins: (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running CompositorRunning: None CurrentDesktop: i3 Date: Wed Sep 21 23:41:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:6504] InstallationDate: Installed on 2016-07-27 (56 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook W65_67SZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05SB.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 21 23:08:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5941 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1626288 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: New Bug description: not all the time, but at some suspend/resume operations fonts disapear from gnome terminal, nm-applet and soffice which then show spaces and underscore placeholders instead of characters. google chrome, thunderbird, firefox, virtualbox are not affected. As it happens not at each suspend resume I find it hard to diagnose what is going wrong. next time I will launch more apps to see wich ones are affected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks [[0;1;31mFAILED[0m] Failed to start
[Desktop-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB
See discussion at: https://github.com/joewing/jwm/issues/194 ** Bug watch added: github.com/joewing/jwm/issues #194 https://github.com/joewing/jwm/issues/194 ** Changed in: jwm (Ubuntu) Status: New => Invalid ** Changed in: jwm (Ubuntu) Assignee: (unassigned) => Samuel Henrique (samueloph) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in Compiz: Triaged Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: New Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Triaged Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: New Status in mutter package in Ubuntu: New Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: New Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1030022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)
Ok. "You will have lost your S/N, MAC addresses, and some key material the HDMI software expects to find (but does not use)." What partition(s) keep that data? (Asking because I'm trying to gather data for discussing with BQ.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1607684 Title: wifi networks not remembered correctly (ubuntu touch, bq M10) Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have a M10, on ubuntu touch OTA-12 (and same issue previously on OTA-11). The issue is that it doesn't remember wifi networks properly. To explain: 1. turn on tablet 2. select my wifi network from the list 3. enter password and click connect 4. reboot device 5. select my wifi network from the list 6. enter password and click connect . . . 30. go to wifi settings -> previous networks 31. view long list that looks like: MyWifinetwork1 MyWifinetwork2 MyWifinetwork3 MyWifinetwork4 ... What it should do (and did some time ago), is see that MyWifinetwork was saved in previous networks and automatically connect using the saved password/settings. So, I'm wondering is this a bug, something badly configured in my wifi network (although other devices remember it fine), or something else? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)
Ouch. What a way to learn about imei... Is this then a fault with the flash tool I used? (I mean an official tool from the manufacturer isn't supposed to destroy the device...) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1607684 Title: wifi networks not remembered correctly (ubuntu touch, bq M10) Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have a M10, on ubuntu touch OTA-12 (and same issue previously on OTA-11). The issue is that it doesn't remember wifi networks properly. To explain: 1. turn on tablet 2. select my wifi network from the list 3. enter password and click connect 4. reboot device 5. select my wifi network from the list 6. enter password and click connect . . . 30. go to wifi settings -> previous networks 31. view long list that looks like: MyWifinetwork1 MyWifinetwork2 MyWifinetwork3 MyWifinetwork4 ... What it should do (and did some time ago), is see that MyWifinetwork was saved in previous networks and automatically connect using the saved password/settings. So, I'm wondering is this a bug, something badly configured in my wifi network (although other devices remember it fine), or something else? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
