[Bug 2065678] Re: nvidia-graphics-drivers-545 package fails to launch graphical session with latest linux 5.15.0-107 update

[Msd]

I bypass the problem by installing manually the 550 version : `apt
install nvidia-driver-550` after checking that my GPU is supported here
: https://www.nvidia.com/fr-fr/geforce/drivers/. Works fine for now.

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

Title:
  nvidia-graphics-drivers-545 package fails to launch graphical session
  with latest linux 5.15.0-107 update

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


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

[Bug 2065678] Re: nvidia-graphics-drivers-545 package fails to launch graphical session with latest linux 5.15.0-107 update

[Msd]

Today I have got an update of "nvidia-dkms-545
(545.29.06-0ubuntu0.22.04.2)", but it fails with "ERROR: modpost: GPL-
incompatible module nvidia.ko uses GPL-only symbol
'rcu_read_unlock_strict'" :

$ sudo apt upgrade 
[...]
Good news! Module version 545.29.06 for nvidia-peermem.ko
exactly matches what is already found in kernel 5.15.0-105-generic.
DKMS will not replace this module.
You may override by specifying --force.

depmod...
Building initial module for 5.15.0-107-generic
Error! Bad return status for module build on kernel: 5.15.0-107-generic (x86_64)
Consult /var/lib/dkms/nvidia/545.29.06/build/make.log for more information.
dpkg: erreur de traitement du paquet nvidia-dkms-545 (--configure) :
 le sous-processus paquet nvidia-dkms-545 script post-installation installé a 
renvoyé un état de sortie d'erreur 10
Paramétrage de python3-idna (3.3-1ubuntu0.1) ...
Traitement des actions différées (« triggers ») pour initramfs-tools 
(0.140ubuntu13.4) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-107-generic
Des erreurs ont été rencontrées pendant l'exécution :
 nvidia-dkms-545
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ tail /var/lib/dkms/nvidia/545.29.06/build/make.log
  {   echo /var/lib/dkms/nvidia/545.29.06/build/nvidia.ko;   echo 
/var/lib/dkms/nvidia/545.29.06/build/nvidia-uvm.ko;   echo 
/var/lib/dkms/nvidia/545.29.06/build/nvidia-modeset.ko;   echo 
/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm.ko;   echo 
/var/lib/dkms/nvidia/545.29.06/build/nvidia-peermem.ko; :; } | awk '!x[$0]++' - 
> /var/lib/dkms/nvidia/545.29.06/build/modules.order
sh ./scripts/modules-check.sh /var/lib/dkms/nvidia/545.29.06/build/modules.order
make -f ./scripts/Makefile.modpost
  sed 's/\.ko$/\.o/' /var/lib/dkms/nvidia/545.29.06/build/modules.order | 
scripts/mod/modpost -m -a  -o 
/var/lib/dkms/nvidia/545.29.06/build/Module.symvers -e -i Module.symvers   -T -
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'rcu_read_unlock_strict'
make[2]: *** [scripts/Makefile.modpost:133 : 
/var/lib/dkms/nvidia/545.29.06/build/Module.symvers] Erreur 1
make[2]: *** Suppression du fichier « 
/var/lib/dkms/nvidia/545.29.06/build/Module.symvers »
make[1]: *** [Makefile:1830 : modules] Erreur 2
make[1] : on quitte le répertoire « /usr/src/linux-headers-5.15.0-107-generic »
make: *** [Makefile:82 : modules] Erreur 2

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

Title:
  nvidia-graphics-drivers-545 package fails to launch graphical session
  with latest linux 5.15.0-107 update

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


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

[Bug 2065678] [NEW] nvidia-graphics-drivers-545 package fails to launch graphical session with latest linux 5.15.0-107 update

[Msd]

Public bug reported:

No graphical session can't be launched after the update to linux
5.15.0-106 and then linux 5.15.0-107 today with nvidia-graphics-
drivers-545 installed.

I can see this problem in syslog :

```
lightdm[2367]: modprobe: FATAL: Module nvidia not found in directory 
/lib/modules/5.15.0-107-generic
```

We can see there is no linux-modules-nvidia-545-5.15.0-107-generic :

```
$ apt-cache rdepends linux-signatures-nvidia-5.15.0-107-generic
linux-signatures-nvidia-5.15.0-107-generic
Reverse Depends:
  linux-modules-nvidia-390-5.15.0-107-generic
  linux-modules-nvidia-550-server-5.15.0-107-generic
  linux-modules-nvidia-550-5.15.0-107-generic
  linux-modules-nvidia-535-server-5.15.0-107-generic
  linux-modules-nvidia-535-5.15.0-107-generic
  linux-modules-nvidia-470-server-5.15.0-107-generic
  linux-modules-nvidia-470-5.15.0-107-generic
  linux-modules-nvidia-450-server-5.15.0-107-generic
```

We can see there is a linux-modules-nvidia-545-5.15.0-105-generic :

```
$ apt-cache rdepends linux-signatures-nvidia-5.15.0-105-generic
linux-signatures-nvidia-5.15.0-105-generic
Reverse Depends:
  linux-modules-nvidia-390-5.15.0-105-generic
  linux-modules-nvidia-550-server-5.15.0-105-generic
  linux-modules-nvidia-550-5.15.0-105-generic
  linux-modules-nvidia-545-5.15.0-105-generic
  linux-modules-nvidia-535-server-5.15.0-105-generic
  linux-modules-nvidia-535-5.15.0-105-generic
  linux-modules-nvidia-470-server-5.15.0-105-generic
  linux-modules-nvidia-470-5.15.0-105-generic
  linux-modules-nvidia-450-server-5.15.0-105-generic

$ du -h -d1 -x /lib/modules | sort -h
[...]
458M/lib/modules/5.15.0-107-generic
871M/lib/modules/5.15.0-105-generic
1,4G/lib/modules
```

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

** Description changed:

  No graphical session can't be launched after the update to linux
  5.15.0-106 and then linux 5.15.0-107 today with nvidia-graphics-
  drivers-545 installed.
  
  I can see this problem in syslog :
- 
  
  ```
  lightdm[2367]: modprobe: FATAL: Module nvidia not found in directory 
/lib/modules/5.15.0-107-generic
  ```
  
  We can see there is no linux-modules-nvidia-545-5.15.0-107-generic :
  
- 
  ```
  $ apt-cache rdepends linux-signatures-nvidia-5.15.0-107-generic
  linux-signatures-nvidia-5.15.0-107-generic
  Reverse Depends:
-   linux-modules-nvidia-390-5.15.0-107-generic
-   linux-modules-nvidia-550-server-5.15.0-107-generic
-   linux-modules-nvidia-550-5.15.0-107-generic
-   linux-modules-nvidia-535-server-5.15.0-107-generic
-   linux-modules-nvidia-535-5.15.0-107-generic
-   linux-modules-nvidia-470-server-5.15.0-107-generic
-   linux-modules-nvidia-470-5.15.0-107-generic
-   linux-modules-nvidia-450-server-5.15.0-107-generic
+   linux-modules-nvidia-390-5.15.0-107-generic
+   linux-modules-nvidia-550-server-5.15.0-107-generic
+   linux-modules-nvidia-550-5.15.0-107-generic
+   linux-modules-nvidia-535-server-5.15.0-107-generic
+   linux-modules-nvidia-535-5.15.0-107-generic
+   linux-modules-nvidia-470-server-5.15.0-107-generic
+   linux-modules-nvidia-470-5.15.0-107-generic
+   linux-modules-nvidia-450-server-5.15.0-107-generic
  ```
  
- We can see there is no linux-modules-nvidia-545-5.15.0-107-generic :
+ We can see there is a linux-modules-nvidia-545-5.15.0-105-generic :
  
- 
- ```  
+ ```
  $ apt-cache rdepends linux-signatures-nvidia-5.15.0-105-generic
  linux-signatures-nvidia-5.15.0-105-generic
  Reverse Depends:
-   linux-modules-nvidia-390-5.15.0-105-generic
-   linux-modules-nvidia-550-server-5.15.0-105-generic
-   linux-modules-nvidia-550-5.15.0-105-generic
-   linux-modules-nvidia-545-5.15.0-105-generic
-   linux-modules-nvidia-535-server-5.15.0-105-generic
-   linux-modules-nvidia-535-5.15.0-105-generic
-   linux-modules-nvidia-470-server-5.15.0-105-generic
-   linux-modules-nvidia-470-5.15.0-105-generic
-   linux-modules-nvidia-450-server-5.15.0-105-generic
+   linux-modules-nvidia-390-5.15.0-105-generic
+   linux-modules-nvidia-550-server-5.15.0-105-generic
+   linux-modules-nvidia-550-5.15.0-105-generic
+   linux-modules-nvidia-545-5.15.0-105-generic
+   linux-modules-nvidia-535-server-5.15.0-105-generic
+   linux-modules-nvidia-535-5.15.0-105-generic
+   linux-modules-nvidia-470-server-5.15.0-105-generic
+   linux-modules-nvidia-470-5.15.0-105-generic
+   linux-modules-nvidia-450-server-5.15.0-105-generic
  
  $ du -h -d1 -x /lib/modules | sort -h
  [...]
  458M  /lib/modules/5.15.0-107-generic
  871M  /lib/modules/5.15.0-105-generic
  1,4G  /lib/modules
  ```

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

Title:
  nvidia-graphics-drivers-545 package fails to launch graphical session
  with latest linux 5.15.0-107 update

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


-- 

[Bug 1932332] acpidump.txt

[Msd]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522532/+files/acpidump.txt

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

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

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] WifiSyslog.txt

[Msd]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522531/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] UdevDb.txt

[Msd]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1932332/+attachment/5522526/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] ProcModules.txt

[Msd]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522524/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] RfKill.txt

[Msd]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1932332/+attachment/5522525/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] ProcInterrupts.txt

[Msd]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522523/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] ProcCpuinfoMinimal.txt

[Msd]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522522/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] Lsusb-v.txt

[Msd]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522521/+files/Lsusb-v.txt

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

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] Lspci-vt.txt

[Msd]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522519/+files/Lspci-vt.txt

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

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] Lsusb-t.txt

[Msd]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522520/+files/Lsusb-t.txt

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

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] Lspci.txt

[Msd]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1932332/+attachment/5522518/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] IwConfig.txt

[Msd]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522517/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] CurrentDmesg.txt

[Msd]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1932332/+attachment/5522516/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] CRDA.txt

[Msd]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1932332/+attachment/5522515/+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/1932332

Title:
  [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after
  closing the pivotal laptop screen

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


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

[Bug 1932332] Re: [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after closing the pivotal laptop screen

[Msd]

apport information

** Tags added: apport-collected focal

** Description changed:

  A friend of mine has a TOSHIBA SATELLITE C55-C and I installed xUbuntu
  20.04 LTS.
  
  I have a minor problem linked to a major problem :
  
  - Minor problem : it is impossible to adjust the light of the screen.
  
  - Major problem : when closing the laptop screen and opening it again,
  the light of the screen stay off and it is impossible to turn it on
  again.
  
  Can you help me ?
  
  Detail behaviour without changing anything
  -
  
  I discovered that the keyboard button controls the
  `/sys/class/backlight/intel_backlight/brightness` and modifying the
  light value with keyboard button or directly by 'echo $INT_VALUE >
  /sys/class/backlight/intel_backlight/brightness' do the same thing.
  
  You can change screen light value with the light keyboard buttons, but
  it does not change anything. The only thing that change is that if you
  set the light to '0', then the screen light is off. And when you put a
  value more than '0' then the screen light is full luminosity ('1' is the
  same effect as '1000').
  
  
  Not working solutions
  -
  
  I have tried a lot of things hoping for a solving solution :
  
  In `/etc/default/grub`, I have tried without success : 
  - GRUB_CMDLINE_LINUX='acpi_backlight=vendor'
  - GRUB_CMDLINE_LINUX='acpi_backlight=vendor acpi_osi=linux'
  - GRUB_CMDLINE_LINUX='acpi_backlight=video'
  - GRUB_CMDLINE_LINUX='video.disable_backlight_sysfs_if=1'
  - GRUB_CMDLINE_LINUX='video.brightness_switch_enabled=0'
  - GRUB_CMDLINE_LINUX='pcie_aspm=force acpi_osi=Linux acpi_backlight=legacy'
  
  I have read :
  
  - https://askubuntu.com/a/1311344
  - https://askubuntu.com/questions/1034305/brightness-problem-ubuntu-18-04-lts
  - https://bbs.archlinux.org/viewtopic.php?id=195967=2
  - 
https://askubuntu.com/questions/451165/toshiba-satellite-p850-fn-keys-not-working
  - https://wiki.archlinux.org/index.php/Backlight
  - https://bugzilla.redhat.com/show_bug.cgi?id=1126159
  
  Not acceptable solution : 'acpi=off'
  
  
  The only solution I have found "working" is to set
  "GRUB_CMDLINE_LINUX='acpi=off'".
  
  That way, when closing the laptop screen : the light goes off. And when
  opening the laptop screen : the light goes on (max value).
  
  In this configuration, it is impossible to adjust the screen light by
  modifying /sys/class/backlight/intel_backlight/brightness.
  
  For example : 'echo 0 > /sys/class/backlight/intel_backlight/brightness'
  let the screen light on.
  
  I thought it was an acceptable behaviour, until I saw a major problem.
  
  The computer is slower than before, because only 1 CPU (instead of 4) is
  detected.
  
  So I can't stay with that configuration.
  
  
  Computer specifications
  ---
  
  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.
  49 structures occupying 2491 bytes.
  Table at 0x000E6EE0.
  
  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: INSYDE Corp.
Version: 5.20
Release Date: 09/15/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 3072 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 5.20
Firmware Revision: 5.0
  
  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: TOSHIBA
Product Name: SATELLITE C55-C
Version: PSCP6E-01F03HFR
Serial Number: YF176764C
UUID: 0a28c286-2265-8c43-896c-6b968f92ea27
Wake-up Type: Power Switch
SKU Number: PSCP6E
Family: Type1 - Family
  
  Handle 0x0002, DMI type 2, 17 bytes
  Base Board Information
Manufacturer: FF50
Product Name: 06F5
Version: Type2 - Board Version
Serial Number: QC020RBF4601368
Asset Tag: 
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Type2 - Board Chassis Location
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
  
  Handle 0x0003, DMI type 3, 25 bytes
  

[Bug 1932332] [NEW] [TOSHIBA SATELLITE C55-C] Black screen (light screen off) after closing the pivotal laptop screen

[Msd]

Public bug reported:

A friend of mine has a TOSHIBA SATELLITE C55-C and I installed xUbuntu
20.04 LTS.

I have a minor problem linked to a major problem :

- Minor problem : it is impossible to adjust the light of the screen.

- Major problem : when closing the laptop screen and opening it again,
the light of the screen stay off and it is impossible to turn it on
again.

Can you help me ?

Detail behaviour without changing anything
-

I discovered that the keyboard button controls the
`/sys/class/backlight/intel_backlight/brightness` and modifying the
light value with keyboard button or directly by 'echo $INT_VALUE >
/sys/class/backlight/intel_backlight/brightness' do the same thing.

You can change screen light value with the light keyboard buttons, but
it does not change anything. The only thing that change is that if you
set the light to '0', then the screen light is off. And when you put a
value more than '0' then the screen light is full luminosity ('1' is the
same effect as '1000').


Not working solutions
-

I have tried a lot of things hoping for a solving solution :

In `/etc/default/grub`, I have tried without success : 
- GRUB_CMDLINE_LINUX='acpi_backlight=vendor'
- GRUB_CMDLINE_LINUX='acpi_backlight=vendor acpi_osi=linux'
- GRUB_CMDLINE_LINUX='acpi_backlight=video'
- GRUB_CMDLINE_LINUX='video.disable_backlight_sysfs_if=1'
- GRUB_CMDLINE_LINUX='video.brightness_switch_enabled=0'
- GRUB_CMDLINE_LINUX='pcie_aspm=force acpi_osi=Linux acpi_backlight=legacy'

I have read :

- https://askubuntu.com/a/1311344
- https://askubuntu.com/questions/1034305/brightness-problem-ubuntu-18-04-lts
- https://bbs.archlinux.org/viewtopic.php?id=195967=2
- 
https://askubuntu.com/questions/451165/toshiba-satellite-p850-fn-keys-not-working
- https://wiki.archlinux.org/index.php/Backlight
- https://bugzilla.redhat.com/show_bug.cgi?id=1126159

Not acceptable solution : 'acpi=off'


The only solution I have found "working" is to set
"GRUB_CMDLINE_LINUX='acpi=off'".

That way, when closing the laptop screen : the light goes off. And when
opening the laptop screen : the light goes on (max value).

In this configuration, it is impossible to adjust the screen light by
modifying /sys/class/backlight/intel_backlight/brightness.

For example : 'echo 0 > /sys/class/backlight/intel_backlight/brightness'
let the screen light on.

I thought it was an acceptable behaviour, until I saw a major problem.

The computer is slower than before, because only 1 CPU (instead of 4) is
detected.

So I can't stay with that configuration.


Computer specifications
---

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
49 structures occupying 2491 bytes.
Table at 0x000E6EE0.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: INSYDE Corp.
Version: 5.20
Release Date: 09/15/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 3072 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 5.20
Firmware Revision: 5.0

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: TOSHIBA
Product Name: SATELLITE C55-C
Version: PSCP6E-01F03HFR
Serial Number: YF176764C
UUID: 0a28c286-2265-8c43-896c-6b968f92ea27
Wake-up Type: Power Switch
SKU Number: PSCP6E
Family: Type1 - Family

Handle 0x0002, DMI type 2, 17 bytes
Base Board Information
Manufacturer: FF50
Product Name: 06F5
Version: Type2 - Board Version
Serial Number: QC020RBF4601368
Asset Tag: 
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Type2 - Board Chassis Location
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

Handle 0x0003, DMI type 3, 25 bytes
Chassis Information
Manufacturer: OEM Chassis ManuFacturer
Type: Notebook
Lock: Not Present
Version: OEM Chassis Version 
Serial Number: OEM Chassis Serial Number   
Asset Tag: No 

[Bug 1932179] [NEW] Crash with nvidia-drivers-460 when plug-in a second screen on the HDMI port

[Msd]

Public bug reported:

Hello,

I can boot with a dual screen : one on the DVI port and the second on
the HDMI port.

Then, if I unplug the HDMI screen, everything goes normal : the last
screen is the unique screen and the display act as expected.

But, if I try to plug again the HDMI screen, the display become black
and I can't do anything. I have to switch off the electricity to the
computer (unpluging the HDMI screen does not work).

Here last syslog lines :

juin 16 16:26:27 PaRaZiTe kernel: NVRM: GPU at PCI::01:00: 
GPU-22339841-e926-4ad6-27c9-a01a1812bf44
juin 16 16:26:27 PaRaZiTe kernel: NVRM: Xid (PCI::01:00): 8, pid=1787, 
Channel 0010
juin 16 16:26:38 PaRaZiTe kernel: nvidia-modeset: WARNING: GPU:0: Unable to 
read EDID for display device HDMI-0
juin 16 16:26:57 PaRaZiTe kernel: NVRM: Xid (PCI::01:00): 62, pid=1787, 
0a99(17d8)  
juin 16 16:26:58 PaRaZiTe kernel: NVRM: Xid (PCI::01:00): 32, pid=1092, 
Channel ID 0008 intr 80846000
juin 16 16:26:58 PaRaZiTe kernel: NVRM: Xid (PCI::01:00): 32, pid=1092, 
Channel ID 0008 intr1 0001 HCE_DBG0 0008 HCE_DBG1 

CPU : AMD Phenom(tm) II X4 955 Processor
GPU : NVIDIA GeForce GTX 970

How can I help more ?

** Affects: nvidia-graphics-drivers-460 (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/1932179

Title:
  Crash with nvidia-drivers-460 when plug-in a second screen on the HDMI
  port

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

https://marc.info/?l=postfix-users=157746682807997=mbox

>> It works fine with `milter_protocol = 6`.
> 
> Which is the default value.
> 
> Milter protocols versions < 6 don't support the SMFIP_HDR_LEADSPC
> feature. This feature was introduced with Sendmail 8.14, and is
> needed to correctly preserve the leading whitespace of a header
> field value.
> 
>   Wietse

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

> * Note that you are folding the line not immediately after ‘Subject:’,
>   there is a trailing space character.

I think it is normal because I want a space when the header is unfolded
between "Subject:" and
"Folding_White_Space_and_too_long_subject_aaa...".

> Unfolding is accomplished by simply removing any CRLF
> that is immediately followed by WSP. 

Thanks again.

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

** Attachment removed: "test.eml"
   
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1857618/+attachment/5315537/+files/test.eml

** Attachment added: "test.eml"
   
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1857618/+attachment/5315856/+files/test.eml

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

> * One other thing I see (don’t think it’s relevant here):
> milter_protocol = 2
> Do not set this! This setting is obsolete, it can only hurt. Always
> use the latest milter protocol, 6 (the default setting).

I don't know why, but changing to `milter_protocol = 6` solves the
problem.

The e-mail is well DKIM-signed.

Thanks !

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

Hello David,

Thank you for your quick reply.

I attached a php script (bug_21857618.php) to reproduce the issue.

You can run it with `php bug_21857618.php t...@example.com 0` to have an 
invalid DKIM signature.
You can run it with `php bug_21857618.php t...@example.com 1` to have valid 
DKIM signature.

Just replace t...@example.com by a valid DKIM-signed domain.

Look at the way "Suject:" is written in both cases.

Here is my opendkim conf file :

```
# cat /etc/opendkim.conf
Syslog  yes
LogResults  yes
LogWhy  yes
UMask   007
Socket  local:/var/run/opendkim/opendkim.sock
PidFile /var/run/opendkim/opendkim.pid
OversignHeaders From
TrustAnchorFile /usr/share/dns/root.key
UserID  opendkim
KeyTable/etc/mail/KeyTable
SigningTable/etc/mail/SigningTable
Modes
SubDomains  yes
MultipleSignatures  yes
InternalHosts   refile:/etc/mail/InternalHosts
Socket  inet:8891@localhost
```

I tried the php script on a Debian 8 server with this simplified config
file and the problem is already here :

```
# cat /etc/opendkim.conf
Syslog  yes
UMask   002
KeyTable/etc/mail/KeyTable
SigningTable/etc/mail/SigningTable
OversignHeaders From
```

If you can't reproduce the case, I'm interesting that you send me a
valid DKIM-signed email with the folded "Subject:" header.

---

> Perhaps some other component at your site or in transit is altering the
folding or line terminators? Anything unusual about your system and
configuration? 

I tried on multiples servers (Ubuntu 18.04, Ubuntu 16.04, Debian 8) and
the problem is here.

> Perhaps try setting Canonicalization to ‘relaxed/relaxed’
and see if the verification result changes

I haven't tried this but I only change a little bit the "Subject:"
header for one time having a valid DKIM signature and the other an
invalid signature. I don't think that this will solve the issue or if so
I don't understand why.

Thank you again for your reply and your tests to reproduce the problem,


Guillaume

```
# dpkg -l | grep opendkim
ii  libopendkim11 2.11.0~alpha-11build1 
  amd64Library for signing and verifying DomainKeys Identified 
Mail signatures
ii  opendkim  2.11.0~alpha-11build1 
  amd64Milter implementation of DomainKeys Identified Mail
# dpkg -l | grep postfix
ii  postfix   3.3.0-1ubuntu0.2  
  amd64High-performance mail transport agent
# dpkg -l |grep php-cli
ii  php-cli   1:7.2+60ubuntu1   
  all  command-line interpreter for the PHP scripting language 
(default)
# cat /etc/postfix/main.cf | grep milter
milter_default_action = accept
milter_protocol = 2
smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891
```

** Attachment added: "bug_21857618.php"
   
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1857618/+attachment/5315817/+files/bug_21857618.php

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] Re: opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

** Attachment added: "test.eml"
   
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1857618/+attachment/5315537/+files/test.eml

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

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1857618] [NEW] opendkim generate an invalid signature if one header is fold just after the header name

[Msd]

Public bug reported:

opendkim generate an invalid signature if one header is fold just after
the header name

Expected : the email is well signed.

Actual : Signature is invalid.

How to reproduce ? Send the email just below by replacing "example.com"
by a valid DKIM-signed domain. I used postfix to send the email.

Here is a source .eml email that will fail to be correctly signed by
opendkim :

```
From: 
To: 
Subject: 
 
Folding_White_Space_and_too_long_subject_a

Test
```

opendkim generate an invalid signature with this email because of the
"Subject:" folding white space.

The signature is valid if the "Subject:" is written in one line :

```
Subject: 
Folding_White_Space_and_too_long_subject_a
```

Ubuntu 18.04.3 LTS
opendkim : 2.11.0~alpha-11build1

---

This bug occurs for all headers signed by opendkim (not only with
"Subject:").

This syntax seems valid. At least Gmail, Outlook, Thunderbird display
the subject correctly.

https://www.ietf.org/rfc/rfc5322.txt :

> Unfolding is accomplished by simply removing any CRLF
>that is immediately followed by WSP.  Each header field should be
>treated in its unfolded form for further syntactic and semantic
>evaluation.  An unfolded header field has no length restriction and
>therefore may be indeterminately long.

Gmail and opendkim itself consider the signature as invalid.

opendkim :

```
Authentication-Results: xxx.example.com (amavisd-new); dkim=fail (2048-bit key)
reason="fail (message has been altered)" header.d=example.com
header.b=ABCDEF; 
```

Gmail:

```
ARC-Authentication-Results: i=1; mx.google.com;
   dkim=fail header.i=@example.com header.s=xxx header.b="a/aa";
```

** Affects: opendkim (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/1857618

Title:
  opendkim generate an invalid signature if one header is fold just
  after the header name

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

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

[Bug 1837076] [NEW] RepeatedMsgReduction should be off by default

[Msd]

Public bug reported:

Maintainers explains that this option should be off :
https://www.rsyslog.com/doc/master/configuration/action/rsconf1_repeatedmsgreduction.html

> This parameter models old sysklogd legacy. Note that many people, including 
> the rsyslog authors, consider this to be a misfeature. [...]
> - While turning this feature on can save some space in logs, most log 
> analysis tools need to see the repeated messages, they can’t handle the “last 
> message repeated” format.
> - This is a feature that worked decades ago when logs were small and reviewed 
> by a human, it fails badly on high volume logs processed by tools. [...]
> This turns on repeated message reduction (not recommended):
> `$RepeatedMsgReduction on# do not log repeated messages`

So I think this option should be off by default in Ubuntu.

This option is Off in Debian 10.

Is there a reason why this is option is on on Ubuntu ?

** Affects: rsyslog (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/1837076

Title:
  RepeatedMsgReduction should be off by default

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

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

[Bug 1830213] [NEW] Count for result is wrong when joining and outputting from only 1 table

[Msd]

Public bug reported:

This bug is still in phpmyadmin 4:4.5.4.1-2ubuntu2.1 in Ubuntu 16.04
xenial :

https://github.com/phpmyadmin/phpmyadmin/issues/12189

Upstream correction is here :

https://github.com/phpmyadmin/phpmyadmin/commit/4fb7d734016c90f49299ce9724f486058b81cdad

Description:Ubuntu 16.04.6 LTS
Release:16.04

** Affects: phpmyadmin (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/1830213

Title:
  Count for result is wrong when joining and outputting from only 1
  table

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

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

[Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

[Msd]

I can confirm that the kernel 3.13.0-159-generic from trusty-proposed
solves the problem.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

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

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

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

I have contacted the postfix-users mailing list.

This is a known and corrected bug as you can see here :

http://article.gmane.org/gmane.mail.postfix.user/254717
http://www.postfix.org/announcements/postfix-2.11.1.html

But it seems it isn't the case on Ubuntu 14.04 LTS.

Can it be corrected ?

Thank you for your help !

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

Title:
  In some rare cases Postfix connect to a wrong MX server

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

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

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

I have contacted the postfix-users mailing list.

This is a known and corrected bug as you can see here :

http://article.gmane.org/gmane.mail.postfix.user/254717
http://www.postfix.org/announcements/postfix-2.11.1.html

But it seems it isn't the case on Ubuntu 14.04 LTS.

Can it be corrected ?

Thank you for your help !

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

Thank you for your help.

I have some news about this bug.

I changed the Postfix config to activate debug log.

And I have caught some errors "wrong MX error". Complete debug logs are
attached.

Here an example with all debug logs.

We can see just after a Gmail transaction, the Postfix process tries to
deliver a mail for yyyacrennesuser...@ac-rennes.fr.

And the DNS reply give the good MX answer :

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: begin ac-rennes.fr address list
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: pref   20 host 
mxsrv2.ac-rennes.fr/195.221.67.38
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: pref   20 host 
mxsrv1.ac-rennes.fr/195.221.67.29
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: end ac-rennes.fr address list

But, we can see just after that scache give a Gmail connexion !!!

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: private/scache: wanted attribute: 
property
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: input attribute name: property
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: input attribute value: 
gmail.com?gmail-smtp-in.l.google.com?64.233.167.27?4096

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: scache_clnt_find_dest: 
dest=smtp?*? dest_prop=gmail.com?gmail-smtp-in.l.google.com?64.233.167.27?4096 
endp_prop=0?31?1456821449 fd=16
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: smtp_session_activate: 
dest=gmail.com host=gmail-smtp-in.l.google.com addr=64.233.167.27 port=25 
features=0x101f, ttl=99, reuse=1

And the process try to deliver the mail to a wrong MX server...

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: > 
gmail-smtp-in.l.google.com[64.233.167.27]:25: RSET
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: > 
gmail-smtp-in.l.google.com[64.233.167.27]:25: MAIL 
FROM: 
SIZE=27032

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: 0D5F218551A:
to=, relay=gmail-smtp-
in.l.google.com[64.233.167.27]:25, conn_use=2, delay=582,
delays=0.11/581/0.01/0.09, dsn=5.1.1, status=bounced (host gmail-smtp-
in.l.google.com[64.233.167.27] said: 550-5.1.1 The email account that
you tried to reach does not exist. Please try 550-5.1.1 double-checking
the recipient's email address for typos or 550-5.1.1 unnecessary spaces.
Learn more at 550 5.1.1  https://support.google.com/mail/answer/6596
x64si24468451wmx.5 - gsmtp (in reply to RCPT TO command))

Note :
1. This bug is rare : most of the time Postfix deliver emails correctly
2. Each time the bug occurs, it's when before there were a TLS error with Gmail 
and the connection is "scached" (private/scache) / reuse=1 / conn_use=2
3. I have all the debug logs you want and other examples of this bug for 
yesterday

Can this help ?

** Attachment added: "debug_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1549388/+attachment/4585498/+files/debug_log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

Thank you for your help.

I have some news about this bug.

I changed the Postfix config to activate debug log.

And I have caught some errors "wrong MX error". Complete debug logs are
attached.

Here an example with all debug logs.

We can see just after a Gmail transaction, the Postfix process tries to
deliver a mail for yyyacrennesuser...@ac-rennes.fr.

And the DNS reply give the good MX answer :

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: begin ac-rennes.fr address list
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: pref   20 host 
mxsrv2.ac-rennes.fr/195.221.67.38
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: pref   20 host 
mxsrv1.ac-rennes.fr/195.221.67.29
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: end ac-rennes.fr address list

But, we can see just after that scache give a Gmail connexion !!!

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: private/scache: wanted attribute: 
property
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: input attribute name: property
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: input attribute value: 
gmail.com?gmail-smtp-in.l.google.com?64.233.167.27?4096

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: scache_clnt_find_dest: 
dest=smtp?*? dest_prop=gmail.com?gmail-smtp-in.l.google.com?64.233.167.27?4096 
endp_prop=0?31?1456821449 fd=16
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: smtp_session_activate: 
dest=gmail.com host=gmail-smtp-in.l.google.com addr=64.233.167.27 port=25 
features=0x101f, ttl=99, reuse=1

And the process try to deliver the mail to a wrong MX server...

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: > 
gmail-smtp-in.l.google.com[64.233.167.27]:25: RSET
Mar  1 09:35:50 ns302430 postfix/smtp[1581]: > 
gmail-smtp-in.l.google.com[64.233.167.27]:25: MAIL 
FROM: 
SIZE=27032

Mar  1 09:35:50 ns302430 postfix/smtp[1581]: 0D5F218551A:
to=, relay=gmail-smtp-
in.l.google.com[64.233.167.27]:25, conn_use=2, delay=582,
delays=0.11/581/0.01/0.09, dsn=5.1.1, status=bounced (host gmail-smtp-
in.l.google.com[64.233.167.27] said: 550-5.1.1 The email account that
you tried to reach does not exist. Please try 550-5.1.1 double-checking
the recipient's email address for typos or 550-5.1.1 unnecessary spaces.
Learn more at 550 5.1.1  https://support.google.com/mail/answer/6596
x64si24468451wmx.5 - gsmtp (in reply to RCPT TO command))

Note :
1. This bug is rare : most of the time Postfix deliver emails correctly
2. Each time the bug occurs, it's when before there were a TLS error with Gmail 
and the connection is "scached" (private/scache) / reuse=1 / conn_use=2
3. I have all the debug logs you want and other examples of this bug for 
yesterday

Can this help ?

** Attachment added: "debug_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1549388/+attachment/4585498/+files/debug_log.txt

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

Title:
  In some rare cases Postfix connect to a wrong MX server

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

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

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

I dont' have any relay map file.

Here is my postfix directory.

# tree /etc/postfix/
/etc/postfix/
|-- db
|   |-- block_recipient
|   `-- block_recipient.db
|-- dynamicmaps.cf
|-- main.cf
|-- main.cf.20151023.120708.bak
|-- master.cf
|-- master.cf.20151023.120708.bak
|-- post-install
|-- postfix-files
|-- postfix-script
|-- sasl
|   `-- smtpd.conf
|-- ssl
|   |-- cacert.pem
|   |-- cakey.pem
|   |-- smtpd.crt
|   `-- smtpd.key
|-- transport
|-- transport.db
|-- virtual
|-- virtual-regexp
|-- virtual-regexp.db
`-- virtual.db

# cat /etc/postfix/db/block_recipient
XXX@domain1 REJECT
YYY@domain2 REJECT
...

About /etc/postfix/virtual and /etc/postfix/virtual-regexp : no rule in
@yahoo, no rule in @gmail, no rule with "generic" (hotmail, aol, ...)
domains.

About /etc/postfix/db/block_recipient : Only emails or domains with
REJECT

Thanks !

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

Title:
  In some rare cases Postfix connect to a wrong MX server

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

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

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

I dont' have any relay map file.

Here is my postfix directory.

# tree /etc/postfix/
/etc/postfix/
|-- db
|   |-- block_recipient
|   `-- block_recipient.db
|-- dynamicmaps.cf
|-- main.cf
|-- main.cf.20151023.120708.bak
|-- master.cf
|-- master.cf.20151023.120708.bak
|-- post-install
|-- postfix-files
|-- postfix-script
|-- sasl
|   `-- smtpd.conf
|-- ssl
|   |-- cacert.pem
|   |-- cakey.pem
|   |-- smtpd.crt
|   `-- smtpd.key
|-- transport
|-- transport.db
|-- virtual
|-- virtual-regexp
|-- virtual-regexp.db
`-- virtual.db

# cat /etc/postfix/db/block_recipient
XXX@domain1 REJECT
YYY@domain2 REJECT
...

About /etc/postfix/virtual and /etc/postfix/virtual-regexp : no rule in
@yahoo, no rule in @gmail, no rule with "generic" (hotmail, aol, ...)
domains.

About /etc/postfix/db/block_recipient : Only emails or domains with
REJECT

Thanks !

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

Here is the output of "postconf -n | grep relay" :

relayhost =

Thank you for your help !

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

Title:
  In some rare cases Postfix connect to a wrong MX server

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

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

[Bug 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

Here is the output of "postconf -n | grep relay" :

relayhost =

Thank you for your help !

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549388] [NEW] In some rare cases Postfix connect to a wrong MX server

[Msd]

Public bug reported:

Hi,

I see on the logs of some of my server some strange lines :

Jan 27 11:39:53 v07 postfix/smtp[11468]: 9CCE614ED3E: to=,
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, conn_use=2,
delay=8.2, delays=0.11/7.9/0.01/0.21, dsn=5.1.1, status=bounced (host
gmail-smtp-in.l.google.com[64.233.184.26] said: 550-5.1.1 The email
account that you tried to reach does not exist. Please try 550-5.1.1
double-checking the recipient's email address for typos or 550-5.1.1
unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/answer/6596 h127si11333632wmd.92 - gsmtp
(in reply to RCPT TO command))

Here you can see a mail to a yahoo.fr domain and postfix tries to
deliver the mail to gmail-smtp-in.l.google.com !

And there is another strange thing : "conn_use=2". Normally, when
Postfix uses TLS, he can't reuse a connection and with Gmail, Postfix
has to use TLS...

So I look in the smtp process log "11468", just before my line :

Jan 27 11:39:51 v07 postfix/smtp[11468]: SSL_connect error to 
gmail-smtp-in.l.google.com[64.233.184.26]:25: lost connection
Jan 27 11:39:53 v07 postfix/smtp[11468]: A747014ECAF: Cannot start TLS: 
handshake failure
Jan 27 11:39:53 v07 postfix/smtp[11468]: Host offered STARTTLS: 
[gmail-smtp-in.l.google.com]
Jan 27 11:39:53 v07 postfix/smtp[11468]: A747014ECAF: to=, 
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, delay=19, 
delays=0.22/4.4/14/0.32, dsn=2.0.0, status=sent (250 2.0.0 OK 1453891193 
h127si11333632wmd.92 - gsmtp)
Jan 27 11:39:53 v07 postfix/smtp[11468]: 9CCE614ED3E: to=, 
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, conn_use=2, delay=8.2, 
delays=0.11/7.9/0.01/0.21, dsn=5.1.1, status=bounced (host 
gmail-smtp-in.l.google.com[64.233.184.26] said: 550-5.1.1 The email account 
that you tried to reach does not exist. Please try 550-5.1.1 double-checking 
the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn 
more at 550 5.1.1  https://support.google.com/mail/answer/6596 
h127si11333632wmd.92 - gsmtp (in reply to RCPT TO command))
Jan 27 11:39:54 v07 postfix/smtp[11468]: B8CD514ED41: to=, 
relay=mx1.free.fr[212.27.48.6]:25, conn_use=2, delay=8.3, 
delays=0.13/8/0.01/0.11, dsn=2.0.0, status=sent (250 OK)

In fact the TLS Handshake with gmail fails. It is why the connection is
not in TLS and why I see "conn_use".

I have a lot of examples like this if you need more (the to address is
not always yahoo.fr, sometimes it's outlook.com, aol.com, ...). Every
time I saw this bug, it is with gmail-smtp-in.l.google.com and there is
TLS Handshake bug.


Do you know what happens ?

** Affects: postfix (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/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

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

[Bug 1549388] [NEW] In some rare cases Postfix connect to a wrong MX server

[Msd]

Public bug reported:

Hi,

I see on the logs of some of my server some strange lines :

Jan 27 11:39:53 v07 postfix/smtp[11468]: 9CCE614ED3E: to=,
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, conn_use=2,
delay=8.2, delays=0.11/7.9/0.01/0.21, dsn=5.1.1, status=bounced (host
gmail-smtp-in.l.google.com[64.233.184.26] said: 550-5.1.1 The email
account that you tried to reach does not exist. Please try 550-5.1.1
double-checking the recipient's email address for typos or 550-5.1.1
unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/answer/6596 h127si11333632wmd.92 - gsmtp
(in reply to RCPT TO command))

Here you can see a mail to a yahoo.fr domain and postfix tries to
deliver the mail to gmail-smtp-in.l.google.com !

And there is another strange thing : "conn_use=2". Normally, when
Postfix uses TLS, he can't reuse a connection and with Gmail, Postfix
has to use TLS...

So I look in the smtp process log "11468", just before my line :

Jan 27 11:39:51 v07 postfix/smtp[11468]: SSL_connect error to 
gmail-smtp-in.l.google.com[64.233.184.26]:25: lost connection
Jan 27 11:39:53 v07 postfix/smtp[11468]: A747014ECAF: Cannot start TLS: 
handshake failure
Jan 27 11:39:53 v07 postfix/smtp[11468]: Host offered STARTTLS: 
[gmail-smtp-in.l.google.com]
Jan 27 11:39:53 v07 postfix/smtp[11468]: A747014ECAF: to=, 
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, delay=19, 
delays=0.22/4.4/14/0.32, dsn=2.0.0, status=sent (250 2.0.0 OK 1453891193 
h127si11333632wmd.92 - gsmtp)
Jan 27 11:39:53 v07 postfix/smtp[11468]: 9CCE614ED3E: to=, 
relay=gmail-smtp-in.l.google.com[64.233.184.26]:25, conn_use=2, delay=8.2, 
delays=0.11/7.9/0.01/0.21, dsn=5.1.1, status=bounced (host 
gmail-smtp-in.l.google.com[64.233.184.26] said: 550-5.1.1 The email account 
that you tried to reach does not exist. Please try 550-5.1.1 double-checking 
the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn 
more at 550 5.1.1  https://support.google.com/mail/answer/6596 
h127si11333632wmd.92 - gsmtp (in reply to RCPT TO command))
Jan 27 11:39:54 v07 postfix/smtp[11468]: B8CD514ED41: to=, 
relay=mx1.free.fr[212.27.48.6]:25, conn_use=2, delay=8.3, 
delays=0.13/8/0.01/0.11, dsn=2.0.0, status=sent (250 OK)

In fact the TLS Handshake with gmail fails. It is why the connection is
not in TLS and why I see "conn_use".

I have a lot of examples like this if you need more (the to address is
not always yahoo.fr, sometimes it's outlook.com, aol.com, ...). Every
time I saw this bug, it is with gmail-smtp-in.l.google.com and there is
TLS Handshake bug.


Do you know what happens ?

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388

Title:
  In some rare cases Postfix connect to a wrong MX server

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs