from:"Tuomas"

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492985/+files/lspci-vvnn.log

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

Title:
  amdgpu with mst WARNING and Kernel Oops on blanking/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions

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

[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492984/+files/version.log

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

Title:
  amdgpu with mst WARNING and Kernel Oops on blanking/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions

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

[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume

** Description changed:

  HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than 
non-HWE, mostly after resume from blanking or suspend.
  Kernel logs for most recent one attached.
  
- $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
- $ fgrep RIP /tmp/oops20210428.txt
- Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 
[amdgpu]
- Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 
[amdgpu]
- Apr 28 08:23:04 ub3ff kernel: RIP: 
0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu]
- Apr 28 08:23:04 ub3ff kernel: RIP: 0033:0x7fe6953a550b
- Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dc_link_add_remote_sink+0x65/0x110 
[amdgpu]
- Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b
- Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 
[amdgpu]
- Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b
- Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 
[amdgpu]
+ $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > oops20210428.txt
+ $ fgrep RIP oops20210428.txt | cut -c 31-
+ RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 [amdgpu]
+ RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 [amdgpu]
+ RIP: 0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu]
+ RIP: 0033:0x7fe6953a550b
+ RIP: 0010:dc_link_add_remote_sink+0x65/0x110 [amdgpu]
+ RIP: 0033:0x7fe6953a550b
+ RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu]
+ RIP: 0033:0x7fe6953a550b
+ RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 28 08:43:08 2021
  InstallationDate: Installed on 2020-04-10 (382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  amdgpu with mst WARNING and Kernel Oops on blanking/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions

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

[Bug 1926400] [NEW] amdgpu with mst WARNING and Kernel Oops on blanking/resume

Public bug reported:

HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than 
non-HWE, mostly after resume from blanking or suspend.
Kernel logs for most recent one attached.

$ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
$ fgrep RIP /tmp/oops20210428.txt
Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 
[amdgpu]
Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 
[amdgpu]
Apr 28 08:23:04 ub3ff kernel: RIP: 
0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu]
Apr 28 08:23:04 ub3ff kernel: RIP: 0033:0x7fe6953a550b
Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dc_link_add_remote_sink+0x65/0x110 
[amdgpu]
Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b
Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu]
Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b
Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu]

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 28 08:43:08 2021
InstallationDate: Installed on 2020-04-10 (382 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal kernel-oops

** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'"
   
https://bugs.launchpad.net/bugs/1926400/+attachment/5492972/+files/oops20210428.txt

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

Title:
  amdgpu with mst WARNING and Kernel Oops on blanking/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2021-02-10 Thread Tuomas

Few months ago I gave up and stopped using my TB18. Easier to connect
few cables once a day than fight with this. I'm much happier now. TB18
serves as an expensive laptop stand for me (elevates laptop 5 cm from
table).

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

2021-01-16 Thread Tuomas Suutari

Now that the new SOF firmware is included in the linux-firmware package
(see bug #1900809) the audio stack has been much more stable for me.
Unfortunately there has been still one audio stack crash after the
firmware upgrade, but it probably was another issue, since the dmesg
didn't contain similar "DSP panic" messages then.  If that new crash
happens again, I'll open a new bug.

However, I think this issue could be closed as fixed.

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

Title:
  Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

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

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

[Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6

2020-11-16 Thread Tuomas Suutari

This update would also fix at least bug #1881505.

Basically, my audio on Lenovo T14 was working very unreliably and jammed
with a DSP panic quite often with the 1.4.2 version, but seems to work
just fine with 1.6.

It would be great to get this update included soon, since it's very
inconvenient to reboot the laptop about 1-2 times a day, because that
seems to be the only way to get audio working after the DSP paic.

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

Title:
  [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6

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

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

[Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

2020-11-09 Thread Tuomas Suutari

It seems that the 1.6 version of the SOF firmware fixes the issue for
me. Haven't got any of those DSP panic messages anymore after the update
and before the update they occurred almost every day.

Is there anything I can do to help in making this fix to be included to
linux-firmware package?

Eugene: Have you tried if your issue is fixed by the newer firmware?

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

Title:
  Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

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

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

[Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

2020-11-05 Thread Tuomas Suutari

If this is indeed the same issue as in
https://github.com/thesofproject/sof/issues/2828, then the problem
should be fixed by upgrading the SOF firmware to 1.6 version.

I'll give it a try by installing directly from
https://github.com/thesofproject/sof-bin/tree/stable-v1.6

I will let you know if that fixed the issue. So far it looks good, but
I'll have to use the system for couple days to be sure.

If the newer firmware fixes the issue, is it possible to get it to the
linux-firmware package for Ubuntu 20.04?

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: github.com/thesofproject/sof/issues #2828
   https://github.com/thesofproject/sof/issues/2828

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

Title:
  Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

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

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

[Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7

2020-11-05 Thread Tuomas Suutari

I have the same problem with Lenovo T14 (Gen 1), which seems to have a
similar sound device:

00:1f.3 Audio device [0403]: Intel Corporation Device [8086:02c8] (prog-if 80)
Subsystem: Lenovo Device [17aa:22b1]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee00858  Data: 
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci

This is what I've got to my dmesg when the sound stopped working:

[127623.194131] sof-audio-pci :00:1f.3: error : DSP panic!
[127623.194155] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[127623.194394] sof-audio-pci :00:1f.3: error: can't enter idle
[127623.194398] sof-audio-pci :00:1f.3: error: trace point 4000
[127623.194402] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50
[127623.194409] sof-audio-pci :00:1f.3: error: DSP Firmware Oops
[127623.194427] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 
0x PS   0x00060925 SAR 0x
[127623.194431] sof-audio-pci :00:1f.3: EPC1 0x EPC2 
0xbe00d30e EPC3 0x EPC40x
[127623.194434] sof-audio-pci :00:1f.3: EPC5 0x EPC6 
0x EPC7 0x DEPC0x
[127623.194438] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 
0x EPS4 0x EPS50x
[127623.194440] sof-audio-pci :00:1f.3: EPS6 0x EPS7 
0x INTENABL 0x INTERRU 0x0222
[127623.194443] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0
[127623.194451] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 
be062380 
[127623.194454] sof-audio-pci :00:1f.3: 0xbe04f5b4:   
0032 
[127623.194457] sof-audio-pci :00:1f.3: 0xbe04f5b8: fb35de00 fc28026c 
7a64e018 952e
[127623.194461] sof-audio-pci :00:1f.3: 0xbe04f5bc: 0090be70 a4f2 
c0edc5f9 
[127623.194463] sof-audio-pci :00:1f.3: 0xbe04f5c0: a9716c98  
6ead97c0 952e
[127623.194467] sof-audio-pci :00:1f.3: 0xbe04f5c4:   
 
[127623.194471] sof-audio-pci :00:1f.3: 0xbe04f5c8: 002cbb98 a4f2 
0090bf48 a4f2
[127623.194475] sof-audio-pci :00:1f.3: 0xbe04f5cc:   
 
[127623.194478] sof-audio-pci :00:1f.3: error: waking up any trace sleepers
[127714.180370] sof-audio-pci :00:1f.3: error: ipc timed out for 0x6005 
size 12
[127714.180387] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[127714.180652] sof-audio-pci :00:1f.3: error: can't enter idle
[127714.180659] sof-audio-pci :00:1f.3: error: trace point 4000
[127714.180664] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50
[127714.180670] sof-audio-pci :00:1f.3: error: DSP Firmware Oops
[127714.180676] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 
0x PS   0x00060925 SAR 0x
[127714.180682] sof-audio-pci :00:1f.3: EPC1 0x EPC2 
0xbe00d30e EPC3 0x EPC40x
[127714.180687] sof-audio-pci :00:1f.3: EPC5 0x EPC6 
0x EPC7 0x DEPC0x
[127714.180692] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 
0x EPS4 0x EPS50x
[127714.180695] sof-audio-pci :00:1f.3: EPS6 0x EPS7 
0x INTENABL 0x INTERRU 0x0222
[127714.180698] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0
[127714.180705] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 
be062380 
[127714.180709] sof-audio-pci :00:1f.3: 0xbe04f5b4:   
0032 
[127714.180713] sof-audio-pci :00:1f.3: 0xbe04f5b8: d02a5b00 530f4b8a 
700a71f8 952e
[127714.180717] sof-audio-pci :00:1f.3: 0xbe04f5bc:  952e 
 530f4b8a
[127714.180720] sof-audio-pci :00:1f.3: 0xbe04f5c0: 000c  
700a7198 952e
[127714.180724] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6f156000 952e 
 
[127714.180728] sof-audio-pci :00:1f.3: 0xbe04f5c8: 000c 6005 
0009 952e
[127714.180732] sof-audio-pci :00:1f.3: 0xbe04f5cc:   
 
[127714.180749] sof-audio-pci :00:1f.3: error: hda irq intsts 0x 
intlctl 0xc085 rirb 00
[127714.180752] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x 
adspis 0x
[127714.180765] sof-audio-pci :00:1f.3: error: host status 0x dsp 
status 0x mask 0x0003
[127714.180768] sof-audio-pci :00:1f.3: error: waking up any trace sleepers
[127714.181386]  HDA Analog: ASoC: trigger FE cmd: 0 failed: -110

[Bug 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)

Actually
https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545
lists a fix (--hanging) for this being available since quantal.

** Tags removed: focal

** Changed in: apport (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  ubuntu-bug lacks an option for collection stack trace of running
  process (infinite loop analysis)

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

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

[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609

Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to 
errors.ubuntu.com now, marking these two as duplicates for now.

** This bug has been marked a duplicate of bug 1861609
   [focal] Xorg crashed with assertion failure (usually in a VM) at 
[privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and 
call stack comes from DRIMoveBuffersHelper

** Information type changed from Public to Private

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

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

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

[Bug 1891745] Re: Xorg crashed with SIGSEGV in dixSaveScreens()

*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609

Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to 
errors.ubuntu.com now, marking these two as duplicates for now.

** This bug has been marked a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings

** Information type changed from Public to Private

** This bug is no longer a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings
** This bug has been marked a duplicate of bug 1861609
   [focal] Xorg crashed with assertion failure (usually in a VM) at 
[privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and 
call stack comes from DRIMoveBuffersHelper

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

Title:
  Xorg crashed with SIGSEGV in dixSaveScreens()

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

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

[Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie
/whoopsie-id) claims "No errors have been reported from this system",
which is consistent with no ".uploaded" files appearing.

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

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

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

[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

** Tags added: regression-update

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

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

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

[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

No longer reproducible by visiting display settings after bug #1891745
crash. Possibly a duplicate of bug #1861609.

** Description changed:

- AssertionMessage Xort: ../../../../../../include/privates.h:121:
+ AssertionMessage Xorg: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.
  
  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
+  Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

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

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

[Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

** Description changed:

  [Impact]
  1. When trying to send a report manually, you can not
- 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even if .crash.upload exists (= upload not yet 
completed?)
- 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality (and does not tell the user that .crash is just a text file)
+ 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even when .crash.upload exists (upload not yet completed)
+ 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality
  
  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
  
  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional state
  = "routable" network that many ubuntu GUI tools refuse to work with
  anyway, is apport one of them?
  
  Similarly to bug #1825822 I attempted to
  
- $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
- "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
- into ".uploaded". And before the "Send" there does not appear to be any
- obvious way to copy the report as text somewhere.
+ $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after
+ clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not
+ change into ".uploaded". And before the "Send" the UI does not contain
+ any obvious way to copy the report as text somewhere (note: just copy
+ the .crash which is text format with base64 parts anyway, at least for
+ now).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

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

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

[Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

** Description changed:

  [Impact]
  1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not
+ 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even if .crash.upload exists (= upload not yet 
completed?)
+ 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality (and does not tell the user that .crash is just a text file)
  
  [Test Case]
  Start Ubuntu
  Open terminal
- $ ubuntu-bug /var/crash/.crash does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
+ $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
  
  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional state
  = "routable" network that many ubuntu GUI tools refuse to work with
  anyway, is apport one of them?
  
  Similarly to bug #1825822 I attempted to
  
  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
  "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
  into ".uploaded". And before the "Send" there does not appear to be any
  obvious way to copy the report as text somewhere.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

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

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

[Bug 1891745] [NEW] Xorg crashed with SIGSEGV in dixSaveScreens()

Public bug reported:

This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636

While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be related to kernel upgrades then, or
just happened to slip by undetected after earlier upgrades?

 [ 81555.574] (EE) Backtrace:
 [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x560d53a2ee0c]
 [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7fb62037b41f]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb524a0]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb52750]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bb00]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bba0]
 [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) [0x560d538fceb6]
 [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) 
[0x560d53a0e779]
 [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x560d5390b65d]
 [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) 
[0x560d538cdeb9]
 [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4]
 [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7fb6201990b3]
 [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e]
 [ 81555.581] (EE) 
 [ 81555.581] (EE) Segmentation fault at address 0x0
 [ 81555.581] (EE) 
 Fatal server error:
 [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting
 [ 81555.581] (EE) 
 [ 81555.581] (EE) 

P.S. Don't currently have a remote debugging setup since all the other
hosts nearby are headless.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 13:17:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (126 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Xorg crashed with SIGSEGV in dixSaveScreens()

To manage

[Bug 1891636] [NEW] After recent updates Xorg crashes whenever entering Display Settings

2020-08-14 Thread Tuomas Heino

Public bug reported:

AssertionMessage Xort: ../../../../../../include/privates.h:121:
dixGetPrivateAddr: Assertion `key-initialized' failed.

Also affected by apport bug #1891634 making filling more information
here somewhat tedious.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:08:34 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (125 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

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

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

[Bug 1891634] [NEW] $ ubuntu-bug /var/crash/.crash does not work

2020-08-14 Thread Tuomas Heino

Public bug reported:

[Impact]
1. When trying to send a report manually, you can not
2. When trying to copy-paste the stacktrace as text, you can not

[Test Case]
Start Ubuntu
Open terminal
$ ubuntu-bug /var/crash/.crash does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.

In multihomed host renderer: networkd in netplan with some of the
redundant bridge members lacking physical connectivity and/or offline
usb tether backup networks tend to result in perfectly functional state
= "routable" network that many ubuntu GUI tools refuse to work with
anyway, is apport one of them?

Similarly to bug #1825822 I attempted to

$ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
"Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
into ".uploaded". And before the "Send" there does not appear to be any
obvious way to copy the report as text somewhere.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27.6
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:28:31 2020
InstallationDate: Installed on 2020-04-10 (125 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

  [Impact]
  1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not 
+ 2. When trying to copy-paste the stacktrace as text, you can not
  
  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
  
  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional state
  = "routable" network that many ubuntu GUI tools refuse to work with
  anyway, is apport one of them?
  
- Similarly to bug#1825822 I attempted to
+ Similarly to bug #1825822 I attempted to
  
  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
  "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
  into ".uploaded". And before the "Send" there does not appear to be any
  obvious way to copy the report as text somewhere.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
-  664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
-  640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
+  664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
+  640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

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

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

[Bug 1873194] Re: clipit interface not working in 20.04

2020-04-27 Thread Tuomas

On Ubuntu 20.04 stable,
the Clipit interface does not work on Xorg either. The hotekeys do not work, 
the preferences do not open and the program does not shut down properly.

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

Title:
  clipit interface not working in 20.04

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

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

[Bug 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)

No such feature seen yet on Focal version of ubuntu-bug either.

** Tags added: focal

** Changed in: apport (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/986779

Title:
  ubuntu-bug lacks an option for collection stack trace of running
  process (infinite loop analysis)

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

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

[Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

Not reproducible on fresh install on same hardware.

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

Title:
  Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

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

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

[Bug 1872020] Re: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ; ; in postinst script?

** Patch added: "this patch let me dpkg --configure --pending successfully"
   
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+attachment/5351085/+files/grubpostinst.patch

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

Title:
  package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to
  install/upgrade: extra ;; in postinst script?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+subscriptions

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

[Bug 1872020] [NEW] package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ; ; in postinst script?

Public bug reported:

(auto)upgrade failed, not analyzed further for now.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.40+15+1533136590.3beb971-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or 
directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.11-0ubuntu25
AptOrdering:
 libwacom-bin:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
BootEFIContents:
 BOOTX64.CSV
 grub.cfg
 grubx64.efi
 mmx64.efi
 shimx64.efi
Date: Fri Apr 10 07:00:51 2020
DuplicateSignature:
 package:shim-signed:1.40+15+1533136590.3beb971-0ubuntu1
 Setting up grub-efi-amd64-signed (1.139+2.04-1ubuntu24) ...
 /var/lib/dpkg/info/grub-efi-amd64-signed.postinst: 23: Syntax error: word 
unexpected (expecting ")")
 dpkg: error processing package grub-efi-amd64-signed (--configure):
  installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 2
EFITables:
 huhti 09 04:46:02 ub3xx kernel: efi: EFI v2.31 by American Megatrends
 huhti 09 04:46:02 ub3xx kernel: efi:  ACPI=0xdf38f000  ACPI 2.0=0xdf38f000  
SMBIOS=0xdec24e98  MPS=0xfc9b0 
 huhti 09 04:46:02 ub3xx kernel: secureboot: Secure boot disabled
 huhti 09 04:46:02 ub3xx kernel: secureboot: Secure boot disabled
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-09-25 (1292 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.1ubuntu1
SourcePackage: shim-signed
Title: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to focal on 2020-04-09 (1 days ago)

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

** Summary changed:

- package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to 
install/upgrade: Assumes procfs to contain stuff that isn't there
+ package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to 
install/upgrade: extra ;; in postinst script?

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

Title:
  package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to
  install/upgrade: extra ;; in postinst script?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+subscriptions

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

[Bug 1871916] [NEW] Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

2020-04-09 Thread Tuomas Heino

Public bug reported:

Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect
x.org drivers for RX 5500 XT. Those drivers appear to be missing
features like multi-monitor support. On the other hand live-usb of 20.04
beta did manage to utilize all 3 connected monitors (before crashing),
so the issue may also be related to upgrading process (used do-release-
upgrade since update-managed does not scale down to 800x600 fallback
which 18.04 used with unsupported hardware).

Yes, this report is in need of some triaging, unless it happens to be a
clear duplicate of another bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  9 22:01:36 2020
DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.132, 5.3.0-46-generic, x86_64: installed
 nvidia, 390.132, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2016-09-25 (1292 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago)
XorgConf:
 Section "Device"
  Identifier "AMD"
  Driver "amdgpu"
 EndSection
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Thu Apr  9 04:46:16 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.7-2ubuntu2

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


** Tags: amd64 apport-bug focal performance ubuntu

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

Title:
  Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

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

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

[Bug 1853107] Re: Crash in starting

2019-11-19 Thread Tuomas Lähteenmäki

install python-six package.

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

Title:
  Crash in starting

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

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

[Bug 1853107] [NEW] Crash in starting

2019-11-19 Thread Tuomas Lähteenmäki

Public bug reported:

Program crash when starting.
Using Ubuntu 18.04 LTS, 5.0.0-36-generic

log is Traceback (most recent call last):
  File "/usr/bin/wammu", line 47, in 
import Wammu.Locales
  File "/usr/lib/python2.7/dist-packages/Wammu/Locales.py", line 31, in 
import six
ImportError: No module named six

** Affects: wammu (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/1853107

Title:
  Crash in starting

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

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

[Bug 1850203] [NEW] installing new os on a sdd 120gb kingston

2019-10-28 Thread Tuomas

Public bug reported:

im trying to install the most recent ubuntu on an kingston 120gb ssd
drive

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 28 22:07:41 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
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.12 ubuntu

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

Title:
  installing new os on a sdd 120gb kingston

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

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

[Bug 1769132] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

2019-10-08 Thread Tuomas Lähteenmäki

xenial version working fine.

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

Title:
  ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

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

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

[Bug 1769132] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

2019-07-31 Thread Tuomas Lähteenmäki

Fix not fix the problem in LTS version. I have installed 2.8.1-2ubuntu2
version and i have same problems. (Ubuntu 18.04)

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

Title:
  ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

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

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

[Bug 1666650] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich

2019-03-26 Thread Tuomas Heino

*** This bug is a duplicate of bug 1486316 ***
https://bugs.launchpad.net/bugs/1486316

** This bug has been marked a duplicate of bug 1486316
   lpc_ich: Resource conflict(s) found affecting gpio_ich

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

Title:
  lpc_ich: Resource conflict(s) found affecting gpio_ich

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

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

[Bug 1486316] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich

2019-03-26 Thread Tuomas Heino

** Tags added: bionic

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

Title:
  lpc_ich: Resource conflict(s) found affecting gpio_ich

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

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-03-08 Thread Tuomas

I updated BIOS by saving exe file to usb stick and used bios update option from 
BIOS boot menu.
For TB18DC firmware upgrade, I installed Windows 10. Actually firmware upgrade 
did not go too smoothly (it upgraded successfully some subsystems, but not all, 
failed with MTS1, MTS2). 

Here are some bios settings that might be related:

Thunderbolt Adapter configuration:
 - Thunderbolt: Yes
 - Enable thunderbolt ... modules: no
 - Enable thunderbolt boot support: no
 - No security: yes

- Always allow dell docks: yes
- Enable USB Boot support: Yes
- Enable external usb port: yes
- Enable usb powershare: no
- Thunderbolt Auto switch: no
- Bios Assist enumeration: yes

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-03-07 Thread Tuomas

And now the rest of issues seem to have been gone away when I also
updated my TB18DC to the latest firmware (1.0.8).

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-03-04 Thread Tuomas

It seems that this problem with TB18DC has gone away for me after
updating my Dell Precision 7530 bios to the latest 1.6.0 version.

There's still another USB problem with dock but symptoms are different
than earlier: for example usb mouse stops working after some time, but
still after that is visible for the system (lsusb)). Network and sound
from dock work now well. I would try updating dock bios, if I just could
install windows.

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-01-16 Thread Tuomas

Updated kernel to 4.19.15-041915-generic (ukuu), and still this
reproduces.

Right after boot it works fine, then after one working day I disconnect 
thunderbolt
and suspend the machine. Then next morning it reproduces within first hour.

With the current setup I don't have any usb devices connected to the
dock (TB18DC), only integrated devices (ethernet and audio) and DP ports
are in use.

Dmesg looks about the same as earlier.

[30714.740801] xhci_hcd :3f:00.0: ERROR unknown event type 15
[30719.651705] xhci_hcd :3f:00.0: xHCI host not responding to stop endpoint 
command.
[30719.652032] xhci_hcd :3f:00.0: xHCI host controller not responding, 
assume dead
[30719.652070] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108
[30719.652074] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108
[30719.652079] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108
[30719.652082] r8152 4-1.2:1.0 enxe4b97a92fb26: Tx status -108
[30719.652099] xhci_hcd :3f:00.0: HC died; cleaning up
[30719.652127] usb 4-1.1: Failed to suspend device, error -19

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-11-29 Thread Tuomas

Okay, after yet another occurrence of the issue:

lspci -vv
00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (prog-if 00 
[VGA controller])
Subsystem: Dell Device 0831
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 07)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core 
Processor Gaussian Mixture Model
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:14.0 USB controller: Intel Corporation Device a36d (rev 10) (prog-if 30 
[XHCI])
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

00:14.2 RAM memory: Intel Corporation Device a36f (rev 10)
Subsystem: Dell Device 0831
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller: Intel Corporation Device a360 (rev 10)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) (prog-if 01 
[AHCI 1.0])
Subsystem: Dell Device 0831
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-11-29 Thread Tuomas

No, for me lspci works fine after this issue:

00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10)
00:14.0 USB controller: Intel Corporation Device a36d (rev 10)
00:14.2 RAM memory: Intel Corporation Device a36f (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
00:16.0 Communication controller: Intel Corporation Device a360 (rev 10)
00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device a33d (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Device a348 (rev 10)
00:1f.4 SMBus: Intel Corporation Device a323 (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM 
(rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1cba (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio 
Controller (rev ff)
02:00.0 Non-Volatile memory controller: Device 1c5c:1504
03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 
4C 2018] (rev 06)
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 
4C 2018] (rev 06)
04:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 
4C 2018] (rev 06)
04:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 
4C 2018] (rev 06)
04:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 
4C 2018] (rev 06)
05:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan 
Ridge 4C 2018] (rev 06)
3a:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3b:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3b:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3d:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3e:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3e:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
3f:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 
(rev 01)
6f:00.0 Network controller: Intel Corporation Device 2526 (rev 29)

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-11-27 Thread Tuomas

This is now happening to me about every 10-20 minutes or so. Very
frustrating.

With TB18DC I'm using

 - onboard sound port
 - onboard ethernet port
 - mouse dongle 
 - fingerprint reader
 - 1 large external monitor with DP
 
After reboot this tends to happen after longer period of time (several hours), 
but
once it happens, it repeats itself pretty soon.

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-11-23 Thread Tuomas

I have the same issue with Dell TB18DC tb dock and Dell Precision 7530
laptop. Using ukuu mainline kernel 4.19.4-041904-generic. I think latest
system bios update 1.4.2 (https://www.dell.com/support/home/us/en/04
/product-support/product/precision-15-7530-laptop/drivers) made this
problem appear a lot more often than earlier.

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

Title:
  USB over thunderbolt turns off every once in a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions

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

[Bug 1798941] [NEW] back button does nothing

2018-10-20 Thread Tuomas Jaakola

Public bug reported:

Steps:
1. Open Ubuntu Software
2. Search for "Dropbox"
3. Install it
4. Launch it
5. Click back button < in the top left corner.
   Expecting it navigates back to search or main view, but nothing happens.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-software 3.30.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 20 11:00:16 2018
InstallationDate: Installed on 2018-10-19 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.30.2-0ubuntu7
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  back button does nothing

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

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

[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

2018-10-19 Thread Tuomas Jaakola

Now I have Ubuntu 18.10 installed.

Workaround is to use a working grub2 (for example booting up with Ubuntu
18.04 installation media) and move to grub command line. There I created
a new menuentry for loading Ubuntu 18.10 installer from another USB
stick.

https://askubuntu.com/questions/436519/boot-efi-files-from-grub2

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

Title:
  System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

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

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

[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

2018-10-19 Thread Tuomas Jaakola

Even though Ubuntu 18.04 installation USB stick works fine, I see same
kind of mmx64.efi error flashing quickly. However it does not halt there
unlike in Ubuntu 18.10 installation media.

The error I see when booting up with Ubuntu 18.04 installation media:

Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi: Not Found
Failed to start MokManager: Not Found
error: file `/boot' not found.

After this error it loads grub nicely and starts Ubuntu 18.04
installation.

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

Title:
  System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

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

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

[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

2018-10-19 Thread Tuomas Jaakola

However, using the same usb-creator-gtk (version 0.3.5) in Ubuntu 18.04,
I created an installation USB stick from Ubuntu 18.04. That works
without any problem in MSI laptop. There is no /EFI/BOOT/mmx64.efi file
either in that USB stick, but it works anyway.

The result is that I am not able to install Ubuntu 18.10 at all.

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

Title:
  System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

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

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

[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

2018-10-18 Thread Tuomas Jaakola

I was about to install Ubuntu 18.10 into laptop (MSI GT62VR 7RE
Dominator Pro) using USB installation media. It was able to boot up and
start installation until the installation halted with a black screen.
After I rebooted I got the same error about missing mmx64.efi.

Windows 10 boots up fine without Ubuntu installation USB stick, but when
I try to boot up using the stick, it fails every time giving me the same
error. So I can't even start installation or use a command line from USB
stick anymore. In /EFI/BOOT/ there are only BOOTx64.EFI and grubx64.efi
files, mmx64.efi file is missing there (should it be there?).

The installation USB stick is created in another machine, using Startup
Disk Creator from Ubuntu 18.04.

Thank you for fixing grub2! How can I use patched grub2 and create a new
Ubuntu installation USB stick which would work? Or what should I do?

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

Title:
  System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

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

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

[Bug 520546] Re: Alt-f2 switches to virtual terminal 2

2018-09-13 Thread Tuomas Suutari

I can reproduce the bug in Ubuntu 18.04.1 by re-configuring keyboard-
configuration package (version 1.178ubuntu2.7) with DISPLAY being
unset/empty, e.g.:

tuomas@matta:~ 0 $ sudo DISPLAY= DEBIAN_FRONTEND=noninteractive \
   dpkg-reconfigure keyboard-configuration
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic

And after running this Alt+F2 switches to VT2 even from X11.  When
switching back to X11 (with Alt+F1), it appears that the Alt+F2 also
goes to X11, since the krunner popup opens (bound to Alt+F2).

Running "sudo kbd_mode -s" in a terminal window within X11 makes the
Alt+Fx keys act normally again.

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

Title:
  Alt-f2 switches to virtual terminal 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions

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

[Bug 1783859] Re: Alt-Key handling changed after update

2018-09-13 Thread Tuomas Suutari

*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

** This bug has been marked a duplicate of bug 520546
   Alt-f2 switches to virtual terminal 2

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

Title:
  Alt-Key handling changed after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1783859/+subscriptions

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

[Bug 1783859] Re: Alt-Key handling changed after update

2018-09-13 Thread Tuomas Suutari

I think this is a duplicate of #520546.

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

Title:
  Alt-Key handling changed after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1783859/+subscriptions

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

[Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

2018-08-28 Thread Fredrik Tuomas

Thank you for your work. I will test.

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661629/+subscriptions

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

[Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy

2018-07-24 Thread Tuomas Heino

@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet
witnessed it working though, even on hardware that had dozen
reports/year shown with mcelog.

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

Title:
  Missing mcelog userspace package in bionic - or maybe linux kernel
  config should disable mcelog_legacy

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

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

[Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2018-06-27 Thread Tuomas Lähteenmäki

Same happened also me. Updating system and intel-microcode is installed in AMD 
machine. 
Updating intel laptop and also AMD-microcode is installed in intel-laptop. Is 
there no amendment here? What processor is used.

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

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

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

[Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2018-06-27 Thread Tuomas Lähteenmäki

im updating latest intel-microcode (sudo apt-get update && sudo apt-get
upgrade -y) and it is also automatically install also amd-microcode in
my laptop. Why? my laptop not use amd-microcode. it is use only intel.
Why it install it when updating my laptop. Is this a bug or what?

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

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

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

[Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable

2018-06-20 Thread Tuomas Lähteenmäki

I have similar big problem with kernel and latest nvidia drivers but i
do not secure boot in my machine. When Ubuntu install new kernel and
boot. nvidia drivers not loaded in kernel. And system crashing.

Error! Could not locate dkms.conf file.
File:  does not exist.

using nvidia 390 drivers.

lspci | grep NVIDIA
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 770] 
(rev a1)

modprobe nvidia
modprobe: ERROR: could not insert 'nvidia_390': Operation not permitted

apt list dkms -a
Listing... ok
dkms/xenial-updates,xenial-updates,now 2.2.0.3-2ubuntu11.5 all [installed]
dkms/xenial,xenial 2.2.0.3-2ubuntu11 all

ls -la dkms.conf
-rw-r--r-- 1 root root 1197 kesä  19 18:17 dkms.conf


 lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename:   xenial

uname -a
Linux valvoja-System-Product-Name 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 
14:15:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Regression: Kernel Update in 16.04 from last days renders nvidia
  driver unusable

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

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

[Bug 1773004] Re: qemu-system-x86_64 segfaults during guest kernel boot

2018-06-03 Thread Tuomas Heino

1. appears to depend on snapshot, given cloud images handle the LUNs fine as 
additional disks
2. debug symbols part may need more effort than I can spend on this

Also appears to require the following PEBCAK configuration snippet, but
that alone was not enough to reproduce the crash with stock cloud
images:

--- vmdef_crashes.xml
+++ vmdef_works_ok.xml
@@ -67,7 +67,7 @@
 
   
 
-
+
   
 
 

Apparently some cleanup had already removed the earlier /var/crash
contents after May 23rd but since I can both reproduce and workaround
this, might attempt reproducing this once I have debugging symbols set
up. Whether OVMF is a requirement is unknown for now, but the crashing
snapshot does use UEFI.

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

Title:
  qemu-system-x86_64 segfaults during guest kernel boot

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

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

[Bug 1773004] Re: qemu-system-x86_64 segfaults during guest kernel boot

2018-05-23 Thread Tuomas Heino

** Attachment added: "i440fx vm definition (same result with q35 too)"
   
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+attachment/5143449/+files/ovmf_v02c.xml

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

Title:
  qemu-system-x86_64 segfaults during guest kernel boot

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

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

[Bug 1773004] [NEW] qemu-system-x86_64 segfaults during guest kernel boot

2018-05-23 Thread Tuomas Heino

Public bug reported:

Attempting to boot old 14.04 LTS snapshot in a VM with LUN passthrough
results in segfaults.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 22:12:54 2018
InstallationDate: Installed on 2018-05-20 (3 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
MachineType: LENOVO ThinkServer TS140
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=88166613-97a3-4912-884e-46bc05b70a85 ro
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKT99AUS
dmi.board.name: ThinkServer TS140
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 7
dmi.chassis.vendor: LENOVO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000PEU:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: ThinkServer TS140
dmi.product.version: 70A4000PEU
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

** Attachment added: "guest kernel serial console output"
   
https://bugs.launchpad.net/bugs/1773004/+attachment/5143433/+files/ovmf2.ttyS1.out

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

Title:
  qemu-system-x86_64 segfaults during guest kernel boot

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

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

[Bug 1759542] [NEW] package libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/cha

2018-03-28 Thread Tuomas Jaakola

Public bug reported:

apt dist-upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libgtk2.0-0 2.24.31-2ubuntu1 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 libgtk2.0-0:i386: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Mar 28 13:47:06 2018
DpkgTerminalLog:
 Preparing to unpack .../libgtk2.0-0_2.24.31-2ubuntu1_i386.deb ...
 Unpacking libgtk2.0-0:i386 (2.24.31-2ubuntu1) over (2.24.31-1ubuntu1.1) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libgtk2.0-0_2.24.31-2ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgtk2.0-0:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other 
instances of package libgtk2.0-0:i386
InstallationDate: Installed on 2017-10-19 (159 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: gtk+2.0
Title: package libgtk2.0-0 2.24.31-2ubuntu1 [modified: 
usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgtk2.0-0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libgtk2.0-0 2.24.31-2ubuntu1 [modified:
  usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different
  from other instances of package libgtk2.0-0:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1759542/+subscriptions

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

[Bug 1313446] Re: window disappears on toggle shade

2018-02-20 Thread Tuomas Heino

As this bug most likely won't ever get fixed (since Unity7 development
was scrapped), it might be useful to document the known workarounds
here, starting with:

1: Start any window manager with working shade support, for example as follows:
$ nohup openbox --replace >/dev/null &
# Warning: If you are not familiar with openbox and alike, their default 
settings are rather minimalistic; no taskbars or app menus included after the 
replace above (see https://help.ubuntu.com/community/Openbox for more details).

2: Disable any references to shading if you want/need to use Unity
$ gsettings list-recursively org.gnome.desktop.wm.keybindings | grep -i shade
$ gsettings list-recursively org.gnome.desktop.wm.preferences | grep -i shade
$ # ... followed by some form of gsettings set or reset to the ones listed (not 
tested)

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

Title:
  window disappears on toggle shade

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

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

[Bug 1735493] [NEW] Please update to 1.16.0 for bionic

2017-11-30 Thread Tuomas Jormola

Public bug reported:

It would be nice to have the latest upstream branch in the next Ubuntu
LTS.

** Affects: sssd (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/1735493

Title:
  Please update to 1.16.0 for bionic

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

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

[Bug 1712772] [NEW] installing Lubuntu and installation crashes..

2017-08-24 Thread Tuomas Pihlajaniemi

Public bug reported:

I have lubuntu on dvd from www.lubuntu.net i can run it from dvd but i
cannot install it for some reason.. i also cannot format my hdd which
contain win 8.01 and its completely stuck..

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CasperVersion: 1.380
Date: Thu Aug 24 08:48:16 2017
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fi 
keyboard-configuration/layoutcode?=fi
LiveMediaBuild: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
ProcEnviron:
 LANGUAGE=fi_FI.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 lubuntu ubiquity-17.04.9 zesty

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

Title:
  installing Lubuntu and installation crashes..

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

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

[Bug 1676423] Re: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1

2017-03-27 Thread Tuomas Lähteenmäki

upgrading packages and get this error. sudo apt upgrade -f I did it and
the upgrade seemed to go ok.

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade:
  aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1

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

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

[Bug 1675784] Re: Blurr text and images in screen when using 379.39 driver

** Description changed:

I get again blurring text and my windows screen again. When using
updated 379.39 driver in Ubuntu 16.04 LTS.

Driver quality is really bad in recent times. I have suffered with this
problem for a very long time. At times, it disappears for some reason,
but always come back. Using Nvdia GTX 770. When, for example, the mouse
selects the text box so the text will be improved. But after a while it
shimmers out.

Screenshot of my desktop
https://mega.nz/#!AxxygBIK!79bbekT7yaLsoxIYtNV_wfAPsjj4F32ra5qbeVkY4gk
Hardinfo report:
https://mega.nz/#!cpg3VAjI!tpA4CY0HHj47AOuY3z-vrVRkJju5VxU4aY6l8TT6l9w
Nvidia log (bug-report) files:
https://mega.nz/#!8ohkzLBC!-qwXBZivmTxs-29oiXvawvocmDQgJZsqSzhN8LGgNWE
+
+
+ I have made a small statistic. Where's the version problem comes up all the
time. Blurr versios are 375.39, 367.10, 349.12, 346.47 and 346.35

** Description changed:

I get again blurring text and my windows screen again. When using
updated 379.39 driver in Ubuntu 16.04 LTS.

+ I have made a small statistic. Where's the version problem comes up all
+ the time. Blurr versios are 375.39, 367.10, 349.12, 346.47 and 346.35

- I have made a small statistic. Where's the version problem comes up all the
time. Blurr versios are 375.39, 367.10, 349.12, 346.47 and 346.35
+
+ When using 375.26 version. It is working great but not found any ppa.

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

Title:
Blurr text and images in screen when using 379.39 driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1675784/+subscriptions

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

[Bug 1675784] [NEW] Blurr text and images in screen when using 379.39 driver

Public bug reported:

I get again blurring text and my windows screen again. When using
updated 379.39 driver in Ubuntu 16.04 LTS.

I have made a small statistic. Where's the version problem comes up all the
time. Blurr versios are 375.39, 367.10, 349.12, 346.47 and 346.35

** Affects: nvidia-graphics-drivers-375 (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "screenshot desktop"

https://bugs.launchpad.net/bugs/1675784/+attachment/4844470/+files/desktop.png

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

Title:
Blurr text and images in screen when using 379.39 driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1675784/+subscriptions

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

[Bug 1675784] Re: Blurr text and images in screen when using 379.39 driver

in 379.26 version working with no problems. But it not found a ppa.

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

Title:
  Blurr text and images in screen when using 379.39 driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1675784/+subscriptions

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

[Bug 1675784] Re: Blurr text and images in screen when using 379.39 driver