[Touch-packages] [Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

2022-06-04 Thread Shuhao
Can confirm that removing the .service files in
/etc/systemd/system/systemd-suspend.service.requires works.

The reason this occurred to me is because i switched GPU from nvidia to
AMD, and some programs thought I have nvenc (because the library is
installed) when i don't, which necessitates the removal of the nvidia-
driver packages.

This seem like an issue with one of the nvidia package's postrm debian
package scripts as opposed to systemd, tho.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1933880

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a 
restart, run `sudo apt autoremove nvidia-driver-465`.
  2. Leaving the terminal open, suspend the machine.

  Expected behavior: the machine suspend successfully and can be woken up 
successfully.
  Actual behavior: the machine doesn't suspend. It either:
  - hang with no respond other than SysRq+REISUB (or maybe network, but I 
didn't test), or
  - return you back to the login screen. Upon logging in, you'll notice that 
the terminal you opened is gone.

  Upon further inspection (on a session that doesn't hang), it's been
  found that X server died with:

  Fatal server error:
  [66.422] (EE) systemd-logind disappeared (stopped/restarted?)

  And checking journal for systemd-logind log, it said:

  Error during inhibitor-delayed operation (already returned success to
  client): Unit nvidia-suspend.service is masked.

  before the new process takes it place.

  The system is Ubuntu 20.04, X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 03:34:00 2021
  InstallationDate: Installed on 2021-03-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1728560] Re: Cannot resolve smtp-mail.outlook.com

2017-12-04 Thread Shuhao
I found that disabling ipv6 dns helped (in thunderbird). Disabling ipv6
systemwide works as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728560

Title:
  Cannot resolve smtp-mail.outlook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, applications can no longer resolve smtp-
  mail.outlook.com, although host can:

  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com 25
  > telnet: could not resolve smtp-mail.outlook.com/25: Temporary failure in 
name resolution
  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com
  > telnet: could not resolve smtp-mail.outlook.com/telnet: Temporary failure 
in name resolution
  > mjg@payens:~/Projects/GNOME/geary$ host smtp-mail.outlook.com
  > smtp-mail.outlook.com is an alias for smtp.live.com.
  > smtp.live.com is an alias for smtp.glbdns2.microsoft.com.
  > smtp.glbdns2.microsoft.com is an alias for smtp.office365.com.
  > smtp.office365.com is an alias for smtp.outlook.office365.com.
  > smtp.outlook.office365.com is an alias for outlook.office365.com.
  > outlook.office365.com is an alias for lb.geo.office365.com.
  > lb.geo.office365.com is an alias for outlook.office365.com.g.office365.com.
  > outlook.office365.com.g.office365.com is an alias for 
outlook-au.office365.com.
  > outlook-au.office365.com has address 40.100.151.226
  > [many more replies snipped]

  Also reported on ask.ubuntu.com:
  https://askubuntu.com/questions/969689/dns-problem-trying-to-ping-or-
  send-email-using-smtp-mail-outlook-com-after-upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 21:07:17 2017
  InstallationDate: Installed on 2015-07-22 (831 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B18.1610241407
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B18.1610241407:bd10/24/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1728560] Re: Cannot resolve smtp-mail.outlook.com

2017-12-03 Thread Shuhao
I observe the same issue here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1731522

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728560

Title:
  Cannot resolve smtp-mail.outlook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, applications can no longer resolve smtp-
  mail.outlook.com, although host can:

  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com 25
  > telnet: could not resolve smtp-mail.outlook.com/25: Temporary failure in 
name resolution
  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com
  > telnet: could not resolve smtp-mail.outlook.com/telnet: Temporary failure 
in name resolution
  > mjg@payens:~/Projects/GNOME/geary$ host smtp-mail.outlook.com
  > smtp-mail.outlook.com is an alias for smtp.live.com.
  > smtp.live.com is an alias for smtp.glbdns2.microsoft.com.
  > smtp.glbdns2.microsoft.com is an alias for smtp.office365.com.
  > smtp.office365.com is an alias for smtp.outlook.office365.com.
  > smtp.outlook.office365.com is an alias for outlook.office365.com.
  > outlook.office365.com is an alias for lb.geo.office365.com.
  > lb.geo.office365.com is an alias for outlook.office365.com.g.office365.com.
  > outlook.office365.com.g.office365.com is an alias for 
outlook-au.office365.com.
  > outlook-au.office365.com has address 40.100.151.226
  > [many more replies snipped]

  Also reported on ask.ubuntu.com:
  https://askubuntu.com/questions/969689/dns-problem-trying-to-ping-or-
  send-email-using-smtp-mail-outlook-com-after-upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 21:07:17 2017
  InstallationDate: Installed on 2015-07-22 (831 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B18.1610241407
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B18.1610241407:bd10/24/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1731522] Re: Cannot ping pod51041.outlook.com but can dig.

2017-12-03 Thread Shuhao
This seems to be a duplicate of #1728560

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  Cannot ping pod51041.outlook.com but can dig.

Status in systemd package in Ubuntu:
  New

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1731522] Re: Cannot ping pod51041.outlook.com but can dig.

2017-11-27 Thread Shuhao
Additionally, I also looked at my nsswitch.conf file, the host line in
it is:

hosts:  files mdns4_minimal [NOTFOUND=return] dns.

I tried hosts: files dns, and all the combinations, but nothing works.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  Cannot ping pod51041.outlook.com but can dig.

Status in systemd package in Ubuntu:
  New

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1731522] Re: systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com

2017-11-27 Thread Shuhao
The bug report here is likely inaccurate. I don't exactly know where the
problem is.

I did some tcpdumps for port 53 traffic. I see that if I did a ping, it
requests for the A records of the domain name and indeed the IP
addresses are getting returned. However, weirdly, ping then requests for
the A records of pod51041.outlook.com.lan. .lan is the search domain on
my network as specified with /etc/resolv.conf automatically.

Furthermore, if I disable ipv6, thunderbird and firefox can access the
domain, but ping still cannot.

So I don't think this bug report should be filed against systemd, but I
don't really know where the problem lies.

** Description changed:

  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:
  
- $ nslookup   
- > host pod51041.outlook.com
- Server:   127.0.0.53
- Address:  127.0.0.53#53
- 
- ** server can't find host: SERVFAIL
- 
- 
- $ ping pod51041.outlook.com  
+ $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution
- 
  
  (Also can't access via thunderbird).
  
  However, it seems to work directly via systemd-resolve:
  
  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
-   40.97.126.50
-   132.245.38.194
-   40.97.147.194
-   132.245.41.34
-   40.97.176.2
-   40.97.150.242
-   40.97.85.114
-   40.97.120.50
-   40.97.85.2
-   40.97.176.34
-   40.97.138.242
-   40.97.166.18
-   40.97.120.162
-   40.97.119.82
-   40.97.176.18
-   40.97.85.98
-   40.97.134.34
-   40.97.84.18
+   40.97.126.50
+   132.245.38.194
+   40.97.147.194
+   132.245.41.34
+   40.97.176.2
+   40.97.150.242
+   40.97.85.114
+   40.97.120.50
+   40.97.85.2
+   40.97.176.34
+   40.97.138.242
+   40.97.166.18
+   40.97.120.162
+   40.97.119.82
+   40.97.176.18
+   40.97.85.98
+   40.97.134.34
+   40.97.84.18
  
  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no
+ 
+ It also works with dig and nslookup.
  
  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

** Summary changed:

- systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com
+ Cannot ping pod51041.outlook.com but can dig.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  Cannot ping pod51041.outlook.com but can dig.

Status in systemd package in Ubuntu:
  New

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51

[Touch-packages] [Bug 1731524] [NEW] mate panel freezes when clicking on fcitx icon in the notification area while having a text field selected

2017-11-10 Thread Shuhao
Public bug reported:

FCITX is enabled by default on Ubuntu Mate. If you click on a textbox,
the notification area will show a keyboard icon with the label "us"
beside it.

When you click on that icon at this moment, a blank menu will pop up and
the entire desktop environment freezes until you switch to tty1 and do
killall mate-panel.

If the us label is not beside the keyboard icon for fcitx (anytime when
you don't have a text field focused), clicking on the icon shows the
regular fcitx menu as normal.

** Affects: mate-desktop (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: systemd (Ubuntu) => mate-desktop (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731524

Title:
  mate panel freezes when clicking on fcitx icon in the notification
  area while having a text field selected

Status in mate-desktop package in Ubuntu:
  New

Bug description:
  FCITX is enabled by default on Ubuntu Mate. If you click on a textbox,
  the notification area will show a keyboard icon with the label "us"
  beside it.

  When you click on that icon at this moment, a blank menu will pop up
  and the entire desktop environment freezes until you switch to tty1
  and do killall mate-panel.

  If the us label is not beside the keyboard icon for fcitx (anytime
  when you don't have a text field focused), clicking on the icon shows
  the regular fcitx menu as normal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1731522] [NEW] systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com

2017-11-10 Thread Shuhao
Public bug reported:

Trying to resolve pod51041.outlook.com's domain name seems to fail for
applications:

$ nslookup   
> host pod51041.outlook.com
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find host: SERVFAIL


$ ping pod51041.outlook.com  
ping: pod51041.outlook.com: Temporary failure in name resolution


(Also can't access via thunderbird).

However, it seems to work directly via systemd-resolve:

$ systemd-resolve pod51041.outlook.com
pod51041.outlook.com: 40.97.160.2
  40.97.126.50
  132.245.38.194
  40.97.147.194
  132.245.41.34
  40.97.176.2
  40.97.150.242
  40.97.85.114
  40.97.120.50
  40.97.85.2
  40.97.176.34
  40.97.138.242
  40.97.166.18
  40.97.120.162
  40.97.119.82
  40.97.176.18
  40.97.85.98
  40.97.134.34
  40.97.84.18

-- Information acquired via protocol DNS in 2.5ms.
-- Data is authenticated: no

Not quite sure why this is the case, I've spotted this issue upstream
that looks similar: https://github.com/systemd/systemd/issues/6520.
However, I'm not familiar enough with DNS to tell if it is the same
issue.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Nov 10 13:10:02 2017
InstallationDate: Installed on 2017-11-10 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
MachineType: LENOVO 2324BB9
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA6WW (2.66 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324BB9
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2324BB9
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  systemd-resolved sends SERVFAIL to host/nslookup for
  pod51041.outlook.com

Status in systemd package in Ubuntu:
  New

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ nslookup   
  > host pod51041.outlook.com
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find host: SERVFAIL

  
  $ ping pod51041.outlook.com  
  ping: pod51041.outlook.com: Temporary failure in name resolution

  
  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
40.97.126.50
132.245.38.194
40.97.147.194
132.245.41.34
40.97.176.2
40.97.150.242
40.97.85.114
40.97.120.50
40.97.85.2
40.97.176.34
40.97.138.242
40.97.166.18
40.97.120.162
40.97.119.82
40.97.176.18
40.97.85.98
40.97.134.34
40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

2016-03-23 Thread Shuhao
If I have my own ppa, do I need to do anything? It's not 100% clear in
this thread.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1558331

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  The title pretty much says it all.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1486456] Re: Please set back libvpx1 into Wily archive

2015-10-13 Thread Shuhao
I think this is an oracle fault, no? They should probably be depending
on libvpx1 > 1.0.0 | libvpx2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1486456

Title:
  Please set back libvpx1 into Wily archive

Status in libvpx package in Ubuntu:
  Confirmed

Bug description:
  Wanting to install virtualbox 5.0 from  virtualbox.org, as the wily
  archive one (5.02-dfsg-2) has a vboxpci iommu issue.

  but i require libvpx1 to install (and no more available into Wily archive)
  https://launchpad.net/ubuntu/+source/libvpx

  virtualbox-5.0:
   Depends: libvpx1 (>=1.0.0) but it is not installable

  Error with the Wily package:
  dmesg | grep -i iommu
  [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on
  [0.00] DMAR: IOMMU enabled
  [   32.662814] vboxpci: IOMMU not found (not registered)

  (this is a test with intel_iommu=on kernel parameter, but without i
  get the same result. So i need the version from virtualbox.org)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-11-28 Thread Shuhao
I just got like 2 50GB log files in /tmp and in
~/.cache/upstart/startxfce4.log with this message. It filled my entire
drive.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1369113

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in steam package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.

[Touch-packages] [Bug 1351590] Re: Cannot configure wi-fi in a live-session without logging out and back in again

2014-10-17 Thread Shuhao
So the proper way to attempt to reproduce this bug is to get a live disk
and see if the wifi works on the first try? I can try this on 14.10 beta
2 sometime today.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1351590

Title:
  Cannot configure wi-fi in a live-session without logging out and back
  in again

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I am using the daily build 20140802 of Xubuntu in a live session and
  cannot setup a wi-fi connection as I am told I do not have the
  authority. See attached screenshot of error.

  If I log out and then back in again I can setup wifi without a
  problem.

  I first saw this problem with 20140801 but did not report it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340build1
  CurrentDesktop: XFCE
  Date: Sat Aug  2 10:41:23 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.10  metric 
9
  LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140802)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0   
802-11-wireless   1406976080   Sat 02 Aug 2014 10:41:20 AM UTCyes   
no /org/freedesktop/NetworkManager/Settings/1
   Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de   
802-3-ethernet1406975781   Sat 02 Aug 2014 10:36:21 AM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp