[Desktop-packages] [Bug 2045478] [NEW] [snap] Chromium-Browser starts with unmaximized window

2023-12-02 Thread Mickael Reis
Public bug reported:

Chromium browser by default start with an unmaximized window in my Ubuntu 
system and I've to manually do maximize.
I have try to edit all desktop file I can edit to add --start-maximized option 
but it doesn't work ...
And i can't edit desktop file in /snap/chromium directory

Is it possible to modify desktop file with another way or snap package
must be updated with this option ?

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2045478

Title:
  [snap] Chromium-Browser starts with unmaximized window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium browser by default start with an unmaximized window in my Ubuntu 
system and I've to manually do maximize.
  I have try to edit all desktop file I can edit to add --start-maximized 
option but it doesn't work ...
  And i can't edit desktop file in /snap/chromium directory

  Is it possible to modify desktop file with another way or snap package
  must be updated with this option ?

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


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


[Desktop-packages] [Bug 2045477] [NEW] Canon MF731 will not print

2023-12-02 Thread j gleacher
Public bug reported:

Printer works fine on other computers and worked on this one until I
reimaged it with new harddrive. Computer reports that printing is
successful, but nothing prints.

ping 192.168.1.19
PING 192.168.1.19 (192.168.1.19) 56(84) bytes of data.
64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=100 ms

nmap 192.168.1.19
Starting Nmap 7.80 ( https://nmap.org ) at 2023-12-02 14:56 EST
Nmap scan report for 192.168.1.19
Host is up (0.049s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
80/tcp   open  http
443/tcp  open  https
515/tcp  open  printer
631/tcp  open  ipp
9100/tcp open  jetdirect

/usr/lib/cups/backend/snmp
network socket://192.168.1.19 "Canon MF731C/733C UFR II" "Canon MF731C/733C" 
"MFG:Canon;MDL:MF731C/733C UFR II;CLS:PRINTER;DES:Canon MF731C/733C UFR 
II;CID:CA_XPS_OIP;CMD:LIPSLX,CPCA;PESP:V1;" ""

sudo /usr/lib/cups/backend/dnssd
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Querying "Canon\032MF731C\047733C._ipp._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._pdl-datastream._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._printer._tcp.local"...
DEBUG: sent=0, count=3
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=3, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: "UUID=6d4ff0ce-6b11-11d8-8020-f80d60e55576".
DEBUG2: query_callback: "usb_CMD=LIPSLX,CPCA".
DEBUG2: query_callback: "TLS=1.2".
DEBUG2: query_callback: "Scan=T".
DEBUG2: query_callback: "Fax=F".
DEBUG2: query_callback: 
"URF=ADOBERGB24,CP255,DM1,PQ4,RS300,SRGB24,W8-16,FN3,IS1-4,OB10-40,V1.4".
DEBUG2: query_callback: "kind=document,envelope,postcard".
DEBUG2: query_callback: "print_wfds=T".
DEBUG2: query_callback: "mopria-certified=1.2".
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: 

[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

2023-12-02 Thread Niklas Schmelzle
The graphic glitch just happened on my system (Ubuntu 23.10, Lenovo
ThinkPad T14 Gen 2a with AMD Ryzen™ 5 PRO 5650U with Radeon™ Graphics ×
12) again. I have `COGL_DEBUG=disable-batching` set in /etc/environment.
Furthermore all extensions are deactivated (however, not deleted).
System was also rebooted.

Interestingly, this time it did not occur to an XWayland window. I
configured chrome to run wayland directly (which decreased the frequency
of the error occuring, at least it seemed like it).

Here dmesg:

[70061.823842] amdgpu :07:00.0: amdgpu: [gfxhub0] no-retry page fault 
(src_id:0 ring:24 vmid:1 pasid:32771, for process chrome pid 5084 thread 
chrome:cs0 pid 5121)
[70061.823858] amdgpu :07:00.0: amdgpu:   in page starting at address 
0x000c5de7b000 from IH client 0x1b (UTCL2)
[70061.823865] amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00100430
[70061.823869] amdgpu :07:00.0: amdgpu:  Faulty UTCL2 client ID: IA 
(0x2)
[70061.823873] amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 0x0
[70061.823877] amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 0x0
[70061.823880] amdgpu :07:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
[70061.823883] amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 0x0
[70061.823886] amdgpu :07:00.0: amdgpu:  RW: 0x0


I might try to set the kernel parameter next. For clarification: I would add 
amdgpu.mcb=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run 
'sudo update-grub' (or update-grub2?). Afterwards I can just reboot?

BTW, just to rule other influences out: I do hibernate my system from
time to time. This should not have any influence, or?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2038998

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  

[Desktop-packages] [Bug 2045466] [NEW] Totem can't open h264 video if gstreamer1.0-vaapi is present

2023-12-02 Thread Michaël
Public bug reported:

Description:Ubuntu 22.04.3 LTS
Release:22.04

totem:
  Install : 42.0-1ubuntu1
  Candidate : 42.0-1ubuntu1

gstreamer1.0-vaapi:
  Install : 1.20.1-1ubuntu1
  Candidate : 1.20.1-1ubuntu1

Expected : Totem play h264 videos

To reproduce :

Ubuntu 22.04 Fresh installation with Install third-party... and
additional media formats check.

Play h264 video doesn't work with error message : An error has occurred
the specified movie could not be found

Fix : apt autoremove gstreamer1.0-vaapi

Bug isn't present in an Ubuntu 22.04 fresh installation with Install
third-party... and additional media formats option uncheck.
gstreamer1.0-vaapi is installed by ubuntu-restricted-addons.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/2045466

Title:
  Totem can't open h264 video if gstreamer1.0-vaapi  is present

Status in totem package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  totem:
Install : 42.0-1ubuntu1
Candidate : 42.0-1ubuntu1

  gstreamer1.0-vaapi:
Install : 1.20.1-1ubuntu1
Candidate : 1.20.1-1ubuntu1

  Expected : Totem play h264 videos

  To reproduce :

  Ubuntu 22.04 Fresh installation with Install third-party... and
  additional media formats check.

  Play h264 video doesn't work with error message : An error has
  occurred the specified movie could not be found

  Fix : apt autoremove gstreamer1.0-vaapi

  Bug isn't present in an Ubuntu 22.04 fresh installation with Install
  third-party... and additional media formats option uncheck.
  gstreamer1.0-vaapi is installed by ubuntu-restricted-addons.

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


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


[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

2023-12-02 Thread Juerg Haefliger
If this is an X specific package then I'd say adding it to Ubuntu won't
fly. X is dead and Wayland is the future. But I've been proven to be
wrong in the past :-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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