[Desktop-packages] [Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

2022-07-31 Thread Daniel van Vugt
** Tags added: focus

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

Title:
  gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have set gnome to "focus on hover", i.e. focus follows mouse. If I
  alt-tab to bring a window to the front but the mouse is over another
  window, then the hovered-over window will reclaim focus and the window
  I raised will typically get covered up again.

  In previous gnome versions, if I explicitly focussed a window via
  keyboard shortcuts, it remained focussed and I think this is the
  preferred behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:35:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-17 (33 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1814839] Re: "Sloppy" or "Focus on Hover" window focus is slow to respond, some keystrokes go to the wrong (old) window

2022-07-31 Thread Daniel van Vugt
** Tags added: focus

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

Title:
  "Sloppy" or "Focus on Hover" window focus is slow to respond, some
  keystrokes go to the wrong (old) window

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/469

  ---

  Ubuntu 18.04.  Gnome X11 session.

  When window focus policy is set to follow the mouse, then if the mouse
  is moved into a new window and keystrokes typed immediately
  afterwards, the keystrokes go to the old window (invariably causing
  application errors).

  This is extremely annoying for rapid-fire developers, who for example
  run vim in one window to edit a script and bash in another to test the
  script; the sequence 1) save changes in vim; 2) move mouse to the bash
  window; 3) type the command to run the script results in the shell
  command (or part of it) being received by vim in the old window (with
  occasionally-entertaining effects).

  It seems like mouse-movement events are not kept in-order with respect
  to keyboard events.  I can see the mouse pointer move to the new
  window before I type on the keyboard, so I know the mouse-move events
  have been received before the keystrokes.

  Speculations:

  This might be a window-manager bug: Although the mouse cursor has
  moved before I type, the window borders may not yet have changed to
  indicate a changed focus (not certain because the sequence is so
  quick).  Therefore the window manager might be (erroneously)
  continuing to pass keystrokes to the "current" (i.e. old) window after
  the mouse moves into the new window.  I'm assuming here that the
  window manager is able to receive mouse-move and keyboard events in a
  single stream, or timestamped, or otherwise marked so they can be
  processed in the order they originally occurred.

  Or maybe Xorg does not keep them in order or doesn't allow the window-
  manager to know their relative order.  Or maybe keystrokes are going
  directly to the old window without filtering for the current mouse
  position (if this is the case, then IMO xorg should be told to stop
  delivering keystrokes if the mouse is outside a specified region until
  the window-manager tells it to resume delivery; or some similar way to
  allow the focus-change to occur first).

  STEPS TO REPRODUCE:

  1. Run gnome-tweaks, set Windows->Window Focus to "Sloppy"
  2. Open two vertically-adjacent gnome-terminal windows
  3. Put cursor in the top window.  Wait 2 seconds.
  4. Move mouse (with one hand) rapidly into the other window, then 
(immediately) type a character into the other window (with the other hand)

  ACTUAL RESULTS: The keystroke appears in the old window

  EXPECTED RESULTS: Keystroke appears in the new window (i.e. the
  keystroke is not processed at all until the window manager completes
  the focus change). In other words, "typeahead" should encompass both
  keystrokes and mouse movements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814839/+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 1983117] Re: "Focus Follow Mouse" auto-raises windows when it shouldn't

2022-07-31 Thread Daniel van Vugt
This might be related to bug 1969602, but please also review these bugs
to check for duplicates:

https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=focus

** Tags added: focus

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

Title:
  "Focus Follow Mouse" auto-raises windows when it shouldn't

Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce on Jammy LTS:
  1. Create a new empty user and login under Wayland
  2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover"
  3. Notice that "Raise Windows When Focused" is disabled

  Windows auto-raise when changing workspaces:
  1. Open two terminal windows and partially overlap them
  2. Place the mouse over the lower terminal window so that it remains lowered
  3. Do not move the mouse: Press Super-End to change to another workspace, 
then Super-Begin to go back
  4. Observe that the terminal window the mouse is over has been raised

  The expected behaviour is that windows are not auto-raised when
  changing workspaces

  Windows auto-raise when closing windows:
  1. Open three terminal windows such that parts of all windows are visible but 
all windows overlap.
  2. Place the mouse inside the topmost terminal so that it is within the 
visible lowest terminal
  3. Without moving the mouse Ctrl-D the terminal to close it
  4. Observe that the lowest terminal window the mouse is over has been raised 
to the top.

  The expected behaviour is that windows are not auto-raised when
  closing windows

  Logout/Login using X and repeat these actions. Notice that window
  ordering remains fixed in order. This has been the expected behaviour
  of gnome for the last 10 years or so.

  This is a behaviour regression for Ubuntu users upgrading from the
  last LTS (using X).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 12:11:27 2022
  InstallationDate: Installed on 2022-06-25 (33 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+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 1983115] Re: Keybinding "Lower window below other windows" lowers windows below the desktop icons

2022-07-31 Thread Daniel van Vugt
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng
in Ubuntu.
https://bugs.launchpad.net/bugs/1983115

Title:
  Keybinding "Lower window below other windows" lowers windows below the
  desktop icons

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce on Jammy LTS:

  1. Create an new empty user
  2. Login using Wayland
  3. Open "Settings" -> "Keyboard" -> "View and Customize Shortcuts" -> 
"Windows" -> "Lower window below other windows"
  4. Click on the setting "Lower window below other windows" and assign a 
keybinding, eg Alt-Down
  5. Close settings
  3. Find the "Home" icon on the desktop
  5. Open a terminal and place it over the home icon
  6. Press the keybinding "Lower window below other windows" and observe that 
the terminal window is lowered below the Home icon. eg the Home icon becomes 
visible on top of the terminal window
  7. Try click on the Hamburger Menu in terminal and observe the menu does not 
open but the window raises above the Home icon.

  Logout, login under X mode and repeat. Notice that the window does not
  lower below the home icon and that the Hamburger Menu works on the
  first click. This is the expected behaviour of this feature going back
  at least 10 years.

  For Ubuntu users coming from the previous LTS (using X) this is a
  behaviour regression.

  I'm guessing this is mutter because it is wayland specific and mutter
  src has the "lower" keybinding which is described as the same "Lower
  window below other windows"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 11:58:21 2022
  InstallationDate: Installed on 2022-06-25 (33 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1983115/+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 1983108] Re: Boot issue

2022-07-31 Thread Daniel van Vugt
Can you provide a log or photo of the screen from the time when the
problem was happening?


** Package changed: plymouth (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Boot issue

Status in Ubuntu:
  Incomplete

Bug description:
  It caused my pc to get stuck during boot time. At rebooting, all
  worked fine

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jul 29 16:13:04 2022
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  InstallationDate: Installed on 2020-10-02 (664 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2009
  dmi.bios.release: 4.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1983108/+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 1983175] Re: In Wayland, can't wake up monitor after it has gone black

2022-07-31 Thread Daniel van Vugt
Thanks for the bug report.

Next time the bug occurs, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu)

** Tags added: jammy

** Tags added: wayland wayland-session

** Tags added: i915

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

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

Title:
  In Wayland, can't wake up monitor after it has gone black

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  sorry I don't know if it's about GDM or else.

  Ubuntu 22.04.1 LTS
  jammy
  Linux 5.15.0-41-generic x86_64 x86_64
  ubuntu / wayland
  installed DE's are :
  ubuntu.desktop  ubuntu-xorg.desktop

  My system is set to turn screen black after some minutes. And after
  some other minutes later, it locks the screen → no sleep nor hibernate
  involved ( even if sleep and hibernate are ok on that machine. )

  On Xorg, after screen's gone black, any mouse or keyboard solicitation
  fires up again the screen, as expected.

  On Wayland, after screen's gone black, any mouse or keyboard
  solicitation just does nothing, screen stays black.

  BUT

  keyboard is not turned off : only thing that works for « waking up » the 
screen is
  key-combo [ ctrl ] + [ alt ] + [ F1 ]

  If of any interest :
  django@ASGARD:~$ sudo lshw -c video
  [sudo] Mot de passe de django : 
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabricant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 nom logique: /dev/fb0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom fb
 configuration : depth=32 driver=i915 latency=0 resolution=1920,1080
 ressources : irq:33 mémoire:f780-f7bf 
mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d
  django@ASGARD:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983175/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

2022-07-31 Thread Daniel van Vugt
** Bug watch removed: github.com/micheleg/dash-to-dock/issues #1769
   https://github.com/micheleg/dash-to-dock/issues/1769

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1967121

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  Fix Released
Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  If the dock is set to auto-hide and a window is under the dock, then
  the dock hides prematurely when a menu is opened from one of its
  icons. This only seems to happen with GNOME 42.

  [Test Plan]

  1. Set the dock to auto hide.
  2. Move a window under the dock's position so that it wants to auto-hide.
  3. Open the dock and right click on one of the icons to open a menu.

  Expected: Dock stays open while the menu is open.
  Observed: Dock closes while the menu is open.

  [Where problems could occur]

  This fix may affect any scenarios relating to the dock auto-hiding.

  [Other Info]

  Upstream fixes:
  ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739
  dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.

2022-07-31 Thread Daniel van Vugt
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1769
   https://github.com/micheleg/dash-to-dock/issues/1769

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1769
   Importance: Unknown
   Status: Unknown

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1983130

Title:
  Ubuntu dock set to auto-hide hides after a right-click menu is closed
  even when there are no reasons for it to do so.

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Expected behavior: Dock set to auto-hide would remain shown after
  either a right-click menu option is selected, or a right-click menu is
  cancelled.

  Actual behavior: Dock hides after a right-click menu closes even when
  there are no windows in its space.

  Additional notes: Dock can be temporarily reset to its normal behavior when 
one of these actions are performed:

- when a window enters the dock's usual space
- when the "show applications" menu is opened and closed
- when a maximized window is opened and closed/minimized

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+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 1875767] Re: When operating install/removal with apt, zed floods log and apparently crashes snapshoting

2022-07-31 Thread Launchpad Bug Tracker
[Expired for zsys (Ubuntu) because there has been no activity for 60
days.]

** Changed in: zsys (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  When operating install/removal with apt, zed floods log and apparently
  crashes snapshoting

Status in zfs-linux package in Ubuntu:
  Won't Fix
Status in zsys package in Ubuntu:
  Expired

Bug description:
  Hello!

  When I ran a install, it behaved like this:

  ERROR rpc error: code = DeadlineExceeded desc = context deadline exceeded 
  ... etc apt messages ...
  A processar 'triggers' para libc-bin (2.31-0ubuntu9) ...
  ERROR rpc error: code = Unavailable desc = transport is closing 

  Log gets flooded by the follow message:

  abr 28 20:41:48 manauara zed[512257]: eid=10429 class=history_event 
pool_guid=0x7E8B0F177C4DD12C
  abr 28 20:41:49 manauara zed[508106]: Missed 1 events

  And machine load gets high for incredible amount of time. Workarround
  is:

  systemctl restart zsysd
  systemctl restart zed

  System also gets a bit slow and fans get high for a while (because the
  load).

  This is a fresh install of ubuntu 20.04 with ZFS on SATA SSD.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 28 20:49:14 2020
  InstallationDate: Installed on 2020-04-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875767/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

2022-07-31 Thread Jeremy Bicha
** Also affects: gdk-pixbuf (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress
Status in gdk-pixbuf source package in Focal:
  New

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1983161] Re: gnome-shell memory leak

2022-07-31 Thread Daniel van Vugt
Disabled extensions can still cause bugs because gnome-shell relies on
extensions to not be buggy to disable themselves cleanly.

Please try deleting custom extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

Also your system log is full of errors coming from appindicators. That's
a built-in extension so it can't be uninstalled, please just try
disabling that one.

** Tags added: gnome-shell-leak

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-shell memory leak

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  As I use it more and more, the memory used by gnome-shell is also increasing.
  I've tested it in Xorg and Wayland and both result in a gradual increase in 
memory.
  I also tested with all my extensions turned off and the result was also a 
gradual increase in memory

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 30 09:15:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (97 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983161/+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 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses

2022-07-31 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5455
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5455

** Changed in: gnome-shell
   Importance: Medium => Unknown

** Changed in: gnome-shell
   Status: Expired => Unknown

** Changed in: gnome-shell
 Remote watch: bugzilla.gnome.org/ #663725 => 
gitlab.gnome.org/GNOME/gnome-shell/-/issues #5455

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

Title:
  Too many icons in Gnome Shell Activities Overview require ellipses

Status in GNOME Shell:
  Unknown
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Several apps in the default Ubuntu 17.04 or 17.10 install have
  Ellipses when shown in GNOME Shell's Activities Overview.

  This was made worse by switching GNOME Shell to use the Ubuntu font
  because the Ubuntu font is a bit wider than GNOME's default Cantarell
  font so some apps that didn't require ellipses in 17.04 require them
  now in 17.10 Alpha.

  The upstream GNOME bug proposes that apps names be allowed to use 2
  lines. This is similar to what the Settings app (gnome-control-center)
  does.

  This is also really bad for languages that use more characters than
  English.

  Original Bug Title
  --
  Gnome Shell Activities Overview should show full names on mouse hover

  Original Bug Report
  ---
  The title says it all --- especially when choosing recent documents, if they 
start with the same say 12 or 14 letters, it's impossible to differentiate them 
 (see attached screenshot).

  When mouse is hovering an icon, the full name of the
  application/document should be shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/968213/+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 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.

2022-07-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1983130

Title:
  Ubuntu dock set to auto-hide hides after a right-click menu is closed
  even when there are no reasons for it to do so.

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Expected behavior: Dock set to auto-hide would remain shown after
  either a right-click menu option is selected, or a right-click menu is
  cancelled.

  Actual behavior: Dock hides after a right-click menu closes even when
  there are no windows in its space.

  Additional notes: Dock can be temporarily reset to its normal behavior when 
one of these actions are performed:

- when a window enters the dock's usual space
- when the "show applications" menu is opened and closed
- when a maximized window is opened and closed/minimized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983130/+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 1983207] [NEW] [VivoBook_ASUSLaptop X509JA_X509JA, Realtek ALC256, Mic, Internal] Underruns, dropouts or crackling sound

2022-07-31 Thread Kaleab Asfaw Azezew
Public bug reported:

The crackling sound happens both with the builtin mic and headset mic.
And it doesn't happen when I boot to windows.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  blankk 1760 F pulseaudio
 /dev/snd/pcmC0D0c:   blankk 1760 F...m pulseaudio
 /dev/snd/pcmC0D0p:   blankk 1760 F...m pulseaudio
 /dev/snd/timer:  blankk 1760 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 31 16:41:55 2022
InstallationDate: Installed on 2022-02-06 (175 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_PulseAudioLog:
 Jul 31 16:20:16 blankk-Lenovo-V15-IWL dbus-daemon[1078]: [system] Activating 
via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1309 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
 Jul 31 16:20:29 blankk-Lenovo-V15-IWL systemd[1303]: pulseaudio.service: 
Succeeded.
 Jul 31 16:20:39 blankk-Lenovo-V15-IWL systemd[1303]: pulseaudio.socket: 
Succeeded.
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [VivoBook_ASUSLaptop X509JA_X509JA, Realtek ALC256, Mic, Internal] 
Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2021
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X509JA.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X509JA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX509JA.308:bd06/11/2021:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX509JA_X509JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX509JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X509JA_X509JA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-08T12:21:11.032664

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [VivoBook_ASUSLaptop X509JA_X509JA, Realtek ALC256, Mic, Internal]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The crackling sound happens both with the builtin mic and headset mic.
  And it doesn't happen when I boot to windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blankk 1760 F pulseaudio
   /dev/snd/pcmC0D0c:   blankk 1760 F...m pulseaudio
   /dev/snd/pcmC0D0p:   blankk 1760 F...m pulseaudio
   /dev/snd/timer:  blankk 1760 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 31 16:41:55 2022
  InstallationDate: Installed on 2022-02-06 (175 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioLog:
   Jul 31 16:20:16 blankk-Lenovo-V15-IWL dbus-daemon[1078]: [system] Activating 
via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1309 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Jul 31 16:20:29 blankk-Lenovo-V15-IWL systemd[1303]: pulseaudio.service: 
Succeeded.
   Jul 31 16:20:39 blankk-Lenovo-V15-IWL systemd[1303]: pulseaudio.socket: 
Succeeded.
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [VivoBook_ASUSLaptop X509JA_X509JA, Realtek 

[Desktop-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps

2022-07-31 Thread M Conrad
```bash
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy
muksihs@omen-desktop:~$  set | grep -E 
'XMODIFIERS|GTK_IM_MODULE|QT_IM_MODULE';setxkbmap -query
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
rules:  evdev
model:  pc105
layout: us
variant:altgr-intl
options:compose:lwin,compose:rwin,grp_led:scroll,mod_led:compose
muksihs@omen-desktop:~$ cat .xsessionrc 
#!/bin/bash

export CLUTTER_IM_MODULE=ibus
export GTK_IM_MODULE=ibus
export QT_IM_MODULE=ibus
export XMODIFIERS=@im=ibus

muksihs@omen-desktop:~$ 
```

I'm using ibus with a local m17n layout.

Layout file: https://github.com/CherokeeLanguage/m17n.d/blob/main/chr-
phonetic.mim

My issue with ibus and intellij/pycharm is that the cursor is positioned
before the last character typed instead of after on short sequences
where a longer sequence exists.

The cursor appears to get moved back one character in the matching case.

I'm not sure the issue I'm having is exactly the same as this issue as
I'm not using dead keys. See
https://youtrack.jetbrains.com/issue/PY-55374/ibus-input-issue-where-
cursor-position-ends-being-before-the-character-inserted

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

Title:
  Unable to use dead keys in Java apps

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1863080/+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 1983181] Re: Cheese Internal data stream error

2022-07-31 Thread Erich Eickmeyer 
** Package changed: linux (Ubuntu) => cheese (Ubuntu)

** Changed in: cheese (Ubuntu)
   Status: Incomplete => New

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller
  than 65535 pixels are not supported

  (cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 30 16:21:11 2022
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese41.1-2
   cheese-common 41.1-2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  corrado1757 F wireplumber
   /dev/snd/controlC0:  corrado1757 F wireplumber
   /dev/snd/seq:corrado1754 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220711.gitdfa29317-0ubuntu1
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983181/+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 1983181] [NEW] Cheese Internal data stream error

2022-07-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

corrado@corrado-n4-kk-0718:~$ cheese

(cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller than
65535 pixels are not supported

(cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: cheese 41.1-2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 30 16:21:11 2022
InstallationDate: Installed on 2022-07-19 (11 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
RelatedPackageVersions:
 cheese41.1-2
 cheese-common 41.1-2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
--- 
ProblemType: Bug
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  corrado1757 F wireplumber
 /dev/snd/controlC0:  corrado1757 F wireplumber
 /dev/snd/seq:corrado1754 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-07-19 (11 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic  N/A
 linux-firmware 20220711.gitdfa29317-0ubuntu1
RfKill:
 1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags:  wayland-session kinetic
Uname: Linux 5.15.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
_MarkForUpload: True
dmi.bios.date: 05/11/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: cheese (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug apport-collected gstreamer-error kinetic 
wayland-session
-- 
Cheese Internal data stream error
https://bugs.launchpad.net/bugs/1983181
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cheese in Ubuntu.

-- 
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 1983202] [NEW] Link within email not actioned

2022-07-31 Thread Tony Middleton
Public bug reported:

Accessing a http or https link in an email has no effect.  This is true
if I left click on the link or right click and select "Open link in
browser".  My default browser is Firefox.

Just to confuse things it does work occasionally, the first time I open
a link after loading Thunderbird.

The problem still exists in safe mode.  I think the problem started
after the update to 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BuildID: 20220628000715
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: KDE
Date: Sun Jul 31 11:51:22 2022
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2020-08-08 (721 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp45s0 scope link metric 1000 
 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 
 192.168.0.2 dev enp45s0 proto static scope link metric 100 
 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
PrefSources:
 prefs.js
 user.js
Profiles: Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to jammy on 2022-05-16 (75 days ago)
dmi.bios.date: 07/01/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550-A PRO (MS-7C56)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.10:bd07/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C56
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug jammy

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

Title:
  Link within email not actioned

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Accessing a http or https link in an email has no effect.  This is
  true if I left click on the link or right click and select "Open link
  in browser".  My default browser is Firefox.

  Just to confuse things it does work occasionally, the first time I
  open a link after loading Thunderbird.

  The problem still exists in safe mode.  I think the problem started
  after the update to 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BuildID: 20220628000715
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jul 31 11:51:22 2022
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-08 (721 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp45s0 scope link metric 1000 
   192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 
100 
   192.168.0.2 dev enp45s0 proto static scope link metric 100 
   192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources:
   prefs.js
   user.js
  Profiles: Profile0 (Default) - 

[Desktop-packages] [Bug 1983199] Re: Unable to connect to Ubuntu running RDP based remote desktop

2022-07-31 Thread Adam Baxter
** Attachment added: "journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1983199/+attachment/5606112/+files/grd-journalctl.txt

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

Title:
  Unable to connect to Ubuntu running RDP based remote desktop

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Initial setup: machine was headless, set up TLS using openssl, set key 
location using grdctl.
  Windows RDP client was unable to connect - journalctl showed that the 
username was unable to be retreived (from dbus?).

  Set password using grdctl /
  https://gitlab.gnome.org/-/snippets/1778#note_1515700

  Plugged a monitor and keyboard in, checked Settings and the password
  was garbage. Reset the password, re-enabled RDP and the Windows client
  was still unable to connect:

  ```
  Jul 31 17:34:06 optiplex gnome-remote-de[2585]: RDP server started
  Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] 
[2585:2622] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
  Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] 
[2585:2622] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
  Jul 31 17:35:08 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:572] 
[2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status 
SEC_I_CONTINUE_NEEDED [0x00090312]
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:573] 
[2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status 
SEC_I_COMPLETE_NEEDED [0x00090313]
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 104: Connection reset by peer
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.nla] - [nla_recv] error: -1
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - client authentication failure
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.peer] - peer_recv_callback: 
CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - transport_check_fds: 
transport->ReceiveCallback() - -1
  Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2585] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a 
system error 32: Broken pipe
  Jul 31 17:35:13 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] 
[2585:2642] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] 
[2585:2642] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
  Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.crypto] - invalid private key
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.core.peer] - peer_recv_callback: 
CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.core.transport] - transport_check_fds: 
transport->ReceiveCallback() - -1
  Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] 
[2585:2652] [WARN][com.freerdp.core.connection] - server supports only NLA 
Security
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] 
[2585:2652] [ERROR][com.freerdp.core.connection] - Protocol security 
negotiation failure
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:578] 
[2585:2662] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
  Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:578] 

[Desktop-packages] [Bug 1983199] [NEW] Unable to connect to Ubuntu running RDP based remote desktop

2022-07-31 Thread Adam Baxter
Public bug reported:

Initial setup: machine was headless, set up TLS using openssl, set key location 
using grdctl.
Windows RDP client was unable to connect - journalctl showed that the username 
was unable to be retreived (from dbus?).

Set password using grdctl /
https://gitlab.gnome.org/-/snippets/1778#note_1515700

Plugged a monitor and keyboard in, checked Settings and the password was
garbage. Reset the password, re-enabled RDP and the Windows client was
still unable to connect:

```
Jul 31 17:34:06 optiplex gnome-remote-de[2585]: RDP server started
Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] 
[2585:2622] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] 
[2585:2622] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Jul 31 17:35:08 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:572] 
[2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status 
SEC_I_CONTINUE_NEEDED [0x00090312]
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:573] 
[2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status 
SEC_I_COMPLETE_NEEDED [0x00090313]
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 104: Connection reset by peer
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.nla] - [nla_recv] error: -1
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - client authentication failure
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.peer] - peer_recv_callback: 
CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2612] [ERROR][com.freerdp.core.transport] - transport_check_fds: 
transport->ReceiveCallback() - -1
Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] 
[2585:2585] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a 
system error 32: Broken pipe
Jul 31 17:35:13 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] 
[2585:2642] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] 
[2585:2642] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.crypto] - invalid private key
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.core.peer] - peer_recv_callback: 
CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] 
[2585:2632] [ERROR][com.freerdp.core.transport] - transport_check_fds: 
transport->ReceiveCallback() - -1
Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] 
[2585:2652] [WARN][com.freerdp.core.connection] - server supports only NLA 
Security
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] 
[2585:2652] [ERROR][com.freerdp.core.connection] - Protocol security 
negotiation failure
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:578] 
[2585:2662] [ERROR][com.freerdp.core.transport] - BIO_read returned a system 
error 0: Success
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:578] 
[2585:2662] [ERROR][com.freerdp.core] - 
transport_read_layer:freerdp_set_last_error_ex 
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file 
descriptor, closing connection
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:580] 
[2585:2652] [ERROR][com.freerdp.core.peer] - peer_recv_callback: 
CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail
Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:580] 
[2585:2652] 

[Desktop-packages] [Bug 1983196] Dependencies.txt

2022-07-31 Thread corrado venturini
apport information

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

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  Starting cheese i have a message:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller
  than 65535 pixels are not supported

  and after many seconds:
  (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
  becaause the hook creates a bug against linux instead cheese.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 31 08:47:35 2022
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  Package: cheese 41.1-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983196/+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 1983196] ProcEnviron.txt

2022-07-31 Thread corrado venturini
apport information

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

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  Starting cheese i have a message:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller
  than 65535 pixels are not supported

  and after many seconds:
  (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
  becaause the hook creates a bug against linux instead cheese.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 31 08:47:35 2022
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  Package: cheese 41.1-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983196/+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 1983196] ProcCpuinfoMinimal.txt

2022-07-31 Thread corrado venturini
apport information

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

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  Starting cheese i have a message:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller
  than 65535 pixels are not supported

  and after many seconds:
  (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
  becaause the hook creates a bug against linux instead cheese.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 31 08:47:35 2022
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  Package: cheese 41.1-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983196/+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 1983196] [NEW] Cheese Internal data stream error

2022-07-31 Thread corrado venturini
Public bug reported:

Starting cheese i have a message:
corrado@corrado-n4-kk-0718:~$ cheese

(cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller than
65535 pixels are not supported

and after many seconds:
(cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)

NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
becaause the hook creates a bug against linux instead cheese.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: cheese 41.1-2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 31 08:47:35 2022
InstallationDate: Installed on 2022-07-19 (12 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
SourcePackage: cheese
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-07-19 (12 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
Package: cheese 41.1-2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Tags:  wayland-session kinetic
Uname: Linux 5.15.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
_MarkForUpload: True

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


** Tags: amd64 apport-bug apport-collected kinetic wayland-session

** Tags added: apport-collected

** Description changed:

  Starting cheese i have a message:
  corrado@corrado-n4-kk-0718:~$ cheese
  
  (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller than
  65535 pixels are not supported
  
  and after many seconds:
  (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  
  NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
  becaause the hook creates a bug against linux instead cheese.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 31 08:47:35 2022
  InstallationDate: Installed on 2022-07-19 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.22.0-0ubuntu4
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2022-07-19 (12 days ago)
+ InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
+ Package: cheese 41.1-2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
+ Tags:  wayland-session kinetic
+ Uname: Linux 5.15.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
+ _MarkForUpload: True

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  New

Bug description:
  Starting cheese i have a message:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller
  than 65535 pixels are not supported

  and after many seconds:
  (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  NOTE: to create this bug report i removed the apport package hook provided by 
cheese and located in /usr/share/apport/package-hooks/source_cheese.py. 
  becaause the hook creates a bug against linux instead cheese.

  ProblemType: 

[Desktop-packages] [Bug 1968855] Re: apport fails when trying to report a problem about Cheese

2022-07-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cheese (Ubuntu)
   Status: New => Confirmed

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

Title:
  apport fails when trying to report a problem about Cheese

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com)[1].

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  [1] https://gitlab.gnome.org/GNOME/cheese/-/issues/139

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