[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-11-02 Thread Raphaël Droz
Same behavior with an Entroware laptop on 5.15.0-52-generic (both
touchpad and internal keyboard, function keys work)


Hard to tell who's the culprit among the kernel, libusb, udev and gdm 

One weird thing in the context of resuming : The Xorg.log generated by
gdm shows:

(II) UnloadModule: "libinput" message 
[...]
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[...]
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[...]
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
(II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)


Typically:


[79.317] (II) config/udev: Adding input device Chicony USB2.0 Camera: 
Chicony  (/dev/input/event9)
[79.317] (**) Chicony USB2.0 Camera: Chicony : Applying InputClass 
"libinput keyboard catchall"
[79.317] (II) Using input driver 'libinput' for 'Chicony USB2.0 Camera: 
Chicony '
[79.317] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 43 
paused 0
[79.317] (**) Chicony USB2.0 Camera: Chicony : always reports core events
[79.317] (**) Option "Device" "/dev/input/event9"
[79.319] (II) event9  - Chicony USB2.0 Camera: Chicony : is tagged by udev 
as: Keyboard
[79.319] (II) event9  - Chicony USB2.0 Camera: Chicony : device is a 
keyboard
[79.319] (II) event9  - Chicony USB2.0 Camera: Chicony : device removed
[79.319] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input17/event9"
[79.319] (II) XINPUT: Adding extended input device "Chicony USB2.0 Camera: 
Chicony " (type: KEYBOARD, id 12)
[79.319] (**) Option "xkb_model" "pc105"
[79.319] (**) Option "xkb_layout" "fr"
[79.319] (**) Option "xkb_variant" "azerty"
[79.320] (II) event9  - Chicony USB2.0 Camera: Chicony : is tagged by udev 
as: Keyboard
[79.320] (II) event9  - Chicony USB2.0 Camera: Chicony : device is a 
keyboard

(a webcam tagged keyboard?)

I don't know if it's related, but if it is it could be a problem with
udev rules during resume?

-- 
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/1965219

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA 

[Touch-packages] [Bug 1450044] Re: On laptop on card AMD, screen brightness backlight isn't memorized between sessions (systemd-backlight)

2015-09-26 Thread Raphaël Droz
** Changed in: systemd (Ubuntu)
   Status: Expired => New

-- 
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/1450044

Title:
  On laptop on card AMD, screen brightness backlight isn't memorized
  between sessions (systemd-backlight)

Status in systemd package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop (on example my laptop on base Dual core AMD A6-4400M APU 
with Radeon HD Graphics 7670m) with Ubuntu 15.04 (systemd).
    2. Set a different screen backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  Description laptop:
  CPU~Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) 
speed/max~2000/2700 MHz Kernel~3.19.0-15-generic x86_64 Up~1:19 
Mem~1798.2/3724.2MB HDD~500.1GB(10.5% used) Procs~208 Client~Shell inxi~2.2.16
  iv@iv-pc:~$  inxi -v5
  System:Host: iv-pc Kernel: 3.19.0-15-generic x86_64 (64 bit gcc: 4.9.2)
     Desktop: Unity 7.3.2 (Gtk 3.14.12-0ubuntu2)
     Distro: Ubuntu 15.04 vivid
  Machine:   System: SAMSUNG product: 355V4C/356V4C/3445VC/3545VC v: 
P09AAN.031.CP
     Mobo: SAMSUNG model: NP355V5X-S01RU v: BOARD 00
     Bios: American Megatrends v: P09AAN date: 07/04/2013
  CPU:   Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) cache: 
2048 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
10780
     clock speeds: max: 2700 MHz 1: 2700 MHz 2: 2400 MHz
  Memory:Using dmidecode: you must be root to run dmidecode
  Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7520G]
     bus-ID: 00:01.0
     Card-2: Advanced Micro Devices [AMD/ATI] Thames [Radeon HD 
7500M/7600M Series]
     bus-ID: 01:00.0
     Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: 
fbdev,vesa)
     Resolution: 1366x768@60.1hz
     GLX Renderer: Gallium 0.4 on AMD ARUBA
     GLX Version: 3.0 Mesa 10.5.2 Direct Rendering: Yes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 29 17:16:22 2015
  InstallationDate: Installed on 2015-04-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3cdab672-0213-4aa9-8bb8-6b5a44b121b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AAN
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355V5X-S01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.version: P09AAN.031.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450044/+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 1450044] Re: On laptop on card AMD, screen brightness backlight isn't memorized between sessions (systemd-backlight)

2015-09-26 Thread Raphaël Droz
side note: I don't think this bug has anything to do with systemd

-- 
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/1450044

Title:
  On laptop on card AMD, screen brightness backlight isn't memorized
  between sessions (systemd-backlight)

Status in systemd package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop (on example my laptop on base Dual core AMD A6-4400M APU 
with Radeon HD Graphics 7670m) with Ubuntu 15.04 (systemd).
    2. Set a different screen backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  Description laptop:
  CPU~Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) 
speed/max~2000/2700 MHz Kernel~3.19.0-15-generic x86_64 Up~1:19 
Mem~1798.2/3724.2MB HDD~500.1GB(10.5% used) Procs~208 Client~Shell inxi~2.2.16
  iv@iv-pc:~$  inxi -v5
  System:Host: iv-pc Kernel: 3.19.0-15-generic x86_64 (64 bit gcc: 4.9.2)
     Desktop: Unity 7.3.2 (Gtk 3.14.12-0ubuntu2)
     Distro: Ubuntu 15.04 vivid
  Machine:   System: SAMSUNG product: 355V4C/356V4C/3445VC/3545VC v: 
P09AAN.031.CP
     Mobo: SAMSUNG model: NP355V5X-S01RU v: BOARD 00
     Bios: American Megatrends v: P09AAN date: 07/04/2013
  CPU:   Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) cache: 
2048 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
10780
     clock speeds: max: 2700 MHz 1: 2700 MHz 2: 2400 MHz
  Memory:Using dmidecode: you must be root to run dmidecode
  Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7520G]
     bus-ID: 00:01.0
     Card-2: Advanced Micro Devices [AMD/ATI] Thames [Radeon HD 
7500M/7600M Series]
     bus-ID: 01:00.0
     Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: 
fbdev,vesa)
     Resolution: 1366x768@60.1hz
     GLX Renderer: Gallium 0.4 on AMD ARUBA
     GLX Version: 3.0 Mesa 10.5.2 Direct Rendering: Yes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 29 17:16:22 2015
  InstallationDate: Installed on 2015-04-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3cdab672-0213-4aa9-8bb8-6b5a44b121b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AAN
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355V5X-S01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.version: P09AAN.031.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450044/+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 1450044] Re: On laptop on card AMD, screen brightness backlight isn't memorized between sessions (systemd-backlight)

2015-09-26 Thread Raphaël Droz
This bug do exist
- with radeon driver(s) [radeonsi in my case]
- on some AMD hardware (Kaveri [Radeon R5 Graphics])
- is well known and explained:
* https://bbs.archlinux.org/viewtopic.php?id=193130
* 
https://askubuntu.com/questions/662799/laptop-backlight-sets-to-maximum-at-startup-xubuntu-15-04
 

Either X apps only handle brightness through a hardcoded /sys path, then:
- it should be documented
- radeon driver developpers should explain why they do not use it

Either X apps can handle various brightness interfaces, then:
- they should explain how and where to configure it

I do have a working radeon_bl0 sysfs backlight interface (the only one I
have), but there seem that no software using it out there.

-- 
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/1450044

Title:
  On laptop on card AMD, screen brightness backlight isn't memorized
  between sessions (systemd-backlight)

Status in systemd package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop (on example my laptop on base Dual core AMD A6-4400M APU 
with Radeon HD Graphics 7670m) with Ubuntu 15.04 (systemd).
    2. Set a different screen backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  Description laptop:
  CPU~Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) 
speed/max~2000/2700 MHz Kernel~3.19.0-15-generic x86_64 Up~1:19 
Mem~1798.2/3724.2MB HDD~500.1GB(10.5% used) Procs~208 Client~Shell inxi~2.2.16
  iv@iv-pc:~$  inxi -v5
  System:Host: iv-pc Kernel: 3.19.0-15-generic x86_64 (64 bit gcc: 4.9.2)
     Desktop: Unity 7.3.2 (Gtk 3.14.12-0ubuntu2)
     Distro: Ubuntu 15.04 vivid
  Machine:   System: SAMSUNG product: 355V4C/356V4C/3445VC/3545VC v: 
P09AAN.031.CP
     Mobo: SAMSUNG model: NP355V5X-S01RU v: BOARD 00
     Bios: American Megatrends v: P09AAN date: 07/04/2013
  CPU:   Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) cache: 
2048 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
10780
     clock speeds: max: 2700 MHz 1: 2700 MHz 2: 2400 MHz
  Memory:Using dmidecode: you must be root to run dmidecode
  Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7520G]
     bus-ID: 00:01.0
     Card-2: Advanced Micro Devices [AMD/ATI] Thames [Radeon HD 
7500M/7600M Series]
     bus-ID: 01:00.0
     Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: 
fbdev,vesa)
     Resolution: 1366x768@60.1hz
     GLX Renderer: Gallium 0.4 on AMD ARUBA
     GLX Version: 3.0 Mesa 10.5.2 Direct Rendering: Yes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 29 17:16:22 2015
  InstallationDate: Installed on 2015-04-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3cdab672-0213-4aa9-8bb8-6b5a44b121b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AAN
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355V5X-S01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.version: P09AAN.031.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450044/+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 1603696] Re: [K501UX, Conexant CX20751/2, Black Headphone Out, Right] No sound at all

2017-05-01 Thread Raphaël Droz
E555, same chip, same problem.
This guy too:
https://askubuntu.com/questions/585709/headphones-not-recognized/674501
This one too, but got it fixed using the right "model":
http://www.linuxquestions.org/questions/slackware-14/slackware64-on-lenovo-g50-70-no-sound-4175514003/
and here too (but managed to solve it):
https://bbs.archlinux.org/viewtopic.php?id=224771
Same chip, but opposite issue (sound in the headphone only);
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654857

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

Title:
  [K501UX, Conexant CX20751/2, Black Headphone Out, Right] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Not Able to get sound out of my headphones from ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1580 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jul 16 15:22:01 2016
  InstallationDate: Installed on 2016-05-28 (49 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1580 F pulseaudio
daniel30828 F alsamixer
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [K501UX, Conexant CX20751/2, Black Headphone Out, Right] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UX.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UX.209:bd01/20/2016:svnASUSTeKCOMPUTERINC.:pnK501UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-16T14:24:41.418524

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1603696/+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 1292183] Re: Gmail password dialog box does not work and also can render the desktop useless after login

2020-10-23 Thread Raphaël Droz
Duplicate of https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549
?

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

Title:
  Gmail password dialog box does not work and also can render the
  desktop useless after login

Status in gcr package in Ubuntu:
  Confirmed

Bug description:
  After each login a dialog box appears to enter the password of my
  gmail mailbox. However even if I type the correct password, the dialog
  box reappears. It seems it's totally unimportant if I type the correct
  or some incorrect password. The only thing which helps is to cancel
  the dialog box two times. The more important problem however: the
  dialog box does not appear immediately after the login, sometimes
  dozens of seconds pass. If I open some application, terminal, etc, it
  can cause problems especially if the app is in fullscreen mode: then
  the dialog box made the desktop unusable, I can't change between
  windows, I can't type, etc (I have to switch to text console, and
  stop/start lightdm to cure the problem ... the other workaround is to
  wait after the login the dialog box to appear cancel it two times and
  then I can work, but that's a bit hmmm odd). I know the problem is
  with the dialog box, as I can see "through" the terminal window, since
  it's set to be somewhat transparent.

  It's in this way since upgraded to 13.10 (and now in 14.04 too), one
  of the main motivation to upgrade to 14.04 was to avoid this very
  annoying feature. However it seems it's still a problem.

  Unfortunately I have no idea which app/setting/etc made the system to
  ask this password and why the correct password is not accepted :( Only
  today I got some hint by swithing into text console and digging in the
  process list. It seems there is a process which onky can be found
  during this problem: /usr/lib/gcr/gcr-prompter

  That's why I send this report against the gcr package as it seems to
  own that file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcr 3.10.1-1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Mar 13 20:27:11 2014
  InstallationDate: Installed on 2012-03-03 (740 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gcr
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1292183/+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 1044549] Re: The "Access Prompt" randomly pop up!

2020-10-23 Thread Raphaël Droz
This 8-years problem still exists on 20.04 (!)

As commented in #4 back in 2012, the particular focus-mode triggers crazy 
situations.
Ex: autologin + autostart app's and/or auto-move windows (dedicated desktop per 
window)

After GDM (auto)login, the "gcr-prompter" can not be focused or even worst: not 
even visible. But still holds a TOTAL focus (grabbing all inputs).
That means neither the popup nor the session can be closed, Gnome-shell can't 
be restarted, and the only possibility is to switch to tty, use `ps`, 
determinate the name of the process... what not even a workaround for a normal 
user.

I think there is no reason that justify keeping a user from using
"Alt-F2 / restart".

About why this popup start in the first place is, IMHO, not a subject (I've 1 
owncloud + 2 google accounts there and I can't tell why this come up)
... But *if* this popup arises it must not brick the whole session.

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

Title:
  The "Access Prompt" randomly pop up!

Status in gcr package in Ubuntu:
  Triaged

Bug description:
  Access Prompt randomly pop up and prompt you for the password. Have you ever 
when opened  Youtube, Facebook, Launchpad account!n And now opened a picture of 
the computer when  pop up"Access Prompt"
  I use autologin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gcr 3.5.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 22:33:44 2012
  ExecutablePath: /usr/lib/gcr/gcr-prompter
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect 
to the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not 
provided by any .service files
   (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár
   (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: 
assertion `G_IS_SETTINGS (settings)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: 
assertion `GTK_IS_BUILDER (builder)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: 
gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+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 1044549] Re: The "Access Prompt" randomly pop up!

2020-10-23 Thread Raphaël Droz
Several problems about bug triage itself:

- Since 2012, no corresponding bug has been opened upstream 
(https://gitlab.gnome.org/GNOME/gcr/-/issues) : ping pkg-gnome-maintainers?
- upstream isn't subscribed to this bug either (@NielsDG?)
- The code about the gcr-prompter itself does not seem to have been 
significantly touched since its creation by Stef Walter in 2012:
 * https://gitlab.gnome.org/GNOME/gcr/-/commits/master/ui/gcr-prompter-tool.c
 * https://gitlab.gnome.org/GNOME/gcr/-/commits/master/ui/gcr-prompt-dialog.c
 * https://gitlab.gnome.org/GNOME/gcr/-/commits/master/ui/gcr-unlock-renderer.c

except "Grab-keyboard logic" in
https://gitlab.gnome.org/GNOME/gcr/-/commit/879b2734a9af3d8658b7b760c609daaf5b5d4fec
(part of 3.36.0) (@Dmitry Baryshkov)

Any chance this prompt could be fixed?

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

Title:
  The "Access Prompt" randomly pop up!

Status in gcr package in Ubuntu:
  Triaged

Bug description:
  Access Prompt randomly pop up and prompt you for the password. Have you ever 
when opened  Youtube, Facebook, Launchpad account!n And now opened a picture of 
the computer when  pop up"Access Prompt"
  I use autologin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gcr 3.5.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 22:33:44 2012
  ExecutablePath: /usr/lib/gcr/gcr-prompter
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect 
to the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not 
provided by any .service files
   (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár
   (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: 
assertion `G_IS_SETTINGS (settings)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: 
assertion `GTK_IS_BUILDER (builder)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: 
gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+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 1044549] Re: The "Access Prompt" randomly pop up!

2020-10-23 Thread Raphaël Droz
Retrospective:

- 
https://askubuntu.com/questions/867/how-can-i-stop-being-prompted-to-unlock-the-default-keyring-on-boot
 (Viewed 439k times, 309 votes)
- 
https://askubuntu.com/questions/495957/how-to-disable-the-unlock-your-keyring-popup
 (Viewed 403k times, 138 votes)
- https://askubuntu.com/questions/3045/how-to-disable-gnome-keyring (Viewed 54k 
times, 16 votes)
- 
https://askubuntu.com/questions/288956/after-login-there-is-a-strange-window-asking-for-a-password/289810
 (Viewed 5k times, 5 votes)
- 
https://askubuntu.com/questions/971187/17-10-stuck-at-unlock-your-login-keyring-on-startup
 (Viewed 870 times, 2 votes)
- 
https://askubuntu.com/questions/959345/why-wont-the-unlock-keyring-window-go-away
 (Viewed 440 times, 0 vote)

This popup annoyance represents the major part of the questions tagged
"gnome-keyring" (https://askubuntu.com/questions/tagged/gnome-keyring)
all over the place.

And it all ends up with two MAIN issues: This one about the "modal"
focus of the prompt.

And the other one about naming which service the popup is prompting a
password for.

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

Title:
  The "Access Prompt" randomly pop up!

Status in gcr package in Ubuntu:
  Triaged

Bug description:
  Access Prompt randomly pop up and prompt you for the password. Have you ever 
when opened  Youtube, Facebook, Launchpad account!n And now opened a picture of 
the computer when  pop up"Access Prompt"
  I use autologin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gcr 3.5.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 22:33:44 2012
  ExecutablePath: /usr/lib/gcr/gcr-prompter
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect 
to the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not 
provided by any .service files
   (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár
   (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: 
assertion `G_IS_SETTINGS (settings)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: 
assertion `GTK_IS_BUILDER (builder)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: 
gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+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 1044549] Re: The "Access Prompt" randomly pop up!

2020-10-29 Thread Raphaël Droz
Forgot:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729

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

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

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

Title:
  The "Access Prompt" randomly pop up!

Status in gcr package in Ubuntu:
  Triaged

Bug description:
  Access Prompt randomly pop up and prompt you for the password. Have you ever 
when opened  Youtube, Facebook, Launchpad account!n And now opened a picture of 
the computer when  pop up"Access Prompt"
  I use autologin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gcr 3.5.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 22:33:44 2012
  ExecutablePath: /usr/lib/gcr/gcr-prompter
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect 
to the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not 
provided by any .service files
   (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár
   (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: 
assertion `G_IS_SETTINGS (settings)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: 
assertion `GTK_IS_BUILDER (builder)' failed
   (gnome-control-center:2016): Gtk-CRITICAL **: 
gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+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 1434115] Re: apparently broken dependency resolution

2016-10-10 Thread Raphaël Droz
On production machine which most probably using php5-fpm + event or worker 
Apache2 MPM, this bug forcefully reinstall libapache2-mod-php5 after 
(unattended = minor) PHP5 update.
The direct effect of this is reinstalling mpm_prefork !

Simply stated: unattended-upgrades breaks LAMP installation by not resolving 
dependencies correctly.
Could maintainer have a look on this please?
I've been hit every time php5 package is updated.


Current workaround:
```
  Package: libapache2-mod-php5 libapache2-mod-php5filter
  Pin: origin ""
  Pin-Priority: -1
```
Note: may add php5-cgi, since the auto-installation of this package is not as 
disastrous.
Note: it's hard to *debug* this bug (unless setting XUUPOPT="-d" inside 
/etc/cron.daily/apt) and may well be left unnoticed in some case... until 
website traffic increases implying the prefork MPM extra-load.


Side question: why would unattended-upgrades provide its own (not-apt-based) 
resolution mechanism in the first place?


** Attachment added: "sample debug unattended-upgrade php5 log"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1434115/+attachment/4759001/+files/auto-upgrade.log

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

Title:
  apparently broken dependency resolution

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  It looks as though unattended upgrades' dependency resolution is a
  little broken when there are multiple alternatives and when the
  dependency is currently satisfied by a package other than the first
  alternative.

  In this case, package php5 was upgraded.  php5 depends:

  $ dpkg -s php5|grep Depends
  Depends: libapache2-mod-php5 (>= 5.5.9+dfsg-1ubuntu4.7) | 
libapache2-mod-php5filter (>= 5.5.9+dfsg-1ubuntu4.7) | php5-cgi (>= 
5.5.9+dfsg-1ubuntu4.7) | php5-fpm (>= 5.5.9+dfsg-1ubuntu4.7), php5-common (>= 
5.5.9+dfsg-1ubuntu4.7)

  I use php5-fpm, and specifically do not want libapache2-mod-php5
  installed (not least because it breaks my FPM config).  After manually
  purging libapache2-mod-php5:

  $ dpkg -l $(dpkg -s php5|grep Depends|perl -npe 's/Depends://; 
s/[,|]/\n/g'|cut -f 2 -d\ )|grep ^[a-z]
  un  libapache2-mod-php5 
  (no description available)
  un  libapache2-mod-php5filter   
  (no description available)
  un  php5-cgi
  (no description available)
  ii  php5-common 5.5.9+dfsg-1ubuntu4.7 
   amd64Common files for packages built from the php5 source
  ii  php5-fpm5.5.9+dfsg-1ubuntu4.7 
   amd64server-side, HTML-embedded scripting language (FPM-CGI 
binary)

  note that:
  • php5-fpm is installed and therefore that dependency of php5 was already 
satisfied
  • php5-cgi and libapache2-mod-php5filter are alternative dependencies along 
with libapache2-mod-php5, yet neither got installed in the way that 
libapache2-mod-php5 did.

  
  For completeness' sake, here's an excerpt of the unattended upgrade log (full 
log attached) showing that it was this morning's upgrade run that installed 
libapache2-mod-php5:

  Selecting previously unselected package libapache2-mod-php5.
  Preparing to unpack .../libapache2-mod-php5_5.5.9+dfsg-1ubuntu4.7_amd64.deb 
...
  Unpacking libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.7) ...
  Preparing to unpack .../php5_5.5.9+dfsg-1ubuntu4.7_all.deb ...
  Unpacking php5 (5.5.9+dfsg-1ubuntu4.7) over (5.5.9+dfsg-1ubuntu4.6) ...

  Other requested information:

  $ lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.82.1ubuntu2.1
Candidate: 0.82.1ubuntu2.1
Version table:
   *** 0.82.1ubuntu2.1 0
  500 http://ubuntu.orion.retrosnub.co.uk/ubuntu/ trusty-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.82.1ubuntu2 0
  500 http://ubuntu.orion.retrosnub.co.uk/ubuntu/ trusty/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1434115/+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 1450044] Re: On laptop on card AMD, screen brightness backlight isn't memorized between sessions (systemd-backlight)

2015-11-30 Thread Raphaël Droz
I do have a radeon_bl0 symlink inside /sys/class/backlight/ pointing to a valid 
path: /sys/devices/pci:00/:00:01.0/drm/card0/card0-eDP-1/radeon_bl0
I do not use systemd.

Handling of radeon_bl0 is probably an the issue for *another* subsystem,
most probably Xorg, udev or ACPI (= the same package that currently
handle the acpi_video0 file (which one is it?)

-- 
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/1450044

Title:
  On laptop on card AMD, screen brightness backlight isn't memorized
  between sessions (systemd-backlight)

Status in systemd package in Ubuntu:
  Expired

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop (on example my laptop on base Dual core AMD A6-4400M APU 
with Radeon HD Graphics 7670m) with Ubuntu 15.04 (systemd).
    2. Set a different screen backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  Description laptop:
  CPU~Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) 
speed/max~2000/2700 MHz Kernel~3.19.0-15-generic x86_64 Up~1:19 
Mem~1798.2/3724.2MB HDD~500.1GB(10.5% used) Procs~208 Client~Shell inxi~2.2.16
  iv@iv-pc:~$  inxi -v5
  System:Host: iv-pc Kernel: 3.19.0-15-generic x86_64 (64 bit gcc: 4.9.2)
     Desktop: Unity 7.3.2 (Gtk 3.14.12-0ubuntu2)
     Distro: Ubuntu 15.04 vivid
  Machine:   System: SAMSUNG product: 355V4C/356V4C/3445VC/3545VC v: 
P09AAN.031.CP
     Mobo: SAMSUNG model: NP355V5X-S01RU v: BOARD 00
     Bios: American Megatrends v: P09AAN date: 07/04/2013
  CPU:   Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) cache: 
2048 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
10780
     clock speeds: max: 2700 MHz 1: 2700 MHz 2: 2400 MHz
  Memory:Using dmidecode: you must be root to run dmidecode
  Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7520G]
     bus-ID: 00:01.0
     Card-2: Advanced Micro Devices [AMD/ATI] Thames [Radeon HD 
7500M/7600M Series]
     bus-ID: 01:00.0
     Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: 
fbdev,vesa)
     Resolution: 1366x768@60.1hz
     GLX Renderer: Gallium 0.4 on AMD ARUBA
     GLX Version: 3.0 Mesa 10.5.2 Direct Rendering: Yes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 29 17:16:22 2015
  InstallationDate: Installed on 2015-04-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3cdab672-0213-4aa9-8bb8-6b5a44b121b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AAN
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355V5X-S01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.version: P09AAN.031.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450044/+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 2102694] [NEW] dangerous "sanitized_helper" contains /** rwkl,

2025-03-14 Thread Raphaël Droz
Public bug reported:

abstractions/ubuntu-helpers's sanitized_helper which was a Pandora box
from from its inception.

It contains:

```
network inet, # line 42
/** rwkl, # line 88
/usr/{,local/}lib*/{,**/}* Pixr, # line 58
```


what basically means : "stop using apparmor" and access any file on my 
filesystem and more than enough to cause *grave* damages. (write-mode to 
everything)

The first comment in the profile says: "lenient profile when 'Ux' is desired" 
and also says:
> LP: #851986 until AppArmor utilizes proper environment filtering

But ... LP: #851986 is "Won't fix" ... since 2012.

Last but not least, more and more programs were made to transition to this 
almost-Ux mode.
~150 in a default modern installation, namely:

akregator
alpine
amarok
anjal
apport-bug
apturl
ark
arora
audacious2
audacity
azureus
balsa
bangarang
banshee
banshee-1
bitstormlite
btmaketorrentgui
chromium{,-browser}
citadel
clamscan
claws-mail
cone
debconf-communicate
decibel
deluge{,-gtk,-console}
digikam
dillo
dolphin
Dooble
dragon
dvipdfm
dvipdfmx
elinks
elmo
emacsclient.emacs2[2-9]
emacsclient.emacs-snapshot
emacs-snapshot-gtk
eog
epiphany
epiphany-browser
epiphany-webkit
esperanza
evince
evolution
exaile
file-roller
firefox
freevo
geary
gedit
gimp*
gmerlin
gmplayer
gnome-appearance-properties
gnome-btdownload
gnome-gmail
gnome-mplayer
gwenview
gxmms
gxmms2
hornsey
iceweasel
jlgui
juk
kaffeine
kate
kazehakase
kde4-config
kde-open
kget
kmail
kmplayer
konqueror
krusader
ktorrent
leafpad
libreoffice
liferea-add-feed
links
listen
localc
lodraw
loimpress
lowriter
lpr
lpstat
lynx.cur
mailody
midori
mktexpk
mktextfm
modest
mousepad
mplayer
muine
mutt
nautilus
nautilus-sendto
netrik
netsurf
okular
oocalc
oodraw
ooffice
ooimpress
oowriter
opera
pcmanfm
plasma-browser-integration-host
potamus
promoe
qbittorrent
qmmp
quodlibet
rhythmbox
scim
scim-bridge
seamonkey
shotwell
smplayer
strange-quark
swfdec-player
sylpheed
thunar
thunderbird
timidity
tkrat
totem
totem-gstreamer
totem-xine
transmission{,-gtk,-qt,-cli}
{t,T}hunar
vim.gnome
vlc
w3m
xarchiver
xdg-open
xfmedia
xmms
yelp
/opt/brave.com/brave{,-beta,-dev,-nightly}/brave-browser{,-beta,-dev,-nightly}
/opt/google/chrome{,-beta,-unstable}/google-chrome{,-beta,-unstable}
/usr/lib{,64}/chromium{,-browser}/chromium{,-browser}
/usr/lib{,64}/firefox*/firefox*
/usr/lib/fennec-*/fennec
/usr/lib/GNUstep/Applications/GNUMail.app/GNUMail
/usr/lib/icecat-*/icecat
/usr/lib/iceweasel/iceweasel
/usr/lib/libreoffice/program/soffice
/usr/lib/mozilla/kmozillahelper
/usr/lib/@{multiarch}/libproxy/*/pxgsettings
/usr/lib/openoffice/program/soffice
/usr/lib/thunderbird*/thunderbird{,.sh,-bin}
/usr/share/minirok/minirok.py
/usr/share/software-center/software-center


Pinch me if you can't find a way to do hidden & automated arbitrary file access 
and network exfiltration using one of these (Actually more than one good 
candidate for such an attack)

As commented in #1042771, some of these do have their own profile
(evince/LibreOffice) but are set to run uncontrolled anyway.


To summarize: Tons of insecure programs are knowingly granted uncontrolled 
permissions (full fs access + full network access + executing arbitrary 
programs in /usr/{,local/}lib*/{,**/}*

No actual reason is given (the same program, for being called a
"helper", becomes trusted and Ux-friendly) and no resolution is even
being considered (2012 "Won't fix") and it's been so since at least one
decade.


The very minimum fix is that to comment these by default:
network inet, # line 42
/usr/{,local/}lib*/{,**/}* Pixr, # line 58

and this
/** rwkl, # line 88

should be adapted to something a bit more reasonable like
@{XDG_CACHE_HOME} & @{XDG_DOWNLOAD_DIR} & /tmp


(And LP #1042771 should fine a resolution so that less programs depends on 
`sanitized_helper` (even less LoC monsters like LibreOffice or firefox)


Finally, note that unless I'm mistaken, `abstractions/ubuntu-helpers` stating
`usr/bin/firefox Cxr -> sanitized_helper` (to take one example), means that 
launching firefox from totem or any media-players makes it run unconfined, 
meanwhile it is when ran directly from the user. This sounds absurd and a 
serious hole in the apparmor security model.

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


** Tags: aa-policy

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

Title:
  dangerous "sanitized_helper" contains /** rwkl,

Status in apparmor package in Ubuntu:
  New

Bug description:
  abstractions/ubuntu-helpers's sanitized_helper which was a Pandora box
  from from its inception.

  It contains:

  ```
  network inet, # line 42
  /** rwkl, # line 88
  /usr/{,local/}lib*/{,**/}* Pixr, # line 58
  ```

  
  what basically means : "stop using apparmor" and access any file on my 
filesystem and more than enough to cause *grave* damages. (write-mode to 
everything)

  The

[Touch-packages] [Bug 2102696] [NEW] insecure usr.bin.man profile

2025-03-14 Thread Raphaël Droz
Public bug reported:

>From the profile itself:

# The purpose of this profile isn't to confine man itself (that might be
# nice in the future, but is tricky since it's quite configurable), but to
# confine the processes it calls that parse untrusted data.
/** mrixwlk,


This is not an acceptable use of apparmor. The replacement below will handle 
95% of the cases.

owner /dev/pts/[0-9]* rw,
/dev/tty rw,
/usr/share/terminfo/** r,

/etc/groff/man.local r,
/etc/manpath.config r,
/usr/bin/grotty ixr,
/usr/bin/{,g,n}roff rmCx -> &man_groff,
/usr/local/share/man/{,**} r,
/usr/share/groff/** r,
/usr/share/man/{,**} r,
/var/cache/man/index.db rkw,
/{,usr/}bin/less{,file,pipe} rix,
@{HOME}/.local/share/man/index.db rkw,
@{HOME}/.local/{,share/}man/{,**} r,


Other improvements include usage of
#include 

and a couple of:
/{usr/,}bin/dash ixr,
/usr/bin/{,g,n}roff ixr,

here and there.
Unsetting LESSHISTFILE is also advised to avoid less doing (useless) histfile 
(re)write attempts.


The above changes means accessing a handful of files, dropping
read/write access to the whole filesystem and still fulfilling the vast
majority of `man` usages. (Users configuring `man` can generally
interpret `journalctl` apparmor warnings and/or configure it). A comment
in the file could even ease the task, like:

# uncomment the line below if man fails edge-cases
# /** mrixwlk,


See also #1788973

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


** Tags: aa-policy

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

Title:
  insecure usr.bin.man profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  From the profile itself:

  # The purpose of this profile isn't to confine man itself (that might be
  # nice in the future, but is tricky since it's quite configurable), but to
  # confine the processes it calls that parse untrusted data.
  /** mrixwlk,

  
  This is not an acceptable use of apparmor. The replacement below will handle 
95% of the cases.

  owner /dev/pts/[0-9]* rw,
  /dev/tty rw,
  /usr/share/terminfo/** r,

  /etc/groff/man.local r,
  /etc/manpath.config r,
  /usr/bin/grotty ixr,
  /usr/bin/{,g,n}roff rmCx -> &man_groff,
  /usr/local/share/man/{,**} r,
  /usr/share/groff/** r,
  /usr/share/man/{,**} r,
  /var/cache/man/index.db rkw,
  /{,usr/}bin/less{,file,pipe} rix,
  @{HOME}/.local/share/man/index.db rkw,
  @{HOME}/.local/{,share/}man/{,**} r,

  
  Other improvements include usage of
  #include 

  and a couple of:
  /{usr/,}bin/dash ixr,
  /usr/bin/{,g,n}roff ixr,

  here and there.
  Unsetting LESSHISTFILE is also advised to avoid less doing (useless) histfile 
(re)write attempts.


  The above changes means accessing a handful of files, dropping
  read/write access to the whole filesystem and still fulfilling the
  vast majority of `man` usages. (Users configuring `man` can generally
  interpret `journalctl` apparmor warnings and/or configure it). A
  comment in the file could even ease the task, like:

  # uncomment the line below if man fails edge-cases
  # /** mrixwlk,


  See also #1788973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2102696/+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