[Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2024-10-05 Thread Sami Pietila
The problem looks like to be that printers re-renerate/update
certificates frequently even if they haven't expired. CUPS notices that
the certificate has changed and refuses to print. This happens with ipps
protocol, which is default. Here are instructions to use ipp protocol,
which does not check certificates.


https://github.com/OpenPrinting/cups/issues/1072

** Bug watch added: github.com/OpenPrinting/cups/issues #1072
   https://github.com/OpenPrinting/cups/issues/1072

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

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


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

[Bug 1970921] Re: Drag and drop does not work

2022-06-01 Thread Sami Pietila
This issue has now been reported to upstream:

https://gitlab.gnome.org/GNOME/nautilus/-/issues/2277

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2277
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/2277

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

Title:
  Drag and drop does not work

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


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

[Bug 1970921] Re: Drag and drop does not work

2022-06-01 Thread Sami Pietila
> Do you use gpaste?

I don't have gpaste package(s) installed.

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

Title:
  Drag and drop does not work

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


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

[Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-05-15 Thread Sami Pietila
** Attachment added: "Error message when trying to print."
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+attachment/5589824/+files/Screenshot%20from%202022-05-15%2015-34-20.png

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

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


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

[Bug 1973441] [NEW] Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-05-15 Thread Sami Pietila
Public bug reported:

After upgrading to 22.04 printing did not work. There is cups-pki-
invalid error and printer goes to paused state.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
Uname: Linux 5.17.7-051707-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
CurrentDesktop: ubuntu:GNOME
Date: Sun May 15 15:34:47 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-10-12 (214 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
dmi.bios.date: 03/29/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513QY.318
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513QY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.81
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513QY_G513QY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

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


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

[Bug 1970921] [NEW] Drag and drop does not work

2022-04-29 Thread Sami Pietila
Public bug reported:

After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to
web browser (chromium, google chrome / apps like seafile, etc.) do not
work. Also drag & drop from nautilus to slack desktop app does not work.
If making several attempts, it might suddenly work with nth attempt.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 29 13:32:48 2022
InstallationDate: Installed on 2016-11-22 (1983 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)
usr_lib_nautilus:
 evince42.1-3
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


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

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

Title:
  Drag and drop does not work

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


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

[Bug 1962451] [NEW] Libreoffice does not open remote files (over SSH with nautilus)

2022-02-28 Thread Sami Pietila
Public bug reported:

With Ubuntu 21.04 LTS I can browse (gnome-files) remote files with SSH
and clicking excel-table files will open the tables to Libreoffice. This
does not work under Ubuntu 21.10 anymore. Libreoffice banner shows
shortly and then nothing happens.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: libreoffice (not installed)
Uname: Linux 5.16.9-051609-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 28 11:14:23 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-10-12 (138 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Libreoffice does not open remote files (over SSH with nautilus)

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


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

[Bug 1954709] Re: Desktop freezes

2021-12-14 Thread Sami Pietila
I also see these kind of messages right after a restart:

[   15.809037] [drm] free PSP TMR buffer
[   16.121709] [drm] PCIE GART of 512M enabled (table at 0x0080).
[   16.121729] [drm] PSP is resuming...
[   16.153821] [drm] reserve 0xa0 from 0x82fe00 for PSP TMR
[   16.253273] amdgpu :03:00.0: amdgpu: RAS: optional ras ta ucode is not 
available
[   16.268898] amdgpu :03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta 
ucode is not available
[   16.268902] amdgpu :03:00.0: amdgpu: SMU is resuming...
[   19.519967] audit: type=1326 audit(1639494466.472:89): auid=1000 uid=1000 
gid=1000 ses=2 subj=snap.snap-store.ubuntu-software pid=1816 
comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 
arch=c03e syscall=93 compat=0 ip=0x7fd422bc74fb code=0x5
[   20.963115] amdgpu :03:00.0: amdgpu: Failed to setup smc hw!
[   20.963121] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of 
IP block  failed -62
[   20.963191] amdgpu :03:00.0: amdgpu: amdgpu_device_ip_resume failed 
(-62).

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

Title:
  Desktop freezes

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


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

[Bug 1954709] [NEW] Desktop freezes

2021-12-13 Thread Sami Pietila
Public bug reported:

Dmesg is showing error like:

[38788.569852] traps: chrome[67234] trap invalid opcode ip:563f6e3411cf 
sp:7ffc8aa52b50 error:0 in chrome[563f69764000+8936000]
[39342.613678] BUG: kernel NULL pointer dereference, address: 00c8
[39342.613682] #PF: supervisor read access in kernel mode
[39342.613684] #PF: error_code(0x) - not-present page
[39342.613685] PGD 0 P4D 0 
[39342.613686] Oops:  [#1] SMP NOPTI
[39342.613688] CPU: 6 PID: 3578 Comm: codium Tainted: GW 
5.13.0-22-generic #22-Ubuntu
[39342.613690] Hardware name: ASUSTeK COMPUTER INC. ROG Strix 
G513QY_G513QY/G513QY, BIOS G513QY.316 11/29/2021
[39342.613691] RIP: 0010:iommu_get_dma_domain+0xd/0x20
[39342.613695] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 
ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 
c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44


and 

[39342.614166] CR2: 00c8
[39342.614167] ---[ end trace 09dc7239d253ac8b ]---
[39342.777369] RIP: 0010:iommu_get_dma_domain+0xd/0x20
[39342.777389] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 
ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 
c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44
[39342.777392] RSP: 0018:a3e380eb7930 EFLAGS: 00010282
[39342.777396] RAX:  RBX:  RCX: 
[39342.777397] RDX: 1000 RSI: fe3fd000 RDI: 9707816070c8
[39342.777398] RBP: a3e380eb7970 R08:  R09: edd704c3f340
[39342.777399] R10: a3e380eb7b50 R11:  R12: 9707816070c8
[39342.777400] R13: 1000 R14: fe3fd000 R15: 9707816070c8
[39342.777402] FS:  () GS:970a8e78() 
knlGS:
[39342.777403] CS:  0010 DS:  ES:  CR0: 80050033
[39342.777404] CR2: 00c8 CR3: 00018140e000 CR4: 00750ee0
[39342.777406] PKRU: 5554
[39342.777409] Fixing recursive fault but reboot is needed!

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-22-generic 5.13.0-22.22
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  sami   1227 F pulseaudio
 /dev/snd/controlC1:  sami   1227 F pulseaudio
CasperMD5CheckResult: pass
Date: Mon Dec 13 23:07:26 2021
InstallationDate: Installed on 2021-10-12 (62 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-22-generic N/A
 linux-backports-modules-5.13.0-22-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513QY.316
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513QY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.73
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.316:bd11/29/2021:br5.19:efr0.73:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513QY_G513QY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug impish

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

Title:
  Desktop freezes

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


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

[Bug 1953681] [NEW] USB-devices do not work properly

2021-12-08 Thread Sami Pietila
Public bug reported:

I have Ubuntu 21.10. I have noticed that USB-ports do not work properly.
On multiple machines for example wireless mouse might not work after a
reboot and I need to unplug and plug the dongle to get it working.

Then when there are multiple USB-devices connected to the computer, the
USB-port might die and only reboot helps. In that case kernel dmesg
shows messages like these:

la joulu  4 13:53:44 2021] xhci_hcd :0f:00.3: Abort failed to stop command 
ring: -110
[la joulu  4 13:53:44 2021] xhci_hcd :0f:00.3: xHCI host controller not 
responding, assume dead
[la joulu  4 13:53:44 2021] xhci_hcd :0f:00.3: HC died; cleaning up
[la joulu  4 13:53:44 2021] xhci_hcd :0f:00.3: Timeout while waiting for 
setup device command
[la joulu  4 13:53:44 2021] xhci_hcd :0f:00.3: Error while assigning device 
slot ID

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-22-generic 5.13.0-22.22
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  8 22:16:39 2021
InstallationDate: Installed on 2021-11-06 (32 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=UUID=759510b9-f553-40ec-9dd2-f102ea364d20 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-22-generic N/A
 linux-backports-modules-5.13.0-22-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 08/09/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4021
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X570-E GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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

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


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

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

Title:
  USB-devices do not work properly

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


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

[Bug 1953611] Re: Wlan is not detected sometimes

2021-12-08 Thread Sami Pietila
** Attachment added: "lspci when the wlan device is not found by ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546244/+files/pci-devices.txt

** Summary changed:

- Wlan is not detected sometimes
+ Wlan is not detected

** Description changed:

- Ubuntu does not always find the wlan device.
+ Ubuntu does not always find the wlan device. A reboot might sometimes
+ remedy the situation.
  
  ip a does not show any wlan devices, but lspci does show the device.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
-  default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600 
-  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
-  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 
600 
-  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+  default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
+  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Wlan is not detected

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


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

[Bug 1953611] Re: Wlan is not detected sometimes

2021-12-08 Thread Sami Pietila
** Attachment added: ""ip a" when the wlan device is not found"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546243/+files/ipa.txt

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

Title:
  Wlan is not detected

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


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

[Bug 1953611] [NEW] Wlan is not detected

2021-12-08 Thread Sami Pietila
Public bug reported:

Ubuntu does not always find the wlan device. A reboot might sometimes
remedy the situation.

ip a does not show any wlan devices, but lspci does show the device.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: network-manager 1.32.12-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  8 13:40:43 2021
InstallationDate: Installed on 2021-11-06 (32 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Wlan is not detected

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


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

[Bug 1953611] Re: Wlan is not detected sometimes

2021-12-08 Thread Sami Pietila
Dmesg when wlan is not found.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546242/+files/dmesg.txt

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

Title:
  Wlan is not detected

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


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

[Bug 1947162] Re: Bluetooth does not work on ASUS ROG Strix G15 Advantage Edition G513 laptop on Ubuntu 21.10

2021-10-15 Thread Sami Pietila
There are also some other issues with 21.10 and the laptop hardware
1) Closing lid does not often put the laptop into proper sleep state (led strip 
stays on), but screen goes blank and does not resume when lid is opened. A 
reboot is needed to recover from this.
2) When downloading large files from the network (using wlan and also wired 
link) it blocks other network connectivity. For example, no new web pages can 
be loaded with internet browsers.

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

Title:
  Bluetooth does not work on  ASUS ROG Strix G15 Advantage Edition G513
  laptop on Ubuntu 21.10

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


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

[Bug 1947162] [NEW] Bluetooth does not work on ASUS ROG Strix G15 Advantage Edition G513 laptop on Ubuntu 21.10

2021-10-14 Thread Sami Pietila
Public bug reported:

Bluetooth does not work on  ASUS ROG Strix G15 Advantage Edition G513
laptop on Ubuntu 21.10.

Bluetooth is visible on the settings menu, but turning Bluetooth on does
work. It still shows as "Bluetooth Off".

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  sami   1862 F pulseaudio
 /dev/snd/controlC1:  sami   1862 F pulseaudio
 /dev/snd/controlC0:  sami   1862 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 14 16:43:43 2021
InstallationDate: Installed on 2021-10-12 (1 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-19-generic N/A
 linux-backports-modules-5.13.0-19-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513QY.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513QY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.68
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.306:bd05/07/2021:br5.19:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513QY_G513QY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  Bluetooth does not work on  ASUS ROG Strix G15 Advantage Edition G513
  laptop on Ubuntu 21.10

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


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

[Bug 1886653] Re: cups-pki-expired

2021-09-19 Thread Sami Pietila
I think the solution should be something that does not require editing
files under /etc.

Perhaps printing should prompt a question if the document should be
printed in case the printer certificate has expired.

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

Title:
  cups-pki-expired

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


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

[Bug 1933306] [NEW] Access to the notebook is denied

2021-06-23 Thread Sami Pietila
Public bug reported:

When starting jupyter-notebook (with "jupyter-notebook" command),
Chromium browser opens and displays a message:

"Access to the file was deniedThe file at 
file:///home/sami/.local/share/jupyter/runtime/nbserver-370045-open.html is not 
readable. It may have been removed, moved, or file permissions may be 
preventing access.
ERR_ACCESS_DENIED"

I am not sure, but I think this stopped working when Chromium was
changed to Snap-based.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: jupyter-notebook 6.2.0-1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 23 10:06:36 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-06-07 (380 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: jupyter-notebook
UpgradeStatus: Upgraded to hirsute on 2021-04-17 (66 days ago)

** Affects: jupyter-notebook (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  Access to the notebook is denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jupyter-notebook/+bug/1933306/+subscriptions

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

[Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

2021-03-07 Thread Sami Pietila
Lately I have been using the controller with a wireless adapter (not
bluetooth). This driver (https://github.com/medusalix/xow) seems to work
well. It would be nice if Ubuntu would ship this driver by default. Now
it must be manually installed from github.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

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

[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

2021-01-19 Thread Sami Pietila
Yes, it would be good to have an informative error message indicating
ssh has failed and that the host key needs to be added to
/root/.ssh/known_hosts.

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

2020-12-12 Thread Sami Pietila
This is the upstream issue:

https://github.com/systemd/systemd/issues/17545

** Bug watch added: github.com/systemd/systemd/issues #17545
   https://github.com/systemd/systemd/issues/17545

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

2020-11-11 Thread Sami Pietila
This was inspected at systemd github incident-pages. Automount (executed
as root) requires the target machine to be in /root/.ssh/known_hosts
file. Unfortunately, the failing mount does not seem to give any helpful
log or error messages.

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

2020-11-11 Thread Sami Pietila
This was inspected at systemd github incident-pages. Automount (executed
at root) requires the target machine to be in /root/.ssh/known_hosts
file. Unfortunately, the failing mount does not seem to give any helpful
log or error messages.

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1897396] Re: Unable to make chromium-chromedriver work with selenium

2020-11-07 Thread Sami Pietila
I did just use:
driver = webdriver.Chrome()

However, I just tried the same code again and could not reproduce the
crash. Now, it seems to work.

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

Title:
  Unable to make chromium-chromedriver work with selenium

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

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

[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

2020-11-04 Thread Sami Pietila
** Description changed:

- I have asked question in askubuntu about "Too many levels of symbolic
+ I have asked question at askubuntu about "Too many levels of symbolic
  links” error when trying to use systemd to mount sshfs
  (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
  links-error-when-using-systemd)
  
  I have not got any responses, so I am submitting a bug report. If this
  is not a bug, please advice how to mount sshfs share with systemd.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:17:04 2020
  InstallationDate: Installed on 2019-11-03 (367 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1902891] [NEW] "Too many levels of symbolic links” error when using systemd to mount sshfs

2020-11-04 Thread Sami Pietila
Public bug reported:

I have asked question in askubuntu about "Too many levels of symbolic
links” error when trying to use systemd to mount sshfs
(https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
links-error-when-using-systemd)

I have not got any responses, so I am submitting a bug report. If this
is not a bug, please advice how to mount sshfs share with systemd.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 16:17:04 2020
InstallationDate: Installed on 2019-11-03 (367 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 81H1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
dmi.bios.date: 08/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8PCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 530S-14ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
dmi.product.family: ideapad 530S-14ARR
dmi.product.name: 81H1
dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
dmi.product.version: Lenovo ideapad 530S-14ARR
dmi.sys.vendor: LENOVO

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


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

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

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

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

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

[Bug 1897396] [NEW] Unable to make chromium-chromedriver work with selenium

2020-09-26 Thread Sami Pietila
Public bug reported:

Trying to use chrome web driver instead of firefox driver in selenium
gives following error. How to use chromium with selenium now when it is
packaged in Snap?

Error message:
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome 
failed to start: exited abnormally.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location 
/snap/chromium/current/command-chromium.wrapper is no longer running, so 
ChromeDriver is assuming that Chrome has crashed.)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-chromedriver 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 26 19:10:59 2020
InstallationDate: Installed on 2019-11-03 (328 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-03-28 (181 days ago)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Unable to make chromium-chromedriver work with selenium

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

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

[Bug 1886653] [NEW] cups-pki-expired

2020-07-07 Thread Sami Pietila
Public bug reported:

The printer always goes to stopped state in Ubuntu 20.04. Print
properties window has status message saying: "cups-pki-expired". I have
HP color laserjet m552, which Ubuntu discovers directly from the local
network and configures automatically.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  7 14:40:00 2020
InstallationDate: Installed on 2019-11-03 (247 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: 
implicitclass://HP_Color_LaserJet_M552_5F80BF_/
MachineType: LENOVO 81H1
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago)
dmi.bios.date: 08/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8PCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 530S-14ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
dmi.product.family: ideapad 530S-14ARR
dmi.product.name: 81H1
dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
dmi.product.version: Lenovo ideapad 530S-14ARR
dmi.sys.vendor: LENOVO

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


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

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

Title:
  cups-pki-expired

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

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

[Bug 1877711] Re: Libreoffice snap can read but not save files over SSH

2020-05-23 Thread Sami Pietila
Reported. I also tried to report bugs with chromium-browser, but it
seems "ubuntu-bug chromium-browser" does not work. It just hangs.

Anyway, chromium browser does not work with jupyter-notebook as running 
"jupyter-notebook" starts the browser with following messages:"
Access to the file was deniedThe file at 
file:///home/sami/.local/share/jupyter/runtime/nbserver-208350-open.html is not 
readable. It may have been removed, moved, or file permissions may be 
preventing access.
ERR_ACCESS_DENIED"

I think this might be a snap issue. I wanted to ask how can I switch to
chromium-browser deb package like with libreoffice? Like with
libreoffice, the chromium-browser snap-version is very slow.

** Attachment added: "chromium-bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+attachment/5375877/+files/chromium-bug.png

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

Title:
  Libreoffice snap can read but not save files over SSH

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

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

[Bug 1880301] [NEW] Unable to install as not supported

2020-05-23 Thread Sami Pietila
Public bug reported:

Hi,

Sometimes the software center gives an error message "Unable to install
xxx as not supported". However installing with apt works just fine. Bug
1877711 has an attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 23 15:25:34 2020
InstallationDate: Installed on 2019-11-03 (202 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-software
UpgradeStatus: Upgraded to focal on 2020-03-28 (55 days ago)

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


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

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

Title:
  Unable to install as not supported

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

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

[Bug 1877711] Re: Libreoffice snap can read but not save files over SSH

2020-05-16 Thread Sami Pietila
If I try to install libreoffice deb version from the software center, I
get a message saying it is not supported. Please see the attached
screenshot.

** Attachment added: "not-supported.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+attachment/5372556/+files/not-supported.png

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

Title:
  Libreoffice snap can read but not save files over SSH

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

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

[Bug 1877711] Re: Libreoffice can read but not save files over SSH

2020-05-14 Thread Sami Pietila
I found a fix. I did uninstall the snap and installed deb packages from
libreoffice home page. Saving works and starting libreoffice is fast
again.

Is it possible to have libreoffice deb packages back to Ubuntu? It looks
like snap is quite problematic and slow.

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

Title:
  Libreoffice can read but not save files over SSH

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

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

[Bug 1877711] Re: Libreoffice can read but not save files over SSH

2020-05-12 Thread Sami Pietila
Hi,

Please see the messages from the log. There seems to be some "libinput
error: client bug" messages, but I don't know if they are related to
this error.

$ journalctl -f
-- Logs begin at Wed 2020-02-19 09:28:50 EET. --
touko 12 18:09:26 530s slack.desktop[140375]: [05/12/20, 18:09:26:659] info: 
[DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]
touko 12 18:09:48 530s systemd-resolved[636]: Using degraded feature set (TCP) 
for DNS server 2001:14b8:1000::2.
touko 12 18:10:18 530s systemd-resolved[636]: Using degraded feature set (UDP) 
for DNS server 2001:14b8:1000::1.
touko 12 18:10:19 530s slack.desktop[140375]: [05/12/20, 18:10:19:926] info: 
[DND] (TADSNN2D9) Checking for changes in DND status for the following members: 
UASJ1J57H,UAE0FL04S,UARGU2CQH,UAN2ACN2W,UAH2W0Q1K,UAY6FKSHL,UAGUME46N
touko 12 18:10:19 530s slack.desktop[140375]: [05/12/20, 18:10:19:927] info: 
[DND] (TADSNN2D9) Will check for changes in DND status again in 5 minutes
touko 12 18:10:33 530s systemd-resolved[636]: Using degraded feature set (UDP) 
for DNS server 2001:14b8:1000::2.
touko 12 18:10:50 530s systemd-resolved[636]: Using degraded feature set (TCP) 
for DNS server 2001:14b8:1000::1.
touko 12 18:11:04 530s slack.desktop[140375]: [05/12/20, 18:11:04:927] info: 
[CHECK-FOR-OLD-IMS] (TADSNN2D9) Within limit: 11
touko 12 18:11:06 530s slack.desktop[140375]: [05/12/20, 18:11:06:723] info: 
Store: SET_SYSTEM_IDLE active
touko 12 18:11:06 530s slack.desktop[140375]: [05/12/20, 18:11:06:728] info: 
[DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]
touko 12 18:11:15 530s systemd-resolved[636]: Using degraded feature set (TCP) 
for DNS server 2001:14b8:1000::2.
touko 12 18:11:46 530s slack.desktop[140375]: [05/12/20, 18:11:46:758] info: 
Store: SET_SYSTEM_IDLE idle_taskbar
touko 12 18:11:46 530s slack.desktop[140375]: [05/12/20, 18:11:46:762] info: 
[DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]
touko 12 18:11:56 530s slack.desktop[140375]: [05/12/20, 18:11:56:760] info: 
Store: SET_SYSTEM_IDLE active
touko 12 18:11:56 530s slack.desktop[140375]: [05/12/20, 18:11:56:766] info: 
[DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]
touko 12 18:11:59 530s dbus-daemon[1097]: [session uid=1000 pid=1097] 
Activating via systemd: service name='org.freedesktop.Tracker1' 
unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=1087 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
touko 12 18:11:59 530s systemd[1060]: Starting Tracker metadata database store 
and lookup manager...
touko 12 18:11:59 530s dbus-daemon[1097]: [session uid=1000 pid=1097] 
Successfully activated service 'org.freedesktop.Tracker1'
touko 12 18:11:59 530s systemd[1060]: Started Tracker metadata database store 
and lookup manager.
touko 12 18:11:59 530s dbus-daemon[1097]: [session uid=1000 pid=1097] 
Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' 
unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=1087 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
touko 12 18:11:59 530s systemd[1060]: Starting Tracker metadata extractor...
touko 12 18:11:59 530s tracker-extract[169737]: Set scheduler policy to 
SCHED_IDLE
touko 12 18:11:59 530s tracker-extract[169737]: Setting priority nice level to 
19
touko 12 18:12:00 530s dbus-daemon[1097]: [session uid=1000 pid=1097] 
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
touko 12 18:12:00 530s systemd[1060]: Started Tracker metadata extractor.
touko 12 18:12:10 530s systemd[1060]: tracker-extract.service: Succeeded.
touko 12 18:12:14 530s gnome-shell[1211]: libinput error: client bug: timer 
event8 debounce: scheduled expiry is in the past (-4ms), your system is too slow
touko 12 18:12:14 530s gnome-shell[1211]: libinput error: client bug: timer 
event8 debounce short: scheduled expiry is in the past (-17ms), your system is 
too slow


** Attachment added: "The message libreoffice shows when trying to save a file."
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+attachment/5370345/+files/Screenshot%20from%202020-05-12%2018-11-59.png

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

Title:
  Libreoffice can read but not save files over SSH

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

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

[Bug 1877711] Re: Libreoffice can read but not save files over SSH

2020-05-11 Thread Sami Pietila
I am using the default Ubuntu Desktop (gnome). I am connecting to the
server by using the desktop file browser (Named "Files" in ubuntu menu):
ctl+l and typing the address "ssh://untuserver.somedomain.com". Then
using the file browser to open a file and later trying to save it.
Saving the file fails. It seems Ubuntu Desktop 20.04 version is no
longer compatible with Ubuntu server.

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

Title:
  Libreoffice can read but not save files over SSH

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

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

[Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

2020-05-09 Thread Sami Pietila
I have the latest Ubuntu 20.04 and it also seems to have this bug. There
are workarounds, but I think it should work out of the box like it does
on Windows. It is weird to have this kind of bug as Xbox One controller
might just be the most popular controller and these kinds of issues
prevent people from gaming on Linux.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

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

[Bug 1877711] [NEW] Libreoffice can read but not save files over SSH

2020-05-09 Thread Sami Pietila
Public bug reported:

With Ubuntu 20.04 libreoffice can not anymore save files over SSH share.

When trying to save, it says: Error saving the document. General Error.
General input/output error.

In addition, starting from Ubuntu 20.04 libreoffice has become very slow
to start.

** Affects: libreoffice (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/1877711

Title:
  Libreoffice can read but not save files over SSH

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-09 Thread Sami Pietila
I further tested this new 4.18.0-18-generic kernel and with this kernel
the wifi seems to work very good. I did not observe any slowness as I
did with the patched 4.18.0-16 kernel.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-09 Thread Sami Pietila
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-09 Thread Sami Pietila
Now dist-upgrade found that kernel. I can confirm, with this kernel
rfkill reports the device unblocked.

ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 3 wlan  phy0  unblocked unblocked
 4 bluetooth hci0  unblocked unblocked

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-07 Thread Sami Pietila
Hi,

I think I have enabled pre-released updates. Is the kernel version
(4.18.0-17-generic), the one that should have this patch?

I am wondering because wifi does not seem to work with this kernel.

Thank

** Attachment added: "devel-enabled.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818204/+attachment/5253636/+files/devel-enabled.png

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-05 Thread Sami Pietila
Hi

How do I test the proposed patch? I enabled backports. Then did apt
update & apt dist-upgrade.

My Linux version is:
Linux 530s 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked   blocked
 1 bluetooth ideapad_bluetooth unblocked   blocked
 2 bluetooth hci0  unblocked unblocked
 3 wlan  phy0blocked unblocked

With 4.18.0-17 the wifi is hard blocked.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-28 Thread Sami Pietila
Hi,

I tested with only the patched kernel and it enables wifi.

However, there still seems to be something weird happening. Even though,
the wifi seems to work, it might take from seconds to minutes for a web
page to load. It feels like having a bad connection, but in a mixed way.
For example, it might take long time to get into youtube and have video
running, but the video then might run ok. With MS Windows, the wifi
works well and there are no delays.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-05 Thread Sami Pietila
Ok.

Thank you for solving this issue!

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-04 Thread Sami Pietila
Looks good. With this kernel, wlan works just fine. I can connect
normally to the wlan networks.

rfkill now shows:
ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 bluetooth hci0  unblocked unblocked
 3 wlan  phy0  unblocked unblocked

Can I somehow switch to this new kernel in 18.04 in such a way that it
keeps getting security updates?

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-04 Thread Sami Pietila
What can I do to get it working? Can I somehow force the system not to
think it is hardware blocked?

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-04 Thread Sami Pietila
I don't think this laptop has such a block button. There is a button
(F7) with airplane symbol. It does not seem to have any effect (even
when used with FN key).

What I know is:

- If I boot to Windows, the wifi works there.
- Bluetooth works fine in Linux.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] nmcli-dev.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243331/+files/nmcli-dev.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] WifiSyslog.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetDevice.virbr0.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243318/+files/NetDevice.virbr0.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] UdevDb.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] ProcModules.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetworkManager.conf.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243321/+files/NetworkManager.conf.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] IwConfig.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetDevice.lo.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243317/+files/NetDevice.lo.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetDevice.enx00e04c704f68.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.enx00e04c704f68.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243316/+files/NetDevice.enx00e04c704f68.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] ProcCpuinfoMinimal.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] PciNetwork.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243322/+files/PciNetwork.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] RfKill.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] PulseList.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] ProcInterrupts.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] ProcEnviron.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetDevice.wlp1s0.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.wlp1s0.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243320/+files/NetDevice.wlp1s0.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] NetDevice.virbr0-nic.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243319/+files/NetDevice.virbr0-nic.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] CurrentDmesg.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] IpAddr.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243312/+files/IpAddr.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Lspci.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] CRDA.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Dependencies.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Lsusb.txt

2019-03-03 Thread Sami Pietila
apport information

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-03 Thread Sami Pietila
apport information

** Tags added: apport-collected

** Description changed:

  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter (rev 31).
  
  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  sami   1315 F pulseaudio
+  /dev/snd/controlC0:  sami   1315 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2019-02-20 (11 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ IpRoute:
+  default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 
+  130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100 
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+ MachineType: LENOVO 81H1
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+ Package: network-manager 1.10.6-2ubuntu1.1
+ PackageArchitecture: amd64
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-15-generic N/A
+  linux-backports-modules-4.18.0-15-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic wayland-session wayland-session
+ Uname: Linux 4.18.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/17/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 8PCN45WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40700 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo ideapad 530S-14ARR
+ dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
+ dmi.product.family: ideapad 530S-14ARR
+ dmi.product.name: 81H1
+ dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
+ dmi.product.version: Lenovo ideapad 530S-14ARR

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-01 Thread Sami Pietila
Interestingly, I have Lenovo 510s with Qualcomm Atheros QCA9377 802.11ac
Wireless Network Adapter (rev 30) and it works just fine on Ubuntu.

For me, it appears as rev 30 works and rev 31 does not. Is this
possible?

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

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

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

[Bug 1818204] [NEW] Qualcomm Atheros QCA9377 wireless does not work

2019-03-01 Thread Sami Pietila
Public bug reported:

I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
Wireless Network Adapter (rev 31).

The menu shows that wireless is off. Turning on the wireless from the
menu does not do anything.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1.1
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  1 11:42:34 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-02-20 (8 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 
metric 100
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH  SLAVE
 Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  155143 
 pe  1. maaliskuuta 2019 11.42.13  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  activated  
/org/freedesktop/NetworkManager/ActiveConnection/11  --
 virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge155143 
 pe  1. maaliskuuta 2019 11.42.13  no   0 no
/org/freedesktop/NetworkManager/Settings/2  yes virbr0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1   --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

** Description changed:

  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter (rev 31).
  
- The menu shows that wireless is off. Turning wireless from the menu does
- not do anything.
+ The menu shows that wireless is off. Turning on the wireless from the
+ menu does not do anything.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
-  default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 
-  130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100 
-  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
-  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+  default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
+  130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
-  NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE 
-  Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/

[Bug 1773744] Re: Desktop session crash

2018-06-07 Thread Sami Pietila
Hi,

>Please also tell us what bug IDs were created by:
>  ubuntu-bug _usr_bin_gnome-shell.1000.crash
>  ubuntu-bug _usr_bin_Xwayland.1000.crash
>  ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

I have reported only one bug ID and it is the current bug with id
1773744.

>You might find them here:
>  https://bugs.launchpad.net/~/+reportedbugs?orderby=-id&start=0

Of the list entries only #1773744 concerns this issue.

> If you don't then please have a look at https://errors.ubuntu.com/user/ID 
> where ID is the 
> contents of the machine's /var/lib/whoopsie/whoopsie-id file. If you find any 
> relevant 
> crash reports there then please provide links to them here.

https://errors.ubuntu.com/oops/597cc890-6405-11e8-9899-fa163ed44aae
https://errors.ubuntu.com/oops/35ae4600-6405-11e8-8466-fa163e171d9b
https://errors.ubuntu.com/oops/2a4719ae-6405-11e8-8ec0-fa163e8d4bab

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

Title:
  Desktop session crash

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

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

[Bug 1773744] Re: Desktop session crash

2018-05-30 Thread Sami Pietila
Hi

1) I did run given commands.

2) I rebooted the machine with three monitors connected. I tried with
both Metacity and Compiz options which had appeared. Trying to log in
resulted crash and returning back to login screen.

3) HP ZR2440, HP 27i, Dell UltraSharp U2515H

4) Monitors are connected with Display port cables. Two of displays are
connected to the integrated intel graphics controller. One display is
connected to Radeon card.

5) No.

6) The 16.04.4 live cd seems to work just fine with my three monitors.

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

Title:
  Desktop session crash

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

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

[Bug 1773744] Re: Desktop session crash

2018-05-29 Thread Sami Pietila
Hi Christopher,

Thank you for taking time to look into this issue.

1) No. The issue started when I connected third monitor to my Ubuntu PC.
I have not tried 3-monitor setup with previous Ubuntu releases.

2) ls -la /var/crash
total 256020
drwxrwsrwt 1 root whoopsie   366 touko 29 15:03 .
drwxr-xr-x 1 root root   128 tammi 27  2017 ..
-rwxrwxrwx 1 root whoopsie 0 touko 29 15:03 .lock
-rw-r- 1 sami whoopsie   5969518 touko 25 19:24 
_opt_Gitter_linux64_Gitter.1000.crash
-rw-r- 1 sami whoopsie  28507228 touko 25 19:30 
_usr_bin_gnome-shell.1000.crash
-rw-r- 1 sami whoopsie  50895637 touko 28 09:58 _usr_bin_Xwayland.1000.crash
-rw-r- 1 sami whoopsie 105541228 touko 25 19:12 
_usr_lib_chromium-browser_chromium-browser.1000.crash
-rw-r- 1 sami whoopsie  71245625 touko 25 19:24 
_usr_lib_xorg_Xorg.1000.crash

3) I now did install gnome-session-flashback and rebooted the machine.
Even after this, the desktop crashed.

4) I just downloaded and booted to the latest cd-image from the link.
Desktop on the cd-image crashed as well with three monitors.

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

Title:
  Desktop session crash

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

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

[Bug 1773744] Re: Desktop session crash

2018-05-28 Thread Sami Pietila
I can see error messages like this in the log: "CRITICAL: We failed, but
the fail whale is dead. Sorry"

touko 28 10:05:38 elite gsd-clipboard[5250]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gsd-xsettings[5224]: gsd-xsettings: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite unknown[5232]: gsd-wacom: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
touko 28 10:05:38 elite unknown[5210]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gsd-color[5245]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-shell[5099]: gnome-shell: Fatal IO error 0 
(Success) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
touko 28 10:05:38 elite polkitd(authority=local)[1476]: Unregistered 
Authentication Agent for unix-session:5 (system bus name :1.247, object path 
/org/freedesktop/PolicyKit1/AuthenticationAge
touko 28 10:05:38 elite gsd-color[2275]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2515H_9X2VY5CG12LL_sami_
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
touko 28 10:05:38 elite gnome-control-c[5869]: gnome-control-center: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
touko 28 10:05:38 elite gnome-session-binary[4955]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
touko 28 10:05:38 elite gnome-session-binary[4955]: CRITICAL: We failed, but 
the fail whale is dead. Sorry
touko 28 10:05:38 elite kernel: rfkill: input handler enabled
touko 28 10:05:38 elite at-spi-bus-launcher[5057]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
touko 28 10:05:38 elite at-spi-bus-launcher[5057]:   after 69 requests (69 
known processed) with 0 events remaining.
touko 28 10:05:38 elite gdm-password][4897]: pam_unix(gdm-password:session): 
session closed for user sami
touko 28 10:05:38 elite gnome-shell[2080]: Object St.Icon (0x55f7781d71a0), has 
been already finalized. Impossible to set any property to it.
touko 28 10:05:38 elite gnome-shell[2080]: Object St.BoxLayout 
(0x55f7781d5c10), has been already finalized. Impossible to set any property to 
it.
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: == Stack trace for 
context 0x55f7776c9320 ==
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: #0 0x55f777a77fe0 i   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7feaa42c96f8 @ 231)
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: #1 0x7ffd8bc93230 b   
resource:///org/gnome/gjs/modules/_legacy.

[Bug 1773744] [NEW] Desktop session crash

2018-05-28 Thread Sami Pietila
Public bug reported:

If I connect third monitor to my Ubuntu PC, the whole graphical display
session crashes. Additionally, the login does not show texts correctly.
The texts are mostly missing.

The errors happend with both Wayland and X.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 28 10:15:54 2018
DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X OEM] 
[103c:90b8]
InstallationDate: Installed on 2016-11-22 (551 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.18
dmi.board.asset.tag: CZC3427KBP
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC3427KBP
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash ubuntu wayland-session

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

Title:
  Desktop session crash

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

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

[Bug 1705825] [NEW] Freeze

2017-07-22 Thread Sami Pietila
Public bug reported:

Display freezes and dmesg at console shows following messages:

[68650.636711] [drm] GPU HANG: ecode 9:0:0x87f9bcfb, in Xorg [1070], reason: 
Hang on render ring, action: reset
[68650.636766] drm/i915: Resetting chip after gpu hang
[68650.636835] [drm] RC6 on
[68650.649123] [drm] GuC firmware load skipped
[68665.561159] drm/i915: Resetting chip after gpu hang
[68665.561263] [drm] RC6 on
[68665.575264] [drm] GuC firmware load skipped
[68683.545135] drm/i915: Resetting chip after gpu hang
[68683.545221] [drm] RC6 on
[68683.559329] [drm] GuC firmware load skipped
[68693.561560] drm/i915: Resetting chip after gpu hang
[68693.561654] [drm] RC6 on
[68693.575457] [drm] GuC firmware load skipped

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Sat Jul 22 17:28:46 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1906] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 510 [17aa:381b]
InstallationDate: Installed on 2017-07-14 (8 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e360 Atheros Communications, Inc. 
 Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80TK
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=fb70cf2a-4a2f-4379-b5ad-2ef44eafad44 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 0VCN22WW(V1.06)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo ideapad 5
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 510S-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80TK:pvrLenovoideapad510S-14ISK:rvnLENOVO:rnLenovoideapad5:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-14ISK:
dmi.product.name: 80TK
dmi.product.version: Lenovo ideapad 510S-14ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Sat Jul 22 17:24:28 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu zesty

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

Title:
  Freeze

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

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


[Bug 1652910] [NEW] clinfo / opencl not working

2016-12-28 Thread Sami Pietila
Public bug reported:

The system (Ubuntu 16.10) has Intel(R) Core(TM) i7-4770 CPU with following 
opencl related packages installed:
beignet
beignet-dev
beignet-opencl-icd
ocl-icd-dbg
ocl-icd-dev
ocl-icd-libopencl1
ocl-icd-opencl-dev

Running clinfo command gives following error message:
terminate called after throwing an instance of 'cl::Error'
  what():  clGetPlatformIDs
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: clinfo 2.1.16.01.12-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Dec 28 10:49:20 2016
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2
 libgcc1 1:6.2.0-5ubuntu12
 ocl-icd-libopencl1 2.2.9-1
InstallationDate: Installed on 2016-11-22 (35 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: clinfo
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  clinfo / opencl not working

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

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


[Bug 1514189] [NEW] There appear artifacts sometimes on the screen

2015-11-08 Thread Sami Pietila
Public bug reported:

Following error warning from dmesg:

[54580.305170] nouveau E[compiz[2090]] fail set_domain
[54580.305176] nouveau E[compiz[2090]] validating bo list
[54580.305202] nouveau E[compiz[2090]] validate: -22
[54580.657058] nouveau E[  PGRAPH][:01:00.0] magic set 0:
[54580.657071] nouveau E[  PGRAPH][:01:00.0]0x00408604: 0x20092505
[54580.657076] nouveau E[  PGRAPH][:01:00.0]0x00408608: 0x0041a27f
[54580.657079] nouveau E[  PGRAPH][:01:00.0]0x0040860c: 0x4432
[54580.657083] nouveau E[  PGRAPH][:01:00.0]0x00408610: 0xa000
[54580.657086] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP0:  FAULT
[54580.657096] nouveau E[  PGRAPH][:01:00.0] magic set 1:
[54580.657101] nouveau E[  PGRAPH][:01:00.0]0x00408e04: 0x20099405
[54580.657104] nouveau E[  PGRAPH][:01:00.0]0x00408e08: 0x0041a9f5
[54580.657108] nouveau E[  PGRAPH][:01:00.0]0x00408e0c: 0x4432
[54580.657112] nouveau E[  PGRAPH][:01:00.0]0x00408e10: 0xa000
[54580.657114] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP1:  FAULT
[54580.657121] nouveau E[  PGRAPH][:01:00.0] ch 6 [0x000f93e000 
compiz[2090]] subc 3 class 0x8597 mthd 0x153c data 0x
[54580.657134] nouveau E[ PFB][:01:00.0] trapped read at 0x0041a27f00 
on channel 0xf93e [compiz[2090]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT
[54580.673591] nouveau E[  PGRAPH][:01:00.0] magic set 0:
[54580.673600] nouveau E[  PGRAPH][:01:00.0]0x00408604: 0x20082d0a
[54580.673604] nouveau E[  PGRAPH][:01:00.0]0x00408608: 0x0041afa3
[54580.673609] nouveau E[  PGRAPH][:01:00.0]0x0040860c: 0x4432
[54580.673613] nouveau E[  PGRAPH][:01:00.0]0x00408610: 0xa000
[54580.673616] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP0:  FAULT
[54580.673626] nouveau E[  PGRAPH][:01:00.0] magic set 1:
[54580.673631] nouveau E[  PGRAPH][:01:00.0]0x00408e04: 0x20097a05
[54580.673635] nouveau E[  PGRAPH][:01:00.0]0x00408e08: 0x0041a9f5
[54580.673640] nouveau E[  PGRAPH][:01:00.0]0x00408e0c: 0x4432
[54580.673643] nouveau E[  PGRAPH][:01:00.0]0x00408e10: 0xa000
[54580.673646] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP1:  FAULT
[54580.673654] nouveau E[  PGRAPH][:01:00.0] ch 6 [0x000f93e000 
compiz[2090]] subc 3 class 0x8597 mthd 0x153c data 0x
[54580.673670] nouveau E[ PFB][:01:00.0] trapped read at 0x0041a9f500 
on channel 0xf93e [compiz[2090]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT
[54580.691258] nouveau E[  PGRAPH][:01:00.0] magic set 0:
[54580.691269] nouveau E[  PGRAPH][:01:00.0]0x00408604: 0x20095405
[54580.691272] nouveau E[  PGRAPH][:01:00.0]0x00408608: 0x0041a27f
[54580.691276] nouveau E[  PGRAPH][:01:00.0]0x0040860c: 0x4432
[54580.691279] nouveau E[  PGRAPH][:01:00.0]0x00408610: 0xa000
[54580.691281] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP0:  FAULT
[54580.691290] nouveau E[  PGRAPH][:01:00.0] magic set 1:
[54580.691293] nouveau E[  PGRAPH][:01:00.0]0x00408e04: 0x20081305
[54580.691296] nouveau E[  PGRAPH][:01:00.0]0x00408e08: 0x0041ac3a
[54580.691299] nouveau E[  PGRAPH][:01:00.0]0x00408e0c: 0x4432
[54580.691301] nouveau E[  PGRAPH][:01:00.0]0x00408e10: 0xa000
[54580.691303] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP1:  FAULT
[54580.691314] nouveau E[  PGRAPH][:01:00.0] ch 6 [0x000f93e000 
compiz[2090]] subc 3 class 0x8597 mthd 0x0f04 data 0x
[54580.691329] nouveau E[ PFB][:01:00.0] trapped read at 0x0041a27f00 
on channel 0xf93e [compiz[2090]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT
[54580.703737] nouveau E[  PGRAPH][:01:00.0] magic set 0:
[54580.703744] nouveau E[  PGRAPH][:01:00.0]0x00408604: 0x20087305
[54580.703748] nouveau E[  PGRAPH][:01:00.0]0x00408608: 0x0041a27f
[54580.703751] nouveau E[  PGRAPH][:01:00.0]0x0040860c: 0x4432
[54580.703754] nouveau E[  PGRAPH][:01:00.0]0x00408610: 0xa000
[54580.703756] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP0:  FAULT
[54580.703761] nouveau E[  PGRAPH][:01:00.0] magic set 1:
[54580.703764] nouveau E[  PGRAPH][:01:00.0]0x00408e04: 0x20086a05
[54580.703767] nouveau E[  PGRAPH][:01:00.0]0x00408e08: 0x0041ac3a
[54580.703770] nouveau E[  PGRAPH][:01:00.0]0x00408e0c: 0x4432
[54580.703773] nouveau E[  PGRAPH][:01:00.0]0x00408e10: 0xa000
[54580.703774] nouveau E[  PGRAPH][:01:00.0] TRAP_TEXTURE - TP1:  FAULT
[54580.703779] nouveau E[  PGRAPH][:01:00.0] ch 6 [0x000f93e000 
compiz[2090]] subc 3 class 0x8597 mthd 0x0f04 data 0x
[54580.703791] nouveau E[ PFB][:01:00.0] trapped read at 0x0041a27f00 
on channel 0xf93e [compiz[2090]] PGRAPH/TEXTURE/00 reason:

[Bug 1509765] [NEW] Ubuntu 15.10 desktop freezes

2015-10-25 Thread Sami Pietila
Public bug reported:

Ubuntu desktop freezes.

>From console, it can be seen that compiz process takes 100% of CPU.
Killing compiz resolves the freeze.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sun Oct 25 09:44:11 2015
DistUpgraded: 2015-10-07 11:55:16,669 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-30-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-14-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. Device [106b:00c7]
InstallationDate: Installed on 2015-09-15 (40 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Apple Inc. MacBookPro6,2
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=cd62ef7a-701d-4f57-8b44-6fe955f85302 ro quiet splash vt.handoff=7
SourcePackage: compiz
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-07 (17 days ago)
dmi.bios.date: 12/09/11
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Oct 24 21:53:22 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug ubuntu wily

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

Title:
  Ubuntu 15.10 desktop freezes

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

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


[Bug 1457180] [NEW] btrfs crash

2015-05-20 Thread Sami Pietila
Public bug reported:

btrfs filesystem crash when deleting files.

dmesg shows:
[41255.051093] kernel BUG at /build/buildd/linux-3.19.0/fs/btrfs/inode.c:3142!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-16-generic 3.19.0-16.16
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Wed May 20 21:48:51 2015
InstallationDate: Installed on 2015-04-10 (40 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=17624252-4d7d-4b40-8ee9-b3a78b7210ef ro quiet splash vt.handoff=7
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  btrfs crash

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

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


[Bug 1341349] Re: Windows are being moved by unity

2014-11-30 Thread Sami Pietila
The bug is still present in Ubuntu 14.10.

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

Title:
  Windows are being moved by unity

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

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


[Bug 1394502] [NEW] Can not attach to running screen session

2014-11-20 Thread Sami Pietila
Public bug reported:

I have ubuntu 14.04 LTS version and there is a screen session. The
session is alive, it has a program running which is generating files. I
can also see it on the process list (ps aux):

sampie1377  0.0  0.0  87140  1736 ?Ss   marras03   0:00
SCREEN -R -d

However, I am unable to attach to that session. 
"screen -list" command says: "No Sockets found in /var/run/screen/S-sampie."

"screen -r" says: "There is no screen to be resumed."

I don't know if this is a bug or not, but how can I attach to the
existing screen session?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: screen 4.1.0~20120320gitdb59704-9
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 20 10:44:01 2014
InstallationDate: Installed on 2014-07-08 (135 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: screen
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Can not attach to running screen session

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

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


[Bug 1393327] Re: Ubuntu 14.04 LTS Server Kernel Crash

2014-11-18 Thread Sami Pietila
The crash has occurred only once. Unfortunately,  I don't know how to
reproduce the problem. The server had been running with high
computational load for several days. Perhaps that was contributing to
the problem.

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

Title:
  Ubuntu 14.04 LTS Server Kernel Crash

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

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


[Bug 1393327] Re: Ubuntu 14.04 LTS Server Kernel Crash

2014-11-18 Thread Sami Pietila
The server has always been 14.04 LTS, so no big kernel upgrades. There
was however an installation of a new VM machine ongoing. Perhaps
something in that caused the host server to crash.

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

Title:
  Ubuntu 14.04 LTS Server Kernel Crash

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

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


[Bug 1393327] [NEW] Ubuntu 14.04 LTS Server Kernel Crash

2014-11-17 Thread Sami Pietila
Public bug reported:

A Dell R720 server with Ubuntu 14.04 LTS crashed with following (see
attachment) kernel messages scrolling on the terminal screen.

The server is a production server. It is not possible to install an
upstream kernel.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 marra 17 09:54 seq
 crw-rw 1 root audio 116, 33 marra 17 09:54 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Nov 17 10:03:33 2014
InstallationDate: Installed on 2014-02-26 (263 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20140219)
MachineType: Dell Inc. PowerEdge R720
PciMultimedia:
 
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=c03eb237-955a-4dee-bba1-deded53df372 ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic  N/A
 linux-firmware 1.127.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.2.2
dmi.board.name: 0DCWD1
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.2:bd01/16/2014:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0DCWD1:rvrA01:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R720
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

** Attachment added: "r720-crash.png"
   
https://bugs.launchpad.net/bugs/1393327/+attachment/4262180/+files/r720-crash.png

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

Title:
  Ubuntu 14.04 LTS Server Kernel Crash

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

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


[Bug 1329672] Re: Ubuntu desktop hangs

2014-11-14 Thread Sami Pietila
This seems to be 14.04 LTS specific issue. The problem is has not been
occurring after upgrading to 14.10.

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

Title:
  Ubuntu desktop hangs

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

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


[Bug 53887] Re: [patch] Command completion should be enhanced

2014-11-04 Thread Sami Pietila
Upstream has now configuration parameters to make almost desired
behavior.

** Changed in: bash (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [patch] Command completion should be enhanced

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

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


[Bug 1388781] Re: Ubuntu server 14.04.1 LTS freeze

2014-11-03 Thread Sami Pietila
The machine is a production server. Is this kernel something that can be
considered for production server usage? I am thinking could there be any
security conserns.

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

Title:
  Ubuntu server 14.04.1 LTS freeze

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

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


[Bug 1388781] [NEW] Ubuntu server 14.04.1 LTS freeze

2014-11-03 Thread Sami Pietila
Public bug reported:

Ubuntu server 14.04 LTS freezes. Before the total freeze, kernel.log is
showing messages like:

Nov  2 07:03:56 node1 kernel: [1941380.104003] BUG: soft lockup - CPU#0 stuck 
for 23s! [nfsd:1320]
Nov  2 07:03:56 node1 kernel: [1941380.104003] Modules linked in: btrfs 
raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsd 
auth_rpcgss nfs_acl nfs lockd sunrpc fscache cirrus ttm drm_kms_helper drm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea joydev 
sysfillrect aesni_intel i2c_piix4 sysimgblt aes_x86_64 lrw gf128mul mac_hid 
glue_helper serio_raw ablk_helper cryptd lp parport hid_generic usbhid hid 
psmouse floppy
Nov  2 07:03:56 node1 kernel: [1941380.104003] CPU: 0 PID: 1320 Comm: nfsd Not 
tainted 3.13.0-37-generic #64-Ubuntu
Nov  2 07:03:56 node1 kernel: [1941380.104003] Hardware name: Red Hat Inc. 
OpenStack Nova, BIOS 0.5.1 01/01/2007
Nov  2 07:03:56 node1 kernel: [1941380.104003] task: 880ecaeb1800 ti: 
880ec7744000 task.ti: 880ec7744000
Nov  2 07:03:56 node1 kernel: [1941380.104003] RIP: 0010:[]  
[] _raw_spin_lock+0x32/0x50
Nov  2 07:03:56 node1 kernel: [1941380.104003] RSP: 0018:880ec7745da8  
EFLAGS: 0206
Nov  2 07:03:56 node1 kernel: [1941380.104003] RAX: 6072 RBX: 
880eca3ae3c0 RCX: eed2
Nov  2 07:03:56 node1 kernel: [1941380.104003] RDX: eed8 RSI: 
eed8 RDI: a029ac80
Nov  2 07:03:56 node1 kernel: [1941380.104003] RBP: 880ec7745da8 R08: 
18bb5554 R09: 18282e0518bb5554
Nov  2 07:03:56 node1 kernel: [1941380.104003] R10: 6a81e9b4 R11: 
18282e0518bb5554 R12: 880ec7745d78
Nov  2 07:03:56 node1 kernel: [1941380.104003] R13: 880ec784c200 R14: 
 R15: ee626da3
Nov  2 07:03:56 node1 kernel: [1941380.104003] FS:  () 
GS:880f1fc0() knlGS:
Nov  2 07:03:56 node1 kernel: [1941380.104003] CS:  0010 DS:  ES:  CR0: 
80050033
Nov  2 07:03:56 node1 kernel: [1941380.104003] CR2: 7f554c039000 CR3: 
000ecbcd8000 CR4: 000406f0
Nov  2 07:03:56 node1 kernel: [1941380.104003] Stack:
Nov  2 07:03:56 node1 kernel: [1941380.104003]  880ec7745de8 
a026d666 006c 880ec807e000
Nov  2 07:03:56 node1 kernel: [1941380.104003]  a02974d8 
88010317e018 88010317e000 001c
Nov  2 07:03:56 node1 kernel: [1941380.104003]  880ec7745e20 
a0261e12 880ec807e1e0 880ec807e000
Nov  2 07:03:56 node1 kernel: [1941380.104003] Call Trace:
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd_cache_update+0x76/0x150 [nfsd]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd_dispatch+0x192/0x200 [nfsd]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
svc_process_common+0x46d/0x6d0 [sunrpc]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
svc_process+0x107/0x170 [sunrpc]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd+0xbf/0x130 [nfsd]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
nfsd_destroy+0x80/0x80 [nfsd]
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
kthread+0xd2/0xf0
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
ret_from_fork+0x7c/0xb0
Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
Nov  2 07:03:56 node1 kernel: [1941380.104003] Code: 89 e5 b8 00 00 02 00 f0 0f 
c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 f2 b8 00 80 00 00 eb 
0c 0f 1f 44 00 00 f3 90 <83> e8 01 74 0a 0f b7 0f 66 39 ca 75 f1 5d c3 66 66 66 
90 66 66



Nov  2 07:03:56 node1 kernel: [1941352.144608] CPU: 2 PID: 135 Comm: khugepaged 
Not tainted 3.13.0-37-generic #64-Ubuntu
Nov  2 07:03:56 node1 kernel: [1941352.144608] Hardware name: Red Hat Inc. 
OpenStack Nova, BIOS 0.5.1 01/01/2007
Nov  2 07:03:56 node1 kernel: [1941352.144608] task: 880ec97e6000 ti: 
880ec908 task.ti: 880ec908
Nov  2 07:03:56 node1 kernel: [1941352.144608] RIP: 0010:[]  
[] copy_page+0x23/0xe0
Nov  2 07:03:56 node1 kernel: [1941352.144608] RSP: 0018:880ec9081d90  
EFLAGS: 00010206
Nov  2 07:03:56 node1 kernel: [1941352.144608] RAX: 23ba7000 RBX: 
880ee3010c00 RCX: 003a
Nov  2 07:03:56 node1 kernel: [1941352.144608] RDX: ffed RSI: 
88085076c000 RDI: 880023ba7000
Nov  2 07:03:56 node1 kernel: [1941352.144608] RBP: 880ec9081e50 R08: 
0008 R09: ffee
Nov  2 07:03:56 node1 kernel: [1941352.144608] R10: 57ff199b23194440 R11: 
0016 R12: 0001
Nov  2 07:03:56 node1 kernel: [1941352.144608] R13: ea0034194440 R14: 
880ed62e5110 R15: 880f1ffc1f00
Nov  2 07:03:56 node1 kernel: [1941352.144608] FS:  () 
GS:880f1fc4() knlGS:
Nov  2 07:03:56 node1 kernel: [1941352.144608] CS:  0010 DS:  ES:  CR0: 
80050033
N

[Bug 1388781] Re: Ubuntu server 12.04.1 LTS freeze

2014-11-03 Thread Sami Pietila
Oh, sorry. It is Ubuntu 14.04.1 LTS not 12.04. I am not sure how to
rename the bug.

** Summary changed:

- Ubuntu server 12.04.1 LTS freeze
+ Ubuntu server 14.04.1 LTS freeze

** Description changed:

- Ubuntu server 12.04 LTS freezes. Before the total freeze, kernel.log is
+ Ubuntu server 14.04 LTS freezes. Before the total freeze, kernel.log is
  showing messages like:
  
  Nov  2 07:03:56 node1 kernel: [1941380.104003] BUG: soft lockup - CPU#0 stuck 
for 23s! [nfsd:1320]
  Nov  2 07:03:56 node1 kernel: [1941380.104003] Modules linked in: btrfs 
raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsd 
auth_rpcgss nfs_acl nfs lockd sunrpc fscache cirrus ttm drm_kms_helper drm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea joydev 
sysfillrect aesni_intel i2c_piix4 sysimgblt aes_x86_64 lrw gf128mul mac_hid 
glue_helper serio_raw ablk_helper cryptd lp parport hid_generic usbhid hid 
psmouse floppy
  Nov  2 07:03:56 node1 kernel: [1941380.104003] CPU: 0 PID: 1320 Comm: nfsd 
Not tainted 3.13.0-37-generic #64-Ubuntu
  Nov  2 07:03:56 node1 kernel: [1941380.104003] Hardware name: Red Hat Inc. 
OpenStack Nova, BIOS 0.5.1 01/01/2007
  Nov  2 07:03:56 node1 kernel: [1941380.104003] task: 880ecaeb1800 ti: 
880ec7744000 task.ti: 880ec7744000
  Nov  2 07:03:56 node1 kernel: [1941380.104003] RIP: 0010:[] 
 [] _raw_spin_lock+0x32/0x50
  Nov  2 07:03:56 node1 kernel: [1941380.104003] RSP: 0018:880ec7745da8  
EFLAGS: 0206
  Nov  2 07:03:56 node1 kernel: [1941380.104003] RAX: 6072 RBX: 
880eca3ae3c0 RCX: eed2
  Nov  2 07:03:56 node1 kernel: [1941380.104003] RDX: eed8 RSI: 
eed8 RDI: a029ac80
  Nov  2 07:03:56 node1 kernel: [1941380.104003] RBP: 880ec7745da8 R08: 
18bb5554 R09: 18282e0518bb5554
  Nov  2 07:03:56 node1 kernel: [1941380.104003] R10: 6a81e9b4 R11: 
18282e0518bb5554 R12: 880ec7745d78
  Nov  2 07:03:56 node1 kernel: [1941380.104003] R13: 880ec784c200 R14: 
 R15: ee626da3
  Nov  2 07:03:56 node1 kernel: [1941380.104003] FS:  () 
GS:880f1fc0() knlGS:
  Nov  2 07:03:56 node1 kernel: [1941380.104003] CS:  0010 DS:  ES:  
CR0: 80050033
  Nov  2 07:03:56 node1 kernel: [1941380.104003] CR2: 7f554c039000 CR3: 
000ecbcd8000 CR4: 000406f0
  Nov  2 07:03:56 node1 kernel: [1941380.104003] Stack:
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  880ec7745de8 
a026d666 006c 880ec807e000
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  a02974d8 
88010317e018 88010317e000 001c
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  880ec7745e20 
a0261e12 880ec807e1e0 880ec807e000
  Nov  2 07:03:56 node1 kernel: [1941380.104003] Call Trace:
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd_cache_update+0x76/0x150 [nfsd]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd_dispatch+0x192/0x200 [nfsd]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
svc_process_common+0x46d/0x6d0 [sunrpc]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
svc_process+0x107/0x170 [sunrpc]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
nfsd+0xbf/0x130 [nfsd]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
nfsd_destroy+0x80/0x80 [nfsd]
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
kthread+0xd2/0xf0
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] 
ret_from_fork+0x7c/0xb0
  Nov  2 07:03:56 node1 kernel: [1941380.104003]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
- Nov  2 07:03:56 node1 kernel: [1941380.104003] Code: 89 e5 b8 00 00 02 00 f0 
0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 f2 b8 00 80 00 00 
eb 0c 0f 1f 44 00 00 f3 90 <83> e8 01 74 0a 0f b7 0f 66 39 ca 75 f1 5d c3 66 66 
66 90 66 66 
+ Nov  2 07:03:56 node1 kernel: [1941380.104003] Code: 89 e5 b8 00 00 02 00 f0 
0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 f2 b8 00 80 00 00 
eb 0c 0f 1f 44 00 00 f3 90 <83> e8 01 74 0a 0f b7 0f 66 39 ca 75 f1 5d c3 66 66 
66 90 66 66
  
  
  
  Nov  2 07:03:56 node1 kernel: [1941352.144608] CPU: 2 PID: 135 Comm: 
khugepaged Not tainted 3.13.0-37-generic #64-Ubuntu
  Nov  2 07:03:56 node1 kernel: [1941352.144608] Hardware name: Red Hat Inc. 
OpenStack Nova, BIOS 0.5.1 01/01/2007
  Nov  2 07:03:56 node1 kernel: [1941352.144608] task: 880ec97e6000 ti: 
880ec908 task.ti: 880ec908
  Nov  2 07:03:56 node1 kernel: [1941352.144608] RIP: 0010:[] 
 [] copy_page+0x23/0xe0
  Nov  2 07:03:56 node1 kernel: [1941352.144608] RSP: 0018:880ec9081d90  
EFLAGS: 00010206
  Nov  2 07:03:56 node1 kernel: [1941352.144608] RAX: 23ba7000 RBX: 
880ee3010c00 RCX: 003a
  Nov  2 07:03:56 node1 kernel: [1941352.144608] RDX: ffed RSI: 
880850

[Bug 1370069] Re: Unlock does not work

2014-09-26 Thread Sami Pietila
I am using 14.04 LTS. Is there a fix available for LTS I could test?

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

Title:
  Unlock does not work

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

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


[Bug 1373899] [NEW] Desktop does not work after suspend

2014-09-25 Thread Sami Pietila
Public bug reported:

Hi,

Desktop crashes after suspend. Following messages are shown on dmesg:

[ 1605.156075] nouveau E[Xorg[1319]] failed to idle channel 0x 
[Xorg[1319]]
[ 1605.156283] nouveau E[ PFB][:01:00.0] trapped read at 0x002001e020 
on channel 0x0001fb13 [unknown] SEMAPHORE_BG/PFIFO_READ/00 reason: 
PAGE_NOT_PRESENT
[ 1605.169373] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e020 
on channel 0x0001fb13 [unknown] PFIFO/PFIFO_READ/SEMAPHORE reason: 
PAGE_NOT_PRESENT
[ 1605.173958] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.174067] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.174175] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.174275] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.174435] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.174685] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.174791] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.174897] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.174999] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.175150] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.175393] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.175500] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.175605] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.175697] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.175887] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.176172] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.176286] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.176394] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.176495] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.176653] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.176897] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.177001] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.177108] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.177211] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.177361] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.177607] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.177708] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.177814] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.177907] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1605.178091] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fb13 [Xorg[1319]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1605.178336] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1605.178437] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1605.178543] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1605.178642] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fb13000 Xorg[1319]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1717.604024] nouveau E[Xorg[5367]] failed to idle channel 0x 
[Xorg[5367]]
[ 1717.604221] nouveau E[ PFB][:01:00.0] trapped read at 0x002001e020 
on channel 0x0001fc23 [unknown] SEMAPHORE_BG/PFIFO_READ/00 reason: 
PAGE_NOT_PRESENT
[ 1717.615926] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e020 
on channel 0x0001fc23 [unknown] PFIFO/PFIFO_READ/SEMAPHORE reason: 
PAGE_NOT_PRESENT
[ 1717.770986] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1717.771103] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 00304041 4360 
 06000432
[ 1717.771210] nouveau E[  PGRAPH][:01:00.0]  TRAP
[ 1717.771305] nouveau E[  PGRAPH][:01:00.0] ch 2 [0x001fc23000 Xorg[5367]] 
subc 0 class 0x5039 mthd 0x0328 data 0x
[ 1717.771466] nouveau E[ PFB][:01:00.0] trapped write at 0x002001e010 
on channel 0x0001fc23 [Xorg[5367]] PGRAPH/DISPATCH/M2M_NOTIFY reason: 
PAGE_NOT_PRESENT
[ 1717.771810] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF NOTIFY
[ 1717.771918] nouveau E[  PGRAPH][:01:00.0] TRAP_M2MF 0030

[Bug 1370069] Re: Unlock does not work

2014-09-19 Thread Sami Pietila
The machine has currently unity 7.2.2+14.04.20140714-0ubuntu1.1.  Is the
current version the latest? As far as I could see from dpkg.log there
has not been updates for unity since I reported the bug.

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

Title:
  Unlock does not work

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

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


[Bug 1370069] Re: Login does not work

2014-09-17 Thread Sami Pietila
Screenshot is attached.

Is there a work around that would allow login to desktop when this issue
occurs, perhaps entering some command to text console?

** Attachment added: "login.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370069/+attachment/4206273/+files/login.jpg

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

Title:
  Login does not work

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

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


[Bug 1370069] [NEW] Login does not work

2014-09-16 Thread Sami Pietila
Public bug reported:

After screen lock the login does not display a field where a password
can be typed and thus there seems to be no way to login to machine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Sep 16 16:53:05 2014
DistUpgraded: 2014-04-11 11:51:55,755 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Subsystem: Hewlett-Packard Company Device [103c:18e4]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:90b8]
InstallationDate: Installed on 2013-11-05 (315 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=ef4f067e-192b-4f3f-873d-bfb295641eec ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to trusty on 2014-04-11 (158 days ago)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.18
dmi.board.asset.tag: CZC3427KBP
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC3427KBP
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Sep  4 10:17:39 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug false-gpu-hang freeze trusty ubuntu

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

Title:
  Login does not work

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

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


[Bug 1369095] Re: BTRFS crash with Ubuntu Server 14.04 LTS (under openstack)

2014-09-15 Thread Sami Pietila
** Tags added: kernel-unable-to-test-upstream

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

Title:
  BTRFS crash with Ubuntu Server 14.04 LTS (under openstack)

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

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


[Bug 1369095] [NEW] BTRFS crash with Ubuntu Server 14.04 LTS (under openstack)

2014-09-13 Thread Sami Pietila
Public bug reported:

The root filesystem became mounted as rw dmesg showing following
messages:

[1759806.961342] btrfs: bdev /dev/vda1 errs: wr 1, rd 0, flush 0, corrupt 0, 
gen 0
[1759806.979607] btrfs: bdev /dev/vda1 errs: wr 2, rd 0, flush 0, corrupt 0, 
gen 0
[1759806.979771] btrfs: bdev /dev/vda1 errs: wr 3, rd 0, flush 0, corrupt 0, 
gen 0
[1759806.998053] btrfs: bdev /dev/vda1 errs: wr 4, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.037591] btrfs: bdev /dev/vda1 errs: wr 5, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.037704] btrfs: bdev /dev/vda1 errs: wr 6, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.037800] btrfs: bdev /dev/vda1 errs: wr 7, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.037894] btrfs: bdev /dev/vda1 errs: wr 8, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.037988] btrfs: bdev /dev/vda1 errs: wr 9, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.038081] btrfs: bdev /dev/vda1 errs: wr 10, rd 0, flush 0, corrupt 0, 
gen 0
[1759807.038452] BTRFS error (device vdb) in btrfs_commit_transaction:1884: 
errno=-5 IO failure (Error while writing out transaction)
[1759807.038624] BTRFS info (device vdb): forced readonly
[1759807.038628] BTRFS warning (device vdb): Skipping commit of aborted 
transaction.
[1759807.038631] [ cut here ]
[1759807.038671] WARNING: CPU: 3 PID: 177 at 
/build/buildd/linux-3.13.0/fs/btrfs/super.c:254 
__btrfs_abort_transaction+0x50/0x110 [btrfs]()
[1759807.038673] btrfs: Transaction aborted (error -5)
[1759807.038675] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
xfs crct10dif_pclmul crc32_pclmul cirrus ghash_clmulni_intel ttm aesni_intel 
drm_kms_helper aes_x86_64 lrw gf128mul drm glue_helper psmouse ablk_helper 
serio_raw cryptd joydev syscopyarea sysfillrect sysimgblt mac_hid i2c_piix4 
hid_generic usbhid hid btrfs xor raid6_pq libcrc32c floppy
[1759807.038712] CPU: 3 PID: 177 Comm: btrfs-transacti Not tainted 
3.13.0-32-generic #57-Ubuntu
[1759807.038715] Hardware name: Red Hat Inc. OpenStack Nova, BIOS 0.5.1 
01/01/2007
[1759807.038719]  0009 8803c60e1cc0 8171bcb4 
8803c60e1d08
[1759807.038725]  8803c60e1cf8 810676cd fffb 
8803c6009000
[1759807.038729]  8803ca33c000 a00e6e90 060b 
8803c60e1d58
[1759807.038734] Call Trace:
[1759807.038750]  [] dump_stack+0x45/0x56
[1759807.038759]  [] warn_slowpath_common+0x7d/0xa0
[1759807.038764]  [] warn_slowpath_fmt+0x4c/0x50
[1759807.038779]  [] __btrfs_abort_transaction+0x50/0x110 
[btrfs]
[1759807.038801]  [] cleanup_transaction+0x6e/0x290 [btrfs]
[1759807.038811]  [] ? prepare_to_wait_event+0x100/0x100
[1759807.038831]  [] btrfs_commit_transaction+0x6ea/0x970 
[btrfs]
[1759807.038849]  [] transaction_kthread+0x1b5/0x240 [btrfs]
[1759807.038866]  [] ? btrfs_cleanup_transaction+0x550/0x550 
[btrfs]
[1759807.038873]  [] kthread+0xd2/0xf0
[1759807.038878]  [] ? kthread_create_on_node+0x1d0/0x1d0
[1759807.03]  [] ret_from_fork+0x7c/0xb0
[1759807.038892]  [] ? kthread_create_on_node+0x1d0/0x1d0
[1759807.038896] ---[ end trace 122a578f827fe06a ]---
[1759807.038899] BTRFS error (device vdb) in cleanup_transaction:1547: errno=-5 
IO failure
[1759807.039003] delayed_refs has NO entry
[1759807.039049] [ cut here ]
[1759807.039071] WARNING: CPU: 3 PID: 177 at 
/build/buildd/linux-3.13.0/fs/btrfs/inode.c:4768 
btrfs_invalidate_inodes+0x1b6/0x1c0 [btrfs]()
[1759807.039073] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
xfs crct10dif_pclmul crc32_pclmul cirrus ghash_clmulni_intel ttm aesni_intel 
drm_kms_helper aes_x86_64 lrw gf128mul drm glue_helper psmouse ablk_helper 
serio_raw cryptd joydev syscopyarea sysfillrect sysimgblt mac_hid i2c_piix4 
hid_generic usbhid hid btrfs xor raid6_pq libcrc32c floppy
[1759807.039102] CPU: 3 PID: 177 Comm: btrfs-transacti Tainted: GW
3.13.0-32-generic #57-Ubuntu
[1759807.039104] Hardware name: Red Hat Inc. OpenStack Nova, BIOS 0.5.1 
01/01/2007
[1759807.039106]  0009 8803c60e1d78 8171bcb4 

[1759807.039111]  8803c60e1db0 810676cd 8803c600bcd8 
8803c600bcf0
[1759807.039115]  8803c60e1e30 8803c600b800 880036cc9e40 
8803c60e1dc0
[1759807.039120] Call Trace:
[1759807.039127]  [] dump_stack+0x45/0x56
[1759807.039132]  [] warn_slowpath_common+0x7d/0xa0
[1759807.039136]  [] warn_slowpath_null+0x1a/0x20
[1759807.039154]  [] btrfs_invalidate_inodes+0x1b6/0x1c0 
[btrfs]
[1759807.039178]  [] ? btrfs_first_delayed_node+0x34/0x50 
[btrfs]
[1759807.039195]  [] btrfs_cleanup_transaction+0x42f/0x550 
[btrfs]
[1759807.039211]  [] transaction_kthread+0x206/0x240 [btrfs]
[1759807.039227]  [] ? btrfs_cleanup_transaction+0x550/0x550 
[btrfs]
[1759807.039232]  [] kthread+0xd2/0xf0
[1759807.039236]  [] ? kthread_create_on_node+0x1d0/0x1d0
[1759807.039242]  [] ret_from_fork+0x7c/0xb0
[1759807.039246]  [] ? kthread_create_on_node+0x1d0/0x1d0
[1759807.039249] ---[ end trace 122a578f827fe06b ]---

[Bug 1359706] Re: EXT4 file system corruption on ubuntu server 14.04 LTS

2014-09-03 Thread Sami Pietila
So far, I have not been able to reproduce the crash again even with
exactly the same kernel.

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

Title:
  EXT4 file system corruption on ubuntu server 14.04 LTS

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

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


  1   2   3   >