[Bug 1966911] Re: Cannot enroll finger on Jammy

[Vincent Gerris]

I tested this on Noble ( 24.04 ) and it also works with 
https://launchpad.net/~andch/+archive/ubuntu/staging-fprint/+packages . When is 
the package going to land in main repositories ?
Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966911

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1911237] Re: Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black (lose signal) after logging in

[Vincent Gerris]

The AN40 with latest firmware does not give any picture at all on my
Asus ROG flow 13 and a bunch of other devices. USB works, no screen
device, HDMI or DP.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911237

Title:
  Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go
  black (lose signal) after logging in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1911237/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1911237] Re: Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black (lose signal) after logging in

[Vincent Gerris]

that's on wayland by the way

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911237

Title:
  Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go
  black (lose signal) after logging in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1911237/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966911] Re: Cannot enroll finger on Jammy

[Vincent Gerris]

hi Andy, that is great, will it be posted here? For people interested,
the message above confirming it works is on a Dell XPS 9500, Dell
Precision 5550 and Dell XPS 9700.

Andy, what do you mean with only in Jammy main? As in not in future releases?
Included in main would be great, then it can 'just work' via extra drivers or 
directly.

I believe I had to wipe the prints specifically for one laptop, but
otherwise it just works.

Thank you for the help and your work!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966911

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2000077] Re: Download URLs are broken

[Vincent Gerris]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/277

Title:
  Download URLs are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/277/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2000077] Re: Download URLs are broken

[Vincent Gerris]

looks like related work has been done :
https://bugs.launchpad.net/ubuntu/+source/onionshare/+bug/2048769

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/277

Title:
  Download URLs are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/277/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2000077] Re: Download URLs are broken

[Vincent Gerris]

I filed : https://bugs.launchpad.net/ubuntu/+source/torbrowser-
launcher/+bug/2058927 - I suppose either can be closed as duplicate if
picked up, wanted to mention the patch and tor updates.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/277

Title:
  Download URLs are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/277/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058927] [NEW] torbrowser-launcher gives 404 and does not install browser

[Vincent Gerris]

Public bug reported:

There are multiple things wrong with getting torbrowser to work.
First of all, the shipped torbrowser-launcher gives a 404 at installation :

https://bugs.launchpad.net/ubuntu/+source/torbrowser-
launcher/+bug/277

It also looks like some gpg keys may have been updated.

There is a tor repo that has the latest tor :
https://community.torproject.org/onion-services/setup/install/

I propose to either pull that in, or fix the current package.

A workaround for the current version 0.3.3 is
 sudo sed -i 's|self.language =.*|self.language = "ALL"|g' 
/usr/lib/python3/dist-packages/torbrowser_launcher/common.py

This updates the links properly. As user @AsciiWolf mentions, check if
this patch needs to be in place :

https://github.com/torproject/torbrowser-
launcher/commit/7472ff6b374eaed7382ae6016b516b84954c18e3

I saw Debian has 0.3.6 , perhaps an update is coming soon. The current
package has no value I would say, hoping this will be fixed soon. Thank
you

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: torbrowser-launcher 0.3.3-6ubuntu1.22.04.1 [modified: 
usr/lib/python3/dist-packages/torbrowser_launcher/common.py]
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: Mon Mar 25 13:35:47 2024
InstallationDate: Installed on 2023-10-20 (157 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: torbrowser-launcher
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: torbrowser-launcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058927

Title:
  torbrowser-launcher gives 404 and does not install browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2058927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1519691] Re: Launcher unable to download tarball

[Vincent Gerris]

sudo sed -i 's|self.language =.*|self.language = "ALL"|g' 
/usr/lib/python3/dist-packages/torbrowser_launcher/common.py might be a 
workaround on 22.04. Since this was filed for 15.04 , there is another bug for 
22.04 : 
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/277

It seems this bug relies on testing which doesn't make much sense for 15.04, I 
propose to close it?
Thank you

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519691

Title:
  Launcher unable to download tarball

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1519691/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2000077] Re: Download URLs are broken

[Vincent Gerris]

This is valid for jammy , 22.04 . The fix there is :  
sudo sed -i 's|self.language =.*|self.language = "ALL"|g' 
/usr/lib/python3/dist-packages/torbrowser_launcher/common.py 

Or indeed an upgrade to a newer version.
Ubuntu, please update or fix this, thank you

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/277

Title:
  Download URLs are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/277/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966911] Re: Cannot enroll finger on Jammy

[Vincent Gerris]

I have tested this with 
https://launchpad.net/ubuntu/jammy/amd64/libfprint-2-2/1:1.94.3+tod1-0ubuntu2~22.04.01
 and Bus 001 Device 005: ID 27c6:533c Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
 and it works great.

Are there any plans to make this part of a main included repo ?
Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966911

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966911] Re: Cannot enroll finger on Jammy

[Vincent Gerris]

I still get an enroll error with the staging driver unfortunately...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966911

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966911] Re: Cannot enroll finger on Jammy

[Vincent Gerris]

Same issue on my Dell Inspiron 5482 with:
Bus 001 Device 003: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader

which used to work on 20.04 LTS.
Will the goodix driver need to be updated?
Anyway, happy to test, thanks for reporting

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966911

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970396] [NEW] freecad pivy dependency broken python 3.10

[Vincent Gerris]

Public bug reported:

Freecad does not load workbenches like draft and others in Ubuntu 22.04 LTS 
with Python3 as default.
Ubuntu 22.04 has python 3.10 and it appears there is a breaking change there:

https://groups.google.com/g/linux.debian.bugs.dist/c/77OUZs8MJNs?pli=1

The error that is thrown is :

 returned a result with an 
exception set
Traceback (most recent call last):
  File "", line 433, in Activated
  File "/usr/share/freecad/Mod/Draft/draftguitools/gui_snapper.py", line 1635, 
in show
self.setTrackers()
  File "/usr/share/freecad/Mod/Draft/draftguitools/gui_snapper.py", line 1679, 
in setTrackers
self.grid = trackers.gridTracker()
  File "/usr/share/freecad/Mod/Draft/draftguitools/gui_trackers.py", line 974, 
in __init__
pick.style.setValue(coin.SoPickStyle.UNPICKABLE)
  File "/usr/lib/python3/dist-packages/pivy/coin.py", line 3989, in __getattr__
field = self.getField(name)
  File "/usr/lib/python3/dist-packages/pivy/coin.py", line 3873, in getField
return _coin.SoFieldContainer_getField(self, name)


Expect to happen : loading draft workbench, no error.
Also happens when enabling raster, the raster does not load.

The above link show this issue to be fixed :
https://github.com/coin3d/pivy/pull/91 and tracked upsgream at 
https://github.com/coin3d/pivy/issues/88
so likely just needs a freecad upgrade here.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: freecad 0.19.2+dfsg1-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 11:53:09 2022
InstallationDate: Installed on 2019-12-17 (860 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: freecad
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: freecad (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970396

Title:
  freecad pivy dependency broken python 3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1970396/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

update : sorry, not my bug - so not closing. needs confirmation. fprint
is fixed, the sensor may not work. unlcear if that is part of this bug.
leaving it to the owner, thank you

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

resolved in the bug mentioned. closing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944369] Re: Crash with fprintd 1.92.0

[Vincent Gerris]

I can confirm this version no longer crashes with the goodix driver. I
am unable to make the fingerprint reader work, it enrolls with an error
and complains about no storage. Seperate issue I suppose? thanks for the
fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944369

Title:
  Crash with fprintd 1.92.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

related :
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962344] Re: fprintd fails to start through core-dump

[Vincent Gerris]

tracked in
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962344

Title:
  fprintd fails to start through core-dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962344] Re: fprintd fails to start through core-dump

[Vincent Gerris]

I found the issue, I had this installed from the Dell repo for 20.04 LTS:
libfprint-2-tod1-goodix
more specifically:
libfprint-2-tod1-goodix_0.0.6-0ubuntu1_somerville1_amd64.deb

This worked great with 20.04 and the fprintd version in there, but apparently 
it breaks the current version.
Seems I have to wait untill Dell/goodix releases a new version.

I will close this one since the issue is not with fprintd itself.

** Changed in: fprintd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962344

Title:
  fprintd fails to start through core-dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

I have a similar Goodix device.
I reported :
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344

They may be related. 
Snippet from my journalctl:

ubuntu@ubuntu-inspiron-5482:~$ journalctl -b 0 | grep fprintd
feb 25 21:09:27 ubuntu-inspiron-5482 sudo[12402]:   ubuntu : TTY=pts/0 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/apt install fprintd
feb 25 21:10:14 ubuntu-inspiron-5482 dbus-daemon[1737]: [system] Activating via 
systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested 
by ':1.153' (uid=1000 pid=12715 comm="fprintd-list ")
feb 25 21:10:15 ubuntu-inspiron-5482 kernel: fprintd[12718]: segfault at 40 ip 
7f96fd1b2056 sp 7ffe9717a980 error 4 in 
libusb-1.0.so.0.3.0[7f96fd1a8000+f000]
feb 25 21:10:15 ubuntu-inspiron-5482 kernel: fprintd[12723]: segfault at 40 ip 
7f96fd1b2056 sp 7f96f2ffca60 error 4 in 
libusb-1.0.so.0.3.0[7f96fd1a8000+f000]
feb 25 21:10:15 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: 
INFO:root:Collecting info for /var/crash/_usr_libexec_fprintd.0.crash...
feb 25 21:10:16 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=dumped, status=11/SEGV
feb 25 21:10:16 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'core-dump'.
feb 25 21:10:20 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: 
INFO:root:Marking /var/crash/_usr_libexec_fprintd.0.crash for whoopsie upload
feb 25 21:10:20 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 20 s): /var/crash/_usr_libexec_fprintd.0.uploaded 
/var/crash/_usr_libexec_tracker-miner-fs-3.1000.uploaded
feb 25 21:10:30 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 10 s): /var/crash/_usr_libexec_fprintd.0.uploaded
feb 25 21:10:40 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 0 s): /var/crash/_usr_libexec_fprintd.0.uploaded
feb 25 21:14:02 ubuntu-inspiron-5482 polkitd(authority=local)[1769]: Operator 
of unix-session:2 successfully authenticated as unix-user:root to gain 
TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for 
system-bus-name::1.165 [systemctl restart fprintd.service] (owned by 
unix-user:ubuntu)
feb 25 21:14:03 ubuntu-inspiron-5482 kernel: fprintd[13512]: segfault at 40 ip 
7f49958e0056 sp 7ffd6ef58100 error 4 in 
libusb-1.0.so.0.3.0[7f49958d6000+f000]
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=dumped, status=11/SEGV
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'core-dump'.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962344] Re: fprintd fails to start through core-dump

[Vincent Gerris]

reference to login bug:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336

snippet from journalctl:
ubuntu@ubuntu-inspiron-5482:~$ journalctl -b 0 | grep fprintd
feb 25 21:09:27 ubuntu-inspiron-5482 sudo[12402]:   ubuntu : TTY=pts/0 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/apt install fprintd
feb 25 21:10:14 ubuntu-inspiron-5482 dbus-daemon[1737]: [system] Activating via 
systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested 
by ':1.153' (uid=1000 pid=12715 comm="fprintd-list ")
feb 25 21:10:15 ubuntu-inspiron-5482 kernel: fprintd[12718]: segfault at 40 ip 
7f96fd1b2056 sp 7ffe9717a980 error 4 in 
libusb-1.0.so.0.3.0[7f96fd1a8000+f000]
feb 25 21:10:15 ubuntu-inspiron-5482 kernel: fprintd[12723]: segfault at 40 ip 
7f96fd1b2056 sp 7f96f2ffca60 error 4 in 
libusb-1.0.so.0.3.0[7f96fd1a8000+f000]
feb 25 21:10:15 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: 
INFO:root:Collecting info for /var/crash/_usr_libexec_fprintd.0.crash...
feb 25 21:10:16 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=dumped, status=11/SEGV
feb 25 21:10:16 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'core-dump'.
feb 25 21:10:20 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: 
INFO:root:Marking /var/crash/_usr_libexec_fprintd.0.crash for whoopsie upload
feb 25 21:10:20 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 20 s): /var/crash/_usr_libexec_fprintd.0.uploaded 
/var/crash/_usr_libexec_tracker-miner-fs-3.1000.uploaded
feb 25 21:10:30 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 10 s): /var/crash/_usr_libexec_fprintd.0.uploaded
feb 25 21:10:40 ubuntu-inspiron-5482 whoopsie-upload-all[12725]: INFO:root:  
missing (remaining: 0 s): /var/crash/_usr_libexec_fprintd.0.uploaded
feb 25 21:14:02 ubuntu-inspiron-5482 polkitd(authority=local)[1769]: Operator 
of unix-session:2 successfully authenticated as unix-user:root to gain 
TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for 
system-bus-name::1.165 [systemctl restart fprintd.service] (owned by 
unix-user:ubuntu)
feb 25 21:14:03 ubuntu-inspiron-5482 kernel: fprintd[13512]: segfault at 40 ip 
7f49958e0056 sp 7ffd6ef58100 error 4 in 
libusb-1.0.so.0.3.0[7f49958d6000+f000]
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=dumped, status=11/SEGV
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'core-dump'.


possibly related:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633

from my comment there:
files updates in /etc/pam.d :
-rw-r--r-- 1 root root 1415 feb 9 15:15 gdm-smartcard-sssd-or-password
-rw-r--r-- 1 root root 1373 feb 9 15:15 gdm-smartcard-sssd-exclusive
-rw-r--r-- 1 root root 1408 feb 9 15:15 gdm-smartcard-pkcs11-exclusive
-rw-r--r-- 1 root root 1320 feb 9 15:15 gdm-password
-rw-r--r-- 1 root root 383 feb 9 15:15 gdm-launch-environment
-rw-r--r-- 1 root root 1342 feb 9 15:15 gdm-fingerprint
-rw-r--r-- 1 root root 1192 feb 9 15:15 gdm-autologin

gdm-fingerprint references:
auth required pam_fprintd.so
password required pam_fprintd.so

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962344

Title:
  fprintd fails to start through core-dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962344] [NEW] fprintd fails to start through core-dump

[Vincent Gerris]

Public bug reported:

some more info :
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=dumped, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit fprintd.service has exited.
░░ 
░░ The process' exit code is 'dumped' and its exit status is 11.
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit fprintd.service has entered the 'failed' state with result 
'core-dump'.
feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint 
Authentication Daemon.
░░ Subject: A start job for unit fprintd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit fprintd.service has finished with a failure.
░░ 
░░ The job identifier is 4596 and the job result is failed.
ubuntu@ubuntu-inspiron-5482:~$ dpkg -l fprintd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  fprintd1.94.2-1 amd64D-Bus daemon for fingerprint 
reader access

if the fprintd package is installed and fprintd-enroll is run, it times out.
That triggers a bug in gdm3 at login, where the user account is not visibe and 
one cannot login.

I have a goodix fingerprint reader:
Bus 001 Device 002: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.2-1
Uname: Linux 5.12.19-051219-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 25 21:19:31 2022
InstallationDate: Installed on 2019-12-17 (801 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fprintd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962344

Title:
  fprintd fails to start through core-dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen when fprintd crashes

[Vincent Gerris]

Hi,

I think the most obvious is to have the fprintd bug tracked in the appropriate 
bug, and have this one track login not working.
I looked at the link and do not understand what you need.
There are some files in /var/crash that end in uploaded, I presume they are 
uploaded?

The last one for fprintd is attached here.


** Attachment added: "fprint crash report"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+attachment/5562099/+files/_usr_libexec_fprintd.0.uploaded

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen when fprintd crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen when fprintd is installed and not starting

[Vincent Gerris]

** Summary changed:

- No login screen when fprintd is installed
+ No login screen when fprintd is installed and not starting

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen when fprintd is installed and not starting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen when fprintd is installed

[Vincent Gerris]

hi, it seems it does not start. 
output from terminal:

ubuntu@ubuntu-inspiron-5482:~$ sudo apt install fprintd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  fprintd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/97,4 kB of archives.
After this operation, 680 kB of additional disk space will be used.
Selecting previously unselected package fprintd.
(Reading database ... 424549 files and directories currently installed.)
Preparing to unpack .../fprintd_1.94.1-1_amd64.deb ...
Unpacking fprintd (1.94.1-1) ...
Setting up fprintd (1.94.1-1) ...
fprintd.service is a disabled or a static unit not running, not starting it.
Processing triggers for dbus (1.12.20-2ubuntu2) ...
Processing triggers for man-db (2.10.1-1) ...
ubuntu@ubuntu-inspiron-5482:~$ systemctl restart fprintd.service 
Job for fprintd.service failed because a fatal signal was delivered to the 
control process.
See "systemctl status fprintd.service" and "journalctl -xeu fprintd.service" 
for details.
ubuntu@ubuntu-inspiron-5482:~$ systemctl status fprintd.service
× fprintd.service - Fingerprint Authentication Daemon
 Loaded: loaded (/lib/systemd/system/fprintd.service; static)
 Active: failed (Result: signal) since Thu 2022-02-17 00:20:25 CET; 15s ago
   Docs: man:fprintd(1)
Process: 33083 ExecStart=/usr/libexec/fprintd (code=killed, signal=SEGV)
   Main PID: 33083 (code=killed, signal=SEGV)
CPU: 531ms

feb 17 00:20:23 ubuntu-inspiron-5482 systemd[1]: Starting Fingerprint 
Authentication Daemon...
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=killed, status=11/SEGV
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'signal'.
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint 
Authentication Daemon.
ubuntu@ubuntu-inspiron-5482:~$ journalctl -xeu fprintd.service
░░ 
░░ The job identifier is 2235.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit fprintd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 11.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit fprintd.service has entered the 'failed' state with result 'signal'.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint 
Authentication Daemon.
░░ Subject: A start job for unit fprintd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit fprintd.service has finished with a failure.
░░ 
░░ The job identifier is 2235 and the job result is failed.

there is also a bug here :
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633 that may
be related?

Thanks for the heads up, hope these things will be solved.

Still seems like a good idea in the context of this bug to handle
fprintd not working gracefully?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen when fprintd is installed and not starting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

files updates in /etc/pam.d :
-rw-r--r-- 1 root root 1415 feb  9 15:15 gdm-smartcard-sssd-or-password
-rw-r--r-- 1 root root 1373 feb  9 15:15 gdm-smartcard-sssd-exclusive
-rw-r--r-- 1 root root 1408 feb  9 15:15 gdm-smartcard-pkcs11-exclusive
-rw-r--r-- 1 root root 1320 feb  9 15:15 gdm-password
-rw-r--r-- 1 root root  383 feb  9 15:15 gdm-launch-environment
-rw-r--r-- 1 root root 1342 feb  9 15:15 gdm-fingerprint
-rw-r--r-- 1 root root 1192 feb  9 15:15 gdm-autologin

gdm-fingerprint references:
authrequiredpam_fprintd.so
password required   pam_fprintd.so

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

5.12.19-051219-generic #202107201136 SMP Tue Jul 20 16:58:52 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux is the kernel.

This triggers a gdm3 login bug where no user shows up for login in gdm3:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'

[Vincent Gerris]

this is an issue in 22.04 dev.
Failed to get Fprintd manager: Error calling StartServiceByName for 
net.reactivated.Fprint: Timeout was reached

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933633

Title:
  Failed to activate service 'net.reactivated.Fprint'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

confirmed that after reinstalling fprintd, the issue returns.
First of all, it creates a delay until the login screen loads.
then when the login screen loads, no user is visible to be clicked, also not 
after the 25000 ms timeout of the fprintd daemon.

So it seems the cause of the issue is the login process in gdm3 is not
handling this properly - ideally the user would get a message like -
fprintd error: timeout xxx etc and the login would skip fingerprint
related stuff and go to normal login.

This is currently broken when the command fprintd-list times out like:
gnome-shell[2622]: Failed to connect to Fprint service: Error calling 
StartServiceByName for net.reactivated.Fprint: Timeout was reached

current work around:
drop to safe login and type:
apt remove fprintd
reboot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

I tracked down the cause, it has to do with sssd and how gdm3 handles it.
Similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1534873

First I removed kerberos auth, which did not seem to have had an effect.
Then I saw that fprintd was showing errors and fprintd-list was throwing the 
same error as in the logs.

I removed it and after that it worked.
So it seems like a bug in sssd related to fingerprint auth, when that is not 
working properly.

Regarding evdi - as you wrote, can be addressed separately. As I wrote ,
it does NOT work properly for me, not the beta driver, not even on 5.13
with beta driver. I just installed 5.12 kernel and latest release driver
because the beta does not work properly on my system - I use a D6000
Dell dock.

Regarding this bug - I will try to see if I can get frintd to work. I
still have Ubuntu sessions showing that do not work, not sure where they
came from, this is even after I purged gnome gnome-shell and gnome-
session. can login now with gdm3 and gnome session.

Is there anything else you need to pursue this ?

** Bug watch added: Red Hat Bugzilla #1534873
   https://bugzilla.redhat.com/show_bug.cgi?id=1534873

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

from the newly installed system with 20.04, warnings came for 
/var/lib/gdm3.config and .local not being empty.
root@ubuntu-inspiron-5482:/var/lib/gdm3# ls -lrta
total 32
drwxr-xr-x   3 root root 4096 feb  5 12:33 .config
drwx--   3 gdm  gdm  4096 feb  5 12:34 .nv
drwx--   4 gdm  gdm  4096 feb  5 12:35 .local
drwx--   6 gdm  gdm  4096 feb  5 12:35 .cache
drwxr-xr-x 101 root root 4096 feb  5 12:37 ..
-rw-r--r--   1 gdm  gdm   feb 13 23:26 greeter-dconf-defaults
drwx--x--x   6 gdm  gdm  4096 feb 13 23:26 .
is what that looks like on the broken system.

On the one with warning, it shows 755 instead of 700 permissions.
There is also no .nv dir.
I will wipe it out, reinstall and see what happens.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, this machine has not been much customised. I only switched display manager 
because the supplied one did not work. I cannot reinstall and lose data.
Display link does not work on at least 2 of my systems with kernel 5.13 and 
they reopened a bug because I reported it - those drivers are always behind and 
rather unstable in my experience, especially with nouveau currently.

I hope devs can come up with a better answer because I bet a lot of folks will 
run into this issue.
I uninstalled caffeine, removed plugins from /usr/share and the problem remains.
I would say I am rather handy with Linux, that is why I run dev builds 
sometimes and report issues.
If I want buggy drivers and no support I can just install windows, man even 
macOS runs better on both machines.
Please notify the gdm3 devs and gnome-extensions ones, because stuff changed 
there.
You can also close the bug, but I am not gonna waste my time on finding the 
issue anymore then.
Isn´t the whole point of open source software that users make it better :)?

Also, I the time of reporting was right after the update, so it can´t be too 
hard to find.
This issue does not occur on another machine with a recent install of 20.04 and 
having that updated. That said, this machine certainly does not go further back 
than 18.04, I think actually 20.04 too.

How about we try to find the cause? You have not answered the question about 
where to find this plugins that are in the bug report, like xcaffeine.
thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, I tried, same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, I did :
ubuntu@ubuntu-inspiron-5482:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  gdm3   41.3-1ubuntu2 amd64GNOME Display Manager

The extensions do not show up in the extensions app, I cannot find a trace 
anywhere.
A screenshot is attached from the app ( that in fact does not seem to follow 
the theme :) ).

Also no extensions show on extensions.gnome.org/local.
Thank you again for the quick reply!

** Attachment added: "gnome extensions screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+attachment/5560236/+files/Screenshot%20from%202022-02-10%2009-18-38.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

Hi Daniel,

Where can I find these extensions?
They are not in apt search, .local/share/gnome-shell/extensions or in 
extensions app.

I did an apt get update and installed the new gdm3 version you mention.
Then sudo dpkg-reconfigure gdm3 and now it actually showed me the choice 
between lightdm and gdm3 ( did not do that on previous version).

Unfortunately, the result is the same.
I get a black screen. If I try other ttys, some show a flashing cursor, but I 
can´t do anything.
The off button responds so the system is not hanging.

Also did a reinstall of gnome-shell package, no success.
So a photo would just be a black screen :).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] monitors.xml.txt

[Vincent Gerris]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559963/+files/monitors.xml.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

lspci output

** Attachment added: "lspci -k output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+attachment/5559965/+files/lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] ShellJournal.txt

[Vincent Gerris]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559962/+files/ShellJournal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

ran apport and added files, thank you.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+attachment/5559964/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] ProcEnviron.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559961/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  After a recent update, when using gdm3 as login manager, there is no account 
visible and it is not possible to login. 
  When switching to lightdm I can login but sleep is broken and some 
notifications do not work.
  Running the latest 22.04 dev branch with Wayland and Nvidia driver.
  Had to select kernel 5.12 to have display link working.
  This issue occurs with and without external displays attached.
  A recent attempt to switch back to gdm3 gave me just a black screen.
  
  I tried to reinstall gdm3 to no avail.
  This seems like a quite serious issue, hence this report for the dev version.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu76
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: lightdm
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2019-12-17 (784 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ NonfreeKernelModules: nvidia_modeset wl nvidia
+ Package: gnome-shell 41.3-1ubuntu1
+ PackageArchitecture: amd64
+ RelatedPackageVersions: mutter-common 41.3-1ubuntu1
+ Tags: third-party-packages jammy
+ Uname: Linux 5.12.19-051219-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559958/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] ProcCpuinfoMinimal.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559960/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] GsettingsChanges.txt

[Vincent Gerris]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559959/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  No login screen after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960336] [NEW] no login screen on Wayland with gdm3 after recent update

[Vincent Gerris]

Public bug reported:

After a recent update, when using gdm3 as login manager, there is no account 
visible and it is not possible to login. 
When switching to lightdm I can login but sleep is broken and some 
notifications do not work.
Running the latest 22.04 dev branch with Wayland and Nvidia driver.
Had to select kernel 5.12 to have display link working.
This issue occurs with and without external displays attached.
A recent attempt to switch back to gdm3 gave me just a black screen.

I tried to reinstall gdm3 to no avail.
This seems like a quite serious issue, hence this report for the dev version.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336

Title:
  no login screen on Wayland with gdm3 after recent update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910821] Re: [snap] chromium fails to start with "/snap/chromium/1444/usr/lib/chromium-browser/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No su

[Vincent Gerris]

same here, all data gone. what a shit show, like waking up after a car
crash feeling fine but no memory. Perhaps devs can consider these kind
of things before these things happen.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910821

Title:
  [snap] chromium fails to start with
  "/snap/chromium/1444/usr/lib/chromium-browser/chrome: error while
  loading shared libraries: libatk-1.0.so.0: cannot open shared object
  file: No such file or directory"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1910821/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Vincent Gerris]

workaround for me to get sound, not mic:
/etc/modprobe.d/alsa-base.conf 
options snd-intel-dspcfg dsp_driver=1

reference : https://bbs.archlinux.org/viewtopic.php?id=260139

still no mic though.
Some more dmesg :

dmesg | grep audio
[5.670976] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[5.751918] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC215: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[5.751928] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[5.751932] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[5.751937] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[5.751939] snd_hda_codec_realtek hdaudioC0D0:inputs:
[5.751942] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
vinger@vinger-HP-EliteBook-830-G6:~$ dmesg | grep firm
[4.444306] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/kbl_dmc_ver1_04.bin (v1.4)
[4.498913] iwlwifi :3a:00.0: loaded firmware version 59.601f3a66.0 
cc-a0-59.ucode op_mode iwlmvm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Vincent Gerris]

I still have this issue on latest kernel for 20.04 LTS:
5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

snippet from journalctl | grep sof-audio :

jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
DSP detected with PCI class/subclass/prog-if info 0x040100
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
Digital mics found on Skylake+ platform, using SOF driver
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
enabling device ( -> 0002)
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
DSP detected with PCI class/subclass/prog-if 0x040100
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
bound :00:02.0 (ops i915_audio_component_bind_ops [i915])
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
use msi interrupt mode
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
hda codecs found, mask 5
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
using HDA machine driver skl_hda_dsp_generic now
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
DMICs detected in NHLT tables: 4
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
Firmware info: version 2:0:0-b678a
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
Firmware: ABI 3:20:0 Kernel ABI 3:18:0
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
warn: FW ABI is more recent than kernel
jan 16 00:32:35 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
unknown sof_ext_man header type 3 size 0x30
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: cl_dsp_init: timeout HDA_DSP_SRAM_REG_ROM_STATUS read
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: status = 0x panic = 0x
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: extended rom status:  0x621 0x0 0x0 0x0 0x0 0x0 0x1811102 0x0
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: dsp init failed after 3 attempts with err: -110
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
ROM error=0x: FW status=0x
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: failed to reset DSP
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: failed to boot DSP firmware -110
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: hda_dsp_core_reset_enter: timeout on HDA_DSP_REG_ADSPCS read
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: dsp core reset failed: core_mask f
jan 16 00:32:36 vinger-HP-EliteBook-830-G6 kernel: sof-audio-pci :00:1f.3: 
error: sof_probe_work failed err: -110

I tried to update files in /lib/firmware/intel/sof from here : 
https://github.com/thesofproject/sof-bin
with no luck.

Please let me know if more info is needed - just have a Dummy device as others 
have.
Thank you

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871011] Re: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)

[Vincent Gerris]

update: when I shut down the printer with the usb cable connected and
then start it again it works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871011

Title:
  USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd
  conflict)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871011] Re: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)

[Vincent Gerris]

I seem to have a similar issue with my HP ENVY 5544.
After removing ippusbxd and stopping the related service, my printer still does 
not print.
Dmesg shows this every time I press the test page button in either HP tools or 
Printers (GNOME GUI):

usblp1: removed

So it seems the device is removed everytime it gets a command.
The print job ends up in the queue but never gets processed, also not after 
reconnect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871011

Title:
  USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd
  conflict)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[Vincent Gerris]

Hi,

If you read the bug you can see that it works when the proprietary Nvidia
drivers are installed. It works otherwise.


On Sat, Mar 13, 2021, 05:20 retro <1912...@bugs.launchpad.net> wrote:

> Hi Vincent, I am interested in buying that laptop. Currently it works
> well or do you have a problem with this model?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1912509
>
> Title:
>   usci_acpi USBC000:00: PPM init failed (-110)
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe
> drives I get:
>   usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.
>
>   kernel 5.4.0-26-generic usually boots (but get an occasional freeze).
>
>   Since I cannot boot in the 5.8 kernel I cannot file the bug with that
>   kernel running.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.4.0-26-generic 5.4.0-26.30
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.14
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  vincent1381 F pulseaudio
>/dev/snd/controlC0:  vincent1381 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jan 20 17:28:23 2021
>   InstallationDate: Installed on 2021-01-20 (0 days ago)
>   InstallationMedia:
>
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
>Bus 001 Device 003: ID 8087:0026 Intel Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic
> root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-26-generic N/A
>linux-backports-modules-5.4.0-26-generic  N/A
>linux-firmware1.187.8
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: FX506LI.307
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: FX506LI
>   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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.family: ASUS TUF Gaming F15
>   dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912509

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[Vincent Gerris]

hi,

Not sure what that message means precisely, but after that the system 
completely hangs.
I installed the nvidia driver and that works wiht 5.8 kernel, as others wrote 
on Stackoverflow.
So this is a kernel / nouveau bug?

The nvidia driver is not supported because it is proprietary and would
like to have the nouveau driver working.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912509

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[Vincent Gerris]

The laptop runs the latest 3.07 bios. I think the issue does not occur
with only one NVMe drive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912509

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912509] [NEW] usci_acpi USBC000:00: PPM init failed (-110)

[Vincent Gerris]

Public bug reported:

When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe drives 
I get:
usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

Since I cannot boot in the 5.8 kernel I cannot file the bug with that
kernel running.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vincent1381 F pulseaudio
 /dev/snd/controlC0:  vincent1381 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 20 17:28:23 2021
InstallationDate: Installed on 2021-01-20 (0 days ago)
InstallationMedia:
 
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
 Bus 001 Device 003: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic  N/A
 linux-firmware1.187.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX506LI.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX506LI
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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ASUS TUF Gaming F15
dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912509

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

So a valid workaround for me, perhaps for others.
It's nice to see other workarounds too, I hope this bug will be fixed in a way 
that this works without any application/terminal settings or hacks, so with 
proprietary driver and fractional scaling.
I don't want to change font size, multiple settings across apps and such, just 
have a single point to change that works, just like in other major OSes :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736

Title:
  [nvidia] Screen scaling 125% gives 200%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857383

Title:
  Fractional scaling applies to both monitors when you only want it on
  one

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1857383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)

[Vincent Gerris]

try the 5.4.x or 5.6.x oem kernel (I'm running Ubuntu 20.04 LTS).

Bus 001 Device 002: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
works for me.

Also check:
https://www.reddit.com/r/Dell/comments/hq3kf3/xps_13_fingerprint_drivers_are_here/

They make my device with the above id work, it might work for yours.

Check :
https://git.launchpad.net/~oem-solutions-engineers/libfprint-2-tod1-goodix/+git/libfprint-2-tod1-goodix
for more info.

Also, you may need to run:
sudo pam-auth-update
and enable fingerprint to have it work for login.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721909

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  lsusb(usbutils)

To manage notifications about this bug go to:
https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel

[Vincent Gerris]

Thank you for the workaround and the patch.
I tested this and got :

ubuntu@ubuntu-inspiron-5482:~$ sudo dkms install bcmwl/6.30.223.271+bdcom -k all
Error! Your kernel headers for kernel all cannot be found.
Please install the linux-headers-all package,
or use the --kernelsourcedir option to tell DKMS where it's located

Then I did :
sudo apt install --reinstall  linux-headers-5.6.0-1007-oem
(because I didn't know the location)
and it worked.

Does anyone know where the patch can be applied to?
I will ping the maintainer I had contact with in the past for Ubuntu so I hope 
this can be merged soon.

Thanks a lot for your contribution !

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872908

Title:
  bcmwl kernel module does not build with 5.6.0 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872908] [NEW] bcmwl kernel module does not build with 5.6.0 kernel

[Vincent Gerris]

Public bug reported:

After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.

The make log shows:

ubuntu@ubuntu-inspiron-5482:~$ cat 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
  CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
  |  ^~~
  |  ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
warning: returning ‘int’ from a function with return type ‘void *’ makes 
pointer from integer without a cast [-Wint-conversion]
  949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
  | ~^~~~
In file included from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
 warning: this statement may fall through [-Wimplicit-fallthrough=]
   52 |  if (wl_dbg_level & WL_DBG_DBG) {   \
  | ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
 note: in expansion of macro ‘WL_DBG’
  816 |   WL_DBG(("network eap\n"));
  |   ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
 note: here
  817 |  default:
  |  ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function 
‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: 
error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == 
NULL) {
  |^~~
  |ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: 
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a 
cast [-Wint-conversion]
  593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == 
NULL) {
  |  ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function 
‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: 
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
  780 |  if ((val & 0xff00) != 0)
  |  ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: 
...this statement, but the latter is misleadingly indented as if it were 
guarded by the ‘if’
  782 |   bar1_size = pci_resource_len(pdev, 2);
  |   ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
  783 |   bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
  |   ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function 
‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: 
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
 3376 |  if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops, wl)) 
== NULL) {
  |  ^~~~
  |  |
  |  const struct 
file_operations *
In file included from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:38:
./include/linux/proc_fs.h:59:31: note: expected ‘const struct proc_ops *’ but 
argument is of type ‘const struct file_operations *’
   59 | extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
  |   ^~~~
cc1: some warnings being treated as errors
make[1]:

[Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel

[Vincent Gerris]

other info:
ubuntu@ubuntu-inspiron-5482:~$ dkms status
bcmwl, 6.30.223.271+bdcom, 5.3.0-26-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 5.4.0-1002-oem, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 5.4.0-21-generic, x86_64: installedError! Could not 
locate dkms.conf file.
File: /var/lib/dkms/evdi/5.2.14/source/dkms.conf does not exist.

evdi, 1.6.0+dfsg, 5.4.0-1002-oem, x86_64: built

The hardware is a Dell DW1560.

Tried to reinstall with:
sudo dkms install bcmwl/6.30.223.271+bdcom

which gave above output.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872908

Title:
  bcmwl kernel module does not build with 5.6.0 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)

[Vincent Gerris]

I think this should not be closed.
I have :
Bus 001 Device 003: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
in my lsusb output, but there is no driver loaded and thus fprintd cannot be 
setup.

For this specific ticket there is a driver request at the project:
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/161

I think it should be linked to that.

Let's hope the folks there or perhaps Dell will fix this, or any other savvy 
developer.
Until then, I think this bug report should remain open to track it.
For other device IDs bugs should be opened too ideally.
I hope this helps.


** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #161
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/161

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721909

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  lsusb(usbutils)

To manage notifications about this bug go to:
https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure

[Vincent Gerris]

16.04 LTS is supported until April 2020 (maintenance), so it's
recommended to use 18.04 LTS (18.10 not being LTS and short in support,
see : https://ubuntu.com/about/release-cycle ).

This bug does not apply to fresh installs (although it may be related) while 
wiping the disk, see initial post.
Make sure to check your BIOS settings (EFI/non-EFI, boot sector protection) and 
please post a new full bug report with full details if you have issues ( I 
suggest on 18.04 LTS).
Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766945

Title:
  (EFI on top of legacy install) choosing "replace" or "resize" options
  in partitioning may lead to an install failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1766945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1517491] Re: installation fails due to broken dependencies

[Vincent Gerris]

This is also reported in :
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1809828

I have this issue on the up to date Ubuntu 18.04 LTS today (used this 
workaround :
https://askubuntu.com/questions/1088662/npm-depends-node-gyp-0-10-9-but-it-is-not-going-to-be-installed).

Seems like a dependency issue of the npm package to me, which should be
fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517491

Title:
  installation fails due to broken dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1517491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1517491] Re: installation fails due to broken dependencies

[Vincent Gerris]

this seems like a dependency issue in the npm package and a side effect of that.
Also reported in :
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1809828

I think one of them should be closed, the other seems a bit clearer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517491

Title:
  installation fails due to broken dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1517491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1809828] Re: Cannot install the npm package: dependency broken

[Vincent Gerris]

I still have this issue with the most recent updates on Ubuntu 18.04. 
Also reported here:
https://askubuntu.com/questions/1088662/npm-depends-node-gyp-0-10-9-but-it-is-not-going-to-be-installed

this bug is related to it:
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1517491

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809828

Title:
  Cannot install the npm package: dependency broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1809828/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 156201] Re: gedit handles opening big files badly

[Vincent Gerris]

Nano is not a gui desktop editor. Besides that vim is superior to nano in
my opinion. A viable alternative would be an open source editor like Atom,
but it can be useful to have a lightweight simple editor that doesn't blow
up with a big file and is installed by default.

On Wed, Jan 23, 2019, 21:45 madbiologist <156...@bugs.launchpad.net
wrote:

> This needs to be fixed.  In the meantime, try using nano.  Unfortunately
> nano doesn't have syntax highlighting.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/156201
>
> Title:
>   gedit handles opening big files badly
>
> Status in gedit:
>   Confirmed
> Status in gedit package in Ubuntu:
>   Triaged
>
> Bug description:
>   Binary package hint: gedit
>
>   Opening big text files (400 MB, 750 MB) in gedit is bad
>   - from a usability standpoint
> -> There's no progress bar or cancel button for the action, and the
> load takes a long time.
>   - from a system standpoint:
> -> In earlier versions, gedit would take so much memory until the
> system swapped all other applications to disk, and the system became
> unusable.
> -> Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but
> the message "failed to allocate  bytes" in the console.
>
>
>
>   Original description:
>   I just opened a 400 MB text file (mbox mail file) in gedit, and it my
> system has now been unresponsive for minutes. Other editors can open large
> files without a problem. Also, there's no progress bar or cancel button
> that would make it easy to see how long gedit is loading the file or to
> cancel the load.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/156201

Title:
  gedit handles opening big files badly

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] Re: cheese doesn't show video on Asus N55SF

[Vincent Gerris]

somehow this bug was filed against linux, changed it to cheese (the
webcam software) and added missing logfiles, marked as confirmed.

** Package changed: linux (Ubuntu) => cheese (Ubuntu)

** Changed in: cheese (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] Lsusb.txt

[Vincent Gerris]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1788725/+attachment/5180132/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] ProcCpuinfoMinimal.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180134/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] PulseList.txt

[Vincent Gerris]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180138/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] ProcModules.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180137/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] ProcCpuinfo.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180133/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] CurrentDmesg.txt

[Vincent Gerris]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180129/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] RfKill.txt

[Vincent Gerris]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1788725/+attachment/5180139/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] Lspci.txt

[Vincent Gerris]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1788725/+attachment/5180131/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] WifiSyslog.txt

[Vincent Gerris]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180141/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] Re: cheese doesn't show video on Asus N55SF

[Vincent Gerris]

apport information

** Tags added: apport-collected

** Description changed:

  when cheese starts, shortly the view of the webcam is visible and then shows 
an error.
  When run from the command line, the terminal shows:
  
  (cheese:6379): Gtk-WARNING **: 01:08:46.810: Theme parsing error:
  cheese.css:7:35: The style property GtkScrollbar:min-slider-length is
  deprecated and shouldn't be used anymore. It will be removed in a future
  version
  
  (cheese:6379): cheese-WARNING **: 01:08:48.017: Device '/dev/video0' failed 
during initialization: gstv4l2object.c(3698): gst_v4l2_object_set_format_full 
(): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error
  
  the app shows : there was an error displaying the video ..
  
  The Kamerka app works fine, so it's not a driver issue it seems.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 24 01:10:51 2018
  InstallationDate: Installed on 2018-08-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. N55SF
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SF.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SF
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N55SF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kinda  2211 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-08-23 (0 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: ASUSTeK Computer Inc. N55SF
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=f2770e86-a220-4c9a-a3ce-061c8b9f7225 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-33-generic N/A
+  linux-backports-modules-4.15.0-33-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  bionic
+ Uname: Linux 4.15.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/29/2011
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: N55SF.207
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: N55SF
+ 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.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
+ dmi.product.family: N
+ dmi.product.name: N55SF
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK Computer Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180127/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] UdevDb.txt

[Vincent Gerris]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1788725/+attachment/5180140/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] ProcEnviron.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180135/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] ProcInterrupts.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180136/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] CRDA.txt

[Vincent Gerris]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1788725/+attachment/5180128/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] IwConfig.txt

[Vincent Gerris]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1788725/+attachment/5180130/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788725] [NEW] cheese doesn't show video on Asus N55SF

[Vincent Gerris]

Public bug reported:

when cheese starts, shortly the view of the webcam is visible and then shows an 
error.
When run from the command line, the terminal shows:

(cheese:6379): Gtk-WARNING **: 01:08:46.810: Theme parsing error:
cheese.css:7:35: The style property GtkScrollbar:min-slider-length is
deprecated and shouldn't be used anymore. It will be removed in a future
version

(cheese:6379): cheese-WARNING **: 01:08:48.017: Device '/dev/video0' failed 
during initialization: gstv4l2object.c(3698): gst_v4l2_object_set_format_full 
(): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error

the app shows : there was an error displaying the video ..

The Kamerka app works fine, so it's not a driver issue it seems.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cheese 3.28.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 24 01:10:51 2018
InstallationDate: Installed on 2018-08-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK Computer Inc. N55SF
RelatedPackageVersions:
 cheese3.28.0-1ubuntu1
 cheese-common 3.28.0-1ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N55SF.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N55SF
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N55SF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic gstreamer-error

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725

Title:
  cheese doesn't show video on Asus N55SF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 995934] Re: Page content is not visible, only title bar updates

[Vincent Gerris]

Hi Paul,

This is so old that it can be disregarded. Thanks for the late response.

Greetings,
Vincent


On Sat, Aug 18, 2018, 12:29 Paul White <995...@bugs.launchpad.net> wrote:

> Vincent,
>
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu and Firefox since that time.
>
> Do you still see a problem related to the one that you reported? Please
> let us know if you do.
>
> If we do not hear from you this bug report will close in approximately
> 60 days time.
>
> Thank you for helping make Ubuntu better.
>
> Paul White
> [Ubuntu Bug Squad]
>
> ** Changed in: firefox (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/995934
>
> Title:
>   Page content is not visible, only title bar updates
>
> Status in firefox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When the window is resized, content is visible again.
>   in multiple themes.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: firefox 12.0+build1-0ubuntu0.12.04.1
>   ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
>   Uname: Linux 3.2.0-24-generic-pae i686
>   NonfreeKernelModules: nvidia
>   AddonCompatCheckDisabled: False
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>   AplayDevices:
> List of PLAYBACK Hardware Devices 
>card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1
> Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
>   ApportVersion: 2.0.1-0ubuntu7
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  vincent3336 F pulseaudio
>   BuildID: 20120423122624
>   CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1:
> nl80211 not found.
>   Card0.Amixer.info:
>Card hw:0 'Intel'/'HDA Intel at 0xf302 irq 50'
>  Mixer name : 'Realtek ALC662 rev1'
>  Components : 'HDA:10ec0662,103c3647,00100101'
>  Controls  : 24
>  Simple ctrls  : 12
>   Channel: release
>   Date: Mon May  7 14:45:34 2012
>   ForcedLayersAccel: False
>   IpRoute:
>default via 145.52.210.1 dev eth0  proto static
>145.52.210.0/24 dev eth0  proto kernel  scope link  src
> 145.52.210.202  metric 1
>169.254.0.0/16 dev eth0  scope link  metric 1000
>192.168.56.0/24 dev vboxnet0  proto kernel  scope link  src
> 192.168.56.1
>   IwConfig:
>lono wireless extensions.
>
>vboxnet0  no wireless extensions.
>
>eth0  no wireless extensions.
>   ProcEnviron:
>PATH=(custom, user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   Profile1IncompatibleExtensions: Ubuntu Firefox Modifications - ID=
> ubu...@ubuntu.com, Version=0.9.4, minVersion=4.0b6, maxVersion=10.*,
> Location=app-system-share, Type=extension, Active=Yes
>   Profiles:
>Profile0 (Default) - LastVersion=12.0/20120423122624 (Running)
>Profile1 - LastVersion=11.0/20120410144204 (Out of date)
>   RfKill:
>
>   RunningIncompatibleAddons: False
>   SourcePackage: firefox
>   UpgradeStatus: Upgraded to precise on 2012-04-25 (11 days ago)
>   dmi.bios.date: 10/22/2009
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: 786G7 v01.02
>   dmi.board.asset.tag: CZC0091QNT
>   dmi.board.name: 3647h
>   dmi.board.vendor: Hewlett-Packard
>   dmi.chassis.asset.tag: CZC0091QNT
>   dmi.chassis.type: 6
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteCMTPC:pvr:rvnHewlett-Packard:rn3647h:rvr:cvnHewlett-Packard:ct6:cvr:
>   dmi.product.name: HP Compaq 8000 Elite CMT PC
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/995934/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995934

Title:
  Page content is not visible, only title bar updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/995934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786942] [NEW] installer crashed after failing to install grub2

[Vincent Gerris]

Public bug reported:

This happened on install of Ubuntu 18.04.1 LTS.
installation was done on an existing drive with other os, manually 
repartitioned adding swap and root fs. expected to see this complete 
successfully.

when running grub-install /dev/sda from command line it said something
about /cow image.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 14 14:43:45 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786942

Title:
  installer crashed after failing to install grub2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786942/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,

Unfortunately I'm unable to test, I don't have the laptop anymore.

Kind regards,
Vincent


Den mån 9 juli 2018 14:31Łukasz Zemczak <1683...@bugs.launchpad.net> skrev:

> Hello Vincent, or anyone else affected,
>
> Accepted unity-settings-daemon into bionic-proposed. The package will
> build now and be available at https://launchpad.net/ubuntu/+source
> /unity-settings-daemon/15.04.1+18.04.20180413-0ubuntu1.1
> 
> in a few hours,
> and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: unity-settings-daemon (Ubuntu Bionic)
>Status: New => Fix Committed
>
> ** Tags removed: verification-done
> ** Tags added: verification-needed verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683445
>
> Title:
>   E6430 brightness control not working
>
> Status in GNOME Settings Daemon:
>   Fix Released
> Status in Nouveau Xorg driver:
>   Won't Fix
> Status in OEM Priority Project:
>   Confirmed
> Status in gnome-settings-daemon package in Ubuntu:
>   Fix Released
> Status in unity-settings-daemon package in Ubuntu:
>   Fix Released
> Status in gnome-settings-daemon source package in Xenial:
>   Confirmed
> Status in unity-settings-daemon source package in Xenial:
>   Confirmed
> Status in gnome-settings-daemon source package in Zesty:
>   Fix Released
> Status in unity-settings-daemon source package in Zesty:
>   Won't Fix
> Status in unity-settings-daemon source package in Bionic:
>   Fix Committed
>
> Bug description:
>   Impact
>   --
>   It looks like GNOME's brightness control simply used the first backlight
> device it saw instead of one currently in use. This meant that the
> brightness control would not work on some computers with multiple GPUs.
>
>   Test Case
>   -
>   From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
>   Restart.
>   Does the brightness control now work correctly?
>
>   Regression Potential
>   
>   This looks like a minimal fix for this issue. It was accepted as part of
> gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be
> upgrading to.
>
>   Original Bug Report
>   ---
>   The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
> Source Nouveau driver shows the brightness slider moving but does not
> affect the brightness.
>
>   When using the kernel boot option acpi_backlight=vendor , the
>   brightness control works.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: linux-image-4.10.0-19-generic 4.10.0-19.21
>   ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
>   Uname: Linux 4.10.0-19-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu 2081 F pulseaudio
>   CurrentDesktop: Unity:Unity7
>   Date: Mon Apr 17 20:00:56 2017
>   HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
>   InstallationDate: Installed on 2017-04-10 (7 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
>   MachineType: Dell Inc. Latitude E6430
>   ProcFB:
>0 nouveaufb
>1 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed
> root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash
> acpi_backlight=vendor vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-19-generic N/A
>linux-backports-modules-4.10.0-19-generic  N/A
>linux-firmware 1.164
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/18/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A18
>   dmi.board.name: 0H3MT5
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:

Re: [Bug 1771869] Re: [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails

[Vincent Gerris]

hi,

I tested the package by downloading and:
 - it upgrades the current version
 - is able to be removed : I guess that is the main factor
 - can be installed again
 - the database starts and is accessible

Seems like it works, thank you and I hope we see it in Release soon.



On Wed, Jun 6, 2018 at 4:39 PM, Robie Basak <1771...@bugs.launchpad.net>
wrote:

> Hello Corey, or anyone else affected,
>
> Accepted percona-xtradb-cluster-5.7 into bionic-proposed. The package
> will build now and be available at https://launchpad.net/ubuntu/+source
> /percona-xtradb-cluster-5.7/5.7.20-29.24-0ubuntu2.1 in a few hours, and
> then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, details of your
> testing will help us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: percona-xtradb-cluster-5.7 (Ubuntu Bionic)
>Status: Triaged => Fix Committed
>
> ** Tags added: verification-needed verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771869
>
> Title:
>   [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails
>
> Status in percona-xtradb-cluster-5.7 package in Ubuntu:
>   Fix Released
> Status in percona-xtradb-cluster-5.7 source package in Bionic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   Both of the following commands fail:
>
>   apt remove percona-xtradb-cluster-server-5.7
>   apt purge percona-xtradb-cluster-server-5.7
>
>   with:
>
>   Removing percona-xtradb-cluster-server-5.7 (5.7.20-29.24-0ubuntu2) ...
>   dpkg: error processing package percona-xtradb-cluster-server-5.7
> (--remove):
>installed percona-xtradb-cluster-server-5.7 package post-removal
> script subprocess returned error exit status 1
>   Errors were encountered while processing:
>percona-xtradb-cluster-server-5.7
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>   The case statement in the postrm script has a 'purge)' case but no
>   'remove)' case. Therefore when called with the remove parameter (which
>   occurs for both apt purge and apt remove), no match is found in the
>   case statement, and the '*)' path is taken which calls 'exit 1'.
>
>   [Testcase]
>
>   apt remove/purge should be successful. See [Impact] section for
>   failure that should no longer be encountered.
>
>   [Regression Potential]
>   Low. This just updates the postrm script to add a no-op 'remove' case.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-
> cluster-5.7/+bug/1771869/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771869

Title:
  [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.7/+bug/1771869/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771869] Re: [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails

[Vincent Gerris]

hi, when will the package be available ? I have the same issue :

dpkg: error processing package percona-xtradb-cluster-server-5.7 (--purge):
 installed percona-xtradb-cluster-server-5.7 package post-removal script 
subprocess returned error exit status 1
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
 percona-xtradb-cluster-server-5.7

I work around apt being stuck with:
sudo apt install --reinstall percona-xtradb-cluster-server-5.7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771869

Title:
  [SRU] apt purge/remove percona-xtradb-cluster-server-5.7 postrm fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.7/+bug/1771869/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption

[Vincent Gerris]

I see the same error but do not seem to get a high load on 18.04 dev.
The package name is gnome-power-statistics 3.25.90-2 (at least the gui).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721282

Title:
  upowerd/gnome-power-statistics crash; high CPU, memory consumption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1721282/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512322] Re: Problem upgrading IBM owned system to 15.10

[Vincent Gerris]

I got the same issue on an upgrade of 17.10 to 18.04 development release

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512322

Title:
  Problem upgrading IBM owned system to 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1512322/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1717536] Re: Synaptic does not start

[Vincent Gerris]

thanks for the workaround:

It's reported here too:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856469

It seems like a bug to me, the app should just start without any
terminal work.

** Bug watch added: Debian Bug tracker #856469
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856469

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717536

Title:
  Synaptic does not start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1717536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[Vincent Gerris]

@Silas 
Linux users are patient indeed and they are certainly not waiting for useless 
comments like yours.
If you want to contribute, educate yourself and try to help out. Ranting does 
contribute NOTHING.
So if you really love Linux, think about that.
Try to follow the rules regarding the bug report and contribute where you can 
and people will like it.

Nobody asked you to use Ubuntu, if you're happy with windows 10 (which probably 
nobody else here is) then use it and be happy, why post here?
Don't forget Linux is a community effort and the ways to fix certain problems 
is difficult.
However, making an effort to get it to work will teach you and will get you 
appreciation from others.

As bagl0312 commented already, your point is not even viable, because the issue 
was fixed in 17.04 by a patch.
If you google the issue for older versions, you will probably land on a page 
that describes how to fix that too:
https://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
 and see work arounds in this thread, so your comment is really just bad timing.

Please think twice before you post something and read the rules.
Thanks to the relentless efforts of the community, this is fixed and work is 
going on to get this in the main version(s).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,


This is what I get now when I try the dev package from:

https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-
daemon/3.24.2-0ubuntu0.1

sudo dpkg -i gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb 
[sudo] password for ubuntu: 
(Reading database ... 354908 files and directories currently installed.)
Preparing to unpack gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb ...
Unpacking gnome-settings-daemon (3.24.2-0ubuntu0.1) over (3.24.0-0ubuntu2) ...
dpkg: dependency problems prevent configuration of gnome-settings-daemon:
 gnome-settings-daemon depends on gnome-settings-daemon-schemas (= 
3.24.2-0ubuntu0.1); however:
  Version of gnome-settings-daemon-schemas on system is 3.24.0-0ubuntu2.

dpkg: error processing package gnome-settings-daemon (--install):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
 gnome-settings-daemon

so I downloaded that from:
https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-daemon-schemas/3.24.2-0ubuntu0.1
and installed it.

Then I rebooted but there is not difference in behaviour.

Note that I use Unity, not Gnome.

When I installed these packages:
http://people.canonical.com/~khfeng/lp1683445/
it worked.

Thank you all!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Vincent Gerris]

You can still add the vpn nameserver to /etc/resolv.conf . Epic blunder by
both systemd-resolv maintainer and Ubuntu packagers for stacking a broken
configuration together for at the 3rd release. Does anyone know how to
escalate this?

On May 4, 2017 19:04, "Winckler"  wrote:

> It's a really ugly workaround, but I'm using iptables to block
> connections to my ISP's DNS. I manually create and remove iptables rules
> using a script but at least this allows me to work remotely. I hope this
> get fix soon.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1624317
>
> Title:
>   systemd-resolved breaks VPN with split-horizon DNS
>
> Status in systemd:
>   New
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I use a VPN configured with network-manager-openconnect-gnome in which
>   a split-horizon DNS setup assigns different addresses to some names
>   inside the remote network than the addresses seen for those names from
>   outside the remote network.  However, systemd-resolved often decides
>   to ignore the VPN’s DNS servers and use the local network’s DNS
>   servers to resolve names (whether in the remote domain or not),
>   breaking the split-horizon DNS.
>
>   This related bug, reported by Lennart Poettering himself, was closed
> with the current Fedora release at the time reaching EOL:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1151544
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,

Glad that it helps :).
I am not sure if the interface actually doesn't work, because it might if the 
Optimus mode would switch to use the Nvidia card dedicatedly, but since that is 
not supported by the nouveau driver, it might not happen. Not sure what 
happened to the Bumblebee projects and the likes and if it would affect this.
As long as an existing interface that is selected will always work, it could be 
omitted indeed.

Greetings,
Vincent

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,

Thanks for your feedback. I had a chat with somebody with some experience and 
he suggested it should be fixed in userspace, here:
https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/power/gsd-backlight-linux.c

This is what he suggests (if the above is indeed what Ubuntu uses,
because it is meant for Fedora):

In the gsd_backlight_helper_get_best_backlight helper.
It only looks at the type of backlight and not at the connection between the 
backlight interface and the connector.
An  option is, if the gsd_backlight_helper_get_type (devices, "firmware")
and gsd_backlight_helper_get_type (devices, "platform") calls both
are unsuccessful, then instead of using gsd_backlight_helper_get_type which 
simply returns the first matching one of the found backlights of type raw, do 
the following:

Take $PATH as the variable to /sys/class/backlight/foo dir
and check the content of $PATH/../enabled, it has to be "enabled", that way you 
can find out which backlight interface is connected to an LVDS interface that 
actually has a connected LCD.

If no interface is found with:
`cat $PATH/../enabled` == "enabled" then as a fallback, still return the first 
found interface.

I tried to implement this, but just getting the development environment
setup to develop and test took me so much time that I haven't gotten to
it.

Perhaps the above is easy to implement for someone with the proper setup.
Please keep us informed, if I make progress I will post too (but that might 
take a while).
cheers

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Vincent Gerris]

indeed, this is COMPLETELY broken on 17.04. It seems systemd-resolved is
the only thing being used. My DNS resolving over anyconnect
(openconnect) does not work AT ALL anymore. I don't know which brilliant
mind decided to change things like that, knowing there are so many bugs
open.

any work arounds known are greatly appreciated (disabling systemd-
resolved did not help)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi Joseph,

Thank you for the quick response.
I tested this with the intel-drm-next kernel and the one you suggested and get 
the exact same behavior. It seems like a regression, because this was not 
needed on 16.04/16.10.

I marked it as confirmed and added the tag, thanks you.


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

So as a wokraround:

sudo vim /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

sudo update-grub

reboot

This option adds the dell_backlight:
ubuntu@ubuntu-Latitude-E6430:~$ ls /sys/class/backlight
dell_backlight  intel_backlight  nv_backlight

Note that sending events to the intel_backlight like so:
root@ubuntu-Latitude-E6430:~# echo 1000 > 
/sys/class/backlight/intel_backlight/brightness 
works too.

More info regarding backlight troubleshooting:
http://hansdegoede.livejournal.com/13889.html

I guess we need a kernel patch/quirk.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683445] [NEW] E6430 brightness control not working

[Vincent Gerris]

Public bug reported:

The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
Source Nouveau driver shows the brightness slider moving but does not
affect the brightness.

When using the kernel boot option acpi_backlight=vendor , the brightness
control works.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Apr 17 20:00:56 2017
HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
InstallationDate: Installed on 2017-04-10 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: Dell Inc. Latitude E6430
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0H3MT5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6430
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs