[Desktop-packages] [Bug 1966501] Re: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()

2022-03-27 Thread corrado venturini
Just firefox open.

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

Title:
  xdg-desktop-portal crashed with SIGSEGV in
  g_cclosure_marshal_generic()

Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  closure_marshal_generic()

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:11:56 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  SegvAnalysis:
   Segfault happened at: 0x556025d66421:mov0x8(%rax),%rcx
   PC (0x556025d66421) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966501/+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 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3

2022-03-27 Thread David Ward
The drivers from Epson are not part of Ubuntu. You will need to obtain
support for them from Epson.

** Changed in: sane-backends (Ubuntu)
   Status: New => Invalid

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

Title:
  New Epson V19 scanner problems under Ubuntu 18.04.3

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  Bought new Epson V19 scanner, and it works fine on my wife's computer
  running Windows 7, and also on my computer running Windows XP.
  Rebooted my computer into Ubuntu 18.04.3, and installed the driver
  packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64
  bit, release date 12-26-2019) using their install.sh file with the
  without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650
  1.0.2, and imagescan-plugin-ocr-engine 1.0.2).  Looking at these
  packages using Aptitude, it appears that they are installed OK with no
  missing dependencies.  Imagescan (on the graphical desktop) appears to
  find the scanner, and when you click to scan, you can hear the scanner
  seeming to run normally, but no image is produced at the end.  Using
  the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to
  work fine for finding the scanner.  But when I try scanimage -T, no
  image file is produced, although you can hear the scanner appearing to
  do a normal scan.  So it appears that all the control functions are
  working fine, but the problem is getting the scan data.  I also tried
  the suggestions in this video
  (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04
  scanner problems how to fix them" concerning bug 1728012.  In the end,
  nothing appears to have changed, so it appears I didn't make it any
  better or any worse.  Any help would be greatly appreciated, including
  referring me to another place if I'm not posting in the right place
  yet.  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+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 1645116] Re: [Brother DCP-J715W] core dumped executing scanimage -L

2022-03-27 Thread David Ward
brscan is not part of Ubuntu. You will need to obtain support for it
from Brother.

If there is currently an issue involving the built-in drivers from the
sane-backends package, please change the status back.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [Brother DCP-J715W] core dumped executing scanimage -L

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  In Xubuntu 16.10 I get a core dump executing via a terminal:
  scanimage -L
  Erreur de segmentation (core dumped)

  Errors report:
  https://errors.ubuntu.com/oops/f494063a-bdc2-11e6-ad54-fa163e30221b

  With Xubuntu 16.04 I don't have this problem:
  scanimage -L
  device `brother3:net1;dev0' is a Brother DCP-J715W DCP-J715W

  The Brother DCP-J715W device is WiFi connected to my router. All the
  clients access the device via the network.

  I installed the latest Brother software on the client from their website:
  
http://support.brother.com/g/b/downloadlist.aspx?c=fr=fr=dcpj715w_eu_as=128=English

  sudo dpkg -i  brscan3-0.2.13-1.amd64.deb
  sudo brsaneconfig3 -a name=scanner model=DCP-J715W ip=192.168.1.27
  sudo brsaneconfig3 -p
  cd /usr/lib64/
  sudo cp -r . /usr/lib

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: sane-utils 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 27 18:13:36 2016
  InstallationDate: Installed on 2016-11-22 (4 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1645116/+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 1512027] Re: open of device pixma:MX7600_... failed: invalid argument

2022-03-27 Thread David Ward
All currently supported versions of Ubuntu have sane-backends 1.0.27 or
later.

If this issue still occurs with a Pixma MX7600, please change the status
of this bug back.

For any device except a Pixma MX7600 that currently shows a similar
issue, please open a separate bug. Do not comment on this one.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  open of device pixma:MX7600_... failed: invalid argument

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Up until recently, I've been able to scan fine with my Canon Pixma
  MX7600. Then I upgraded to Ubuntu Wily and I've started getting:

  $ scanimage
  scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument

  The device pings and I can get to its HTTP port. Everything appears
  OK.

  If I run

  strace -f -s 256 -o /tmp/trace.txt scanimage

  the relevant output appears to be:

  socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204
  connect(204, {sa_family=AF_INET, sin_port=htons(8612),
  sin_addr=inet_addr("192.168.2.107")}, 16) = 0
  sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16
  select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257})
  recvfrom(204, 
"BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k",
  2048, 0, NULL, N
  ULL) = 32
  close(204)
  write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed:
  Invalid argument\n", 78) = 78

  It appears to me that the scanner is responding but the driver doesn't
  like the response. I'm running sane 1.0.14-11 and sane-utils
  1.0.25+git201505.

  WORKAROUND: Use the PPA from
  https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+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 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-27 Thread Stephen Carr
** Attachment added: "Bluetootth entries from boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+attachment/5573582/+files/BT-LOG.txt

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

Title:
  Flood of Bluetooth Malicious advertisind data

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  This problem occurred with the  ugrade of the kernel to patch level
  105.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:48:22 2022
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-06-21 (1370 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_AU.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+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 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-27 Thread Stephen Carr
I had to reboot my laptop and for a while there seemed no problem the
flood of Malicious data in the system log - then suddenly it started
again at the rate of 17,000 lines per hour.

The Bluetooth device is part of the Intel AC1365 combo unit.

I have attached the start of the boot log and a filtered log with just
the Bluetooth entries.


** Attachment added: "Boot log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+attachment/5573581/+files/BOOT-LOG.txt

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

Title:
  Flood of Bluetooth Malicious advertisind data

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  This problem occurred with the  ugrade of the kernel to patch level
  105.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:48:22 2022
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-06-21 (1370 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_AU.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+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 1966440] Re: gnome-shell crashes often when using the menu (start) button

2022-03-27 Thread Daniel van Vugt
The first crash in your log is bug 1782984. You can avoid that by
logging into 'Ubuntu on Wayland'.

The remaining crashes (signal 11) I can't yet identify so please follow these 
instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Your package update problem seems to be caused by either:
 * PPAs
 * the 'proposed' pocket
 * a broken upgrade for other reasons.

If you can't fix it then please just reinstall Ubuntu from scratch and
be careful to never use PPAs and never enable 'proposed'.



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

** Tags added: focal

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

Title:
  gnome-shell crashes often when using the menu (start) button

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  
  I upgraded from 20.04 LTS

  
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 42~beta-1ubuntu3
Version table:
   42~beta-1ubuntu3 500
  500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
   *** 3.36.9-0ubuntu0.20.04.2 100
  100 /var/lib/dpkg/status

  
  When I press the "windows" key and start searching for an app this works 
fine, and I can launch the app. However immediately afterwards all windows 
freeze, loose their decoration/position. Then the  screen flashes and we're 
back. All notification in the queue pop up again as well.

  It happens almost every time.

  I checked the PID of the gnome-shell in top, and it effectively changes so I 
believe the gnome-shell crashes. It shouldn't. 
  How can I collect relevant debug info?
  I cannot seem to find a cause.
  I'm using nvidia-drivers if that matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 13:21:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-28 (177 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966440/+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 1965535] Re: Stop recommending snap

2022-03-27 Thread gui ambros
+1, I would also strongly prefer that Ubuntu stops adopting snap by
default, or at least give users the option to use other deb/apt
alternatives. I respect the work done by snap developers, but given its
current state breaking XDG standards, forced app updates, and impact on
size/performance, I don't believe it's ready for prime time (nor will be
anytime soon).

I've been a loyal Ubuntu user for almost 15 years, but this would make
me reconsider and switching to another distro. I don't say this as any
form of pressure, but to indicate how strongly I feel about this issue.
Judging by the size of this other thread [1], I'd venture many other
users feel equally about this.

[1] https://bugs.launchpad.net/snapd/+bug/1575053

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

Title:
  Stop recommending snap

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Currently, ubuntu recommends installing snap by default, and some apps
  are slowly transitioning from DEB-based installation to Snap-based
  installation.

  APT is great, and facilitates having a clean, maintainable system.

  The snap project is not very well designed or engineered (just
  changing the location of where snap data is located is taking the
  project more than 5 years because it was hardcoded:
  https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and
  VERY slow. The design of snap, as well as the way that decisions are
  made, are very questionable, and are receiving increasing amounts of
  criticism.

  I'd like to request that Ubuntu stops recommending snap, stops
  transitioning towards snaps, and we come back to defaulting to
  DEB/APT-based installation for all apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1964916] Re: I am having a wierd display glitch

2022-03-27 Thread Daniel van Vugt
If the problem occurs in Wayland and also after uninstalling the old
driver, then it sounds like either a kernel bug or a hardware connection
problem.

It looks like this is a desktop but with a laptop screen. Is that right?

** Package changed: xserver-xorg-video-intel (Ubuntu) => linux-hwe-5.11
(Ubuntu)

** Summary changed:

- I am having a wierd display glitch
+ [Sandy Bridge] Flickering white lines on screen

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

Title:
  [Sandy Bridge] Flickering white lines on screen

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  https://www.youtube.com/watch?v=GcAXAicoZqY

  this is the video of my error
  i am having this issue on all versions of ubuntu-- i have tried installing 
versions 20.04, 18.04.06, 12.04..
  i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I 
used Windows 10 on my PC but i thought of switching to ubuntu when this problem 
arose.. The glitch shows up on ubuntu splash screen and remains there until i 
restart my pc with nomodeset parameter...i have reinstalled windows 10 but i 
want this issue to get fixed.. i need to use ubuntu ...pls

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 14:59:57 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ac5]
  InstallationDate: Installed on 2022-03-05 (9 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Hewlett-Packard 120-2110il
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: LEO_707
  dmi.board.name: 2AC5
  dmi.board.vendor: Quanta
  dmi.board.version: 101
  dmi.chassis.asset.tag: 4CS2040B0F
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 120-2110il
  dmi.product.sku: QF135AA#ACJ
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+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 1944369] Re: Crash with fprintd 1.92.0

2022-03-27 Thread Launchpad Bug Tracker
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu1

---
libfprint (1:1.94.3+tod1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1944369)
  * debian/libfprint-2-2.postinst: Devices triggers updated
  * debian/libfprint-2-tod1.symbols: Add new symbols
  * debian/docs: Update README name to use markdown file
  * tod: Ensure we install tod-macros.h header

 -- Marco Trevisan (Treviño)   Sun, 27 Mar 2022
23:48:11 +0200

** Changed in: libfprint (Ubuntu)
   Status: New => Fix Released

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

Title:
  Crash with fprintd 1.92.0

Status in libfprint-2-tod1-goodix:
  Opinion
Status in OEM Priority Project:
  Confirmed
Status in libfprint package in Ubuntu:
  Fix Released

Bug description:
  When using this with fprintd 1.92.0 and onwards I get:

  /usr/lib/fprintd: symbol lookup error: /usr/lib/fprintd: undefined
  symbol: fp_device_has_feature, version LIBFPRINT_2.0.0

  See more comments here:
  https://aur.archlinux.org/packages/libfprint-2-tod1-xps9300-bin/

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369/+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 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from

2022-03-27 Thread Daniel van Vugt
Please open a new bug about the Wayland problem by running:

  ubuntu-bug gnome-shell

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

Title:
  [focal] Xorg crashed with assertion failure (usually in a VM) at
  [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized'
  failed] and call stack comes from DRIMoveBuffersHelper

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashed with assertion failure (usually in a VM):

  privates.h:121: dixGetPrivateAddr: Assertion `key->initialized'
  failed.

  and call stack comes from DRIMoveBuffersHelper

  WORKAROUND

  Select 'Ubuntu on Wayland' on the login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+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 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

2022-03-27 Thread Daniel van Vugt
Certainly using nvidia-driver-470 will avoid this crash. Although
choosing 'Ubuntu on Xorg' at the login screen with nvidia-driver-510
should avoid it too.

P.S. GNOME Shell refers to the integrated GPU (Intel) as primary
(because it's attached to the screen), and the more powerful GPU
(usually not wired to the screen) is the secondary.

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

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  This is on my weird desktop setup, with one monitor plugged into an
  AMD card and one into an NVIDIA card.

  When using the Wayland session, by default Shell will come up on the
  monitor connected to the AMD card, and the second (NVIDIA) monitor
  will be blank. Attempting to enable the second monitor in Display
  Settings will immediately and reproducibly crash gnome-shell.

  This is trivial for me to reproduce, so if you need patches tested I
  can easily do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 
5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2
  Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 09:37:51 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-11-02 (125 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1964037/+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 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-27 Thread Daniel van Vugt
I can't seem to reproduce the problem, and bug 1966443 doesn't appear to
be relevant. Please repeat the steps in comment #3...

My new theory is that the upgrade to Mesa 22 you mention in comment #5
is showing a crash in Mesa itself (which will crash GTK4 apps like
gnome-extensions-app). Because Ivy Bridge Intel GPUs like yours have
been switched to a new driver in Mesa 22 and we haven't had time to
really test that new driver yet.

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966221/+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 1966443] Re: I can't start it

2022-03-27 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1965897 ***
https://bugs.launchpad.net/bugs/1965897

** Description changed:

- For "https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966221;
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 21:29:03 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1647578316
  GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' 
b"['Utilities', 'YaST']"
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/xiaozhangup
  ProcEnviron:
-  LANG=zh_CN.UTF-8
-  LANGUAGE=zh_CN:zh
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=zh_CN.UTF-8
+  LANGUAGE=zh_CN:zh
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo

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

Title:
  I can't start it

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 21:29:03 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1647578316
  GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' 
b"['Utilities', 'YaST']"
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/xiaozhangup
  ProcEnviron:
   LANG=zh_CN.UTF-8
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966443/+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 1966570] Re: 60fps video is choppy in firefox 98 and ubuntu 21.10

2022-03-27 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)

** Also affects: kwin (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- 60fps video is choppy in firefox 98 and ubuntu 21.10
+ 60fps video is choppy in firefox 98 and Kubuntu 21.10

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

Title:
  60fps video is choppy in firefox 98 and Kubuntu 21.10

Status in firefox package in Ubuntu:
  New
Status in kwin package in Ubuntu:
  New

Bug description:
  I have tried many browsers and all have low choppy 60fps videos with
  the browsers.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Mar 26 21:47:15 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Intel(R) Client Systems NUC10i3FNH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7ef8b16e-5e8c-4890-bc8a-e9705ec6b22b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0055.2021.1202.1748
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i3FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61362-303
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0055.2021.1202.1748:bd12/02/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i3FNH:pvrK61356-304:rvnIntelCorporation:rnNUC10i3FNB:rvrK61362-303:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i3FNHFA:
  dmi.product.family: FN
  dmi.product.name: NUC10i3FNH
  dmi.product.sku: BXNUC10i3FNHFA
  dmi.product.version: K61356-304
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~i
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203260600.ae710f~oibaf~i
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966570/+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 656478] Re: Init script for saned is spammy on default install needlessly

2022-03-27 Thread Mario Limonciello
** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Init script for saned is spammy on default install needlessly

Status in sane-backends package in Ubuntu:
  Won't Fix

Bug description:
  The default install of Maverick installs sane-utils which provides an
  init script for saned.  It's disabled by default, but on every boot
  spams the VT with

  
  echo "$NAME disabled; edit /etc/default/saned"

  Looking at how simple the init script and /etc/default/saned are, I would 
contend that this should either:
  1) Be converted to an upstart script that's not enabled by default
  or
  2) Remove the line that tells the user that saned is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656478/+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 1966614] [NEW] I am getting calendar notification pop-ups even though I've turned them off

2022-03-27 Thread Jonathan Kamens
Public bug reported:

I keep getting calendar notification pop-ups -- at the top middle of my
screen -- even though in the calendar settings in Notifications I have
"Notification Popups" turned off.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.2-3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 27 20:20:15 2022
InstallationDate: Installed on 2019-08-16 (954 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to jammy on 2021-11-09 (138 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-calendar (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 gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1966614

Title:
  I am getting calendar notification pop-ups even though I've turned
  them off

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I keep getting calendar notification pop-ups -- at the top middle of
  my screen -- even though in the calendar settings in Notifications I
  have "Notification Popups" turned off.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-calendar 41.2-3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 20:20:15 2022
  InstallationDate: Installed on 2019-08-16 (954 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to jammy on 2021-11-09 (138 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1966614/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-03-27 Thread Mathieu Pillard
Not sure if this is filed under the right package (is this a
driver/kernel issue ?), but I can reproduce with Intel TigerLake-LP GT2
hardware - it used to work from Ubuntu 20.04 to 21.10, and fails with
22.04 alpha, even from the Live 20220326 ISO.

vainfo shows the same thing as original post:
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1427515] Re: "service saned status" fails unless called from root

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  "service saned status" fails unless called from root

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I observed the following on my trusty machine.

  $ service saned status
  /etc/init.d/saned: 73: [: =: unexpected operator
  saned is not running, but pidfile existed.
  rm: remove write-protected regular file ‘/var/run/saned.pid’? n

  $ sudo service saned status
  saned is running.

  
  In other words, the status call fails unless done from root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1427515/+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 1391038] Re: simple-scan does not recognize canon LiDE30 scanner

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  simple-scan does not recognize canon LiDE30 scanner

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Mint 16 *and* Mint 17
  Plug in USB scanner, start simple scan. It shows a spinner but never connects 
and scans.
  Strangely, the scanner is shown properly in the preferences!
  Canon CanoScan N1240U/LiDE30
  The scanner makes some noises but does not scan.

  This used to work under Mint16 until some upgrade pooched it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1391038/+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 1384303] Re: Cannot scan using Canon Lide 25 with simple-scan on 14.04. on USB 3.0, USB 2.0 works

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  Cannot scan using Canon Lide 25 with simple-scan on 14.04. on USB 3.0,
  USB 2.0 works

Status in sane-backends package in Ubuntu:
  Incomplete
Status in simple-scan package in Ubuntu:
  Incomplete
Status in Debian:
  Fix Released

Bug description:
  I do a clean install UBuntu 14.04, but unable to scan via simple-scan with 
error "Failed to scan, unable to start scan".
  The scanner (Canon Lide 25) was detected properly on lsusb, and working fine 
via VirtualBox.

  Previously using Lubuntu 13.10, simple-scan able to scan perfectly.

  $ lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc. 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. 
  Bus 003 Device 005: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25
  Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
  Bus 003 Device 002: ID 046d:c52e Logitech, Inc. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy simple-scan
  simple-scan:
Installed: 3.12.1-0ubuntu1
Candidate: 3.12.1-0ubuntu1
Version table:
   *** 3.12.1-0ubuntu1 0
  500 http://id.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.12.0-0ubuntu1 0
  500 http://id.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: simple-scan 3.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 22 22:18:36 2014
  DriverPackageVersions:
   libsane 1.0.23-3ubuntu3.1
   libsane-extras N/A
   hplip 3.14.3-0ubuntu3.2
   hpoj N/A
  InstallationDate: Installed on 2014-08-29 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=6ae128c4-d0aa-401f-8057-102dea6e8953 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: H87M-ITX
  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.:bvrP2.00:bd07/04/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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/sane-backends/+bug/1384303/+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 1427519] Re: stopping the service does not remove PID file

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  stopping the service does not remove PID file

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  From my trusty machine:

  $ sudo service saned start ; sudo service saned stop ; sudo service saned 
status
  Starting SANE network scanner server: saned.
  Stopping SANE network scanner server: saned.
  saned is not running, but pidfile existed.

  Running the status call once more after that will reveal that the PID
  file is now gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1427519/+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 1222162] Re: scanimage crashed with SIGSEGV in _int_malloc()

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  scanimage crashed with SIGSEGV in _int_malloc()

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Not a issue in 13.04
  Also 10.0.0.50 is running 13.04
  This does not have a 100% reproduction rate, sometimes it hangs indefinitely 
and some times it works
  Terminal output, last 6 lines matter, the rest proves it should work
  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
  
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:004:002","NAME":"UMAX 
3400 flatbed 
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
 Deskjet_F4400_series all-in-one"},
  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d 
'net:10.0.0.50:plustek:libusb:004:002'
  Usage: scanimage [OPTION]...

  Start image acquisition on a scanner device and write image data to
  standard output.

  Parameters are separated by a blank from single-character options (e.g.
  -d epson) and by a "=" from multi-character options (e.g. 
--device-name=epson).
  -d, --device-name=DEVICE   use a given scanner device (e.g. hp:/dev/scanner)
  --format=pnm|tiff  file format of output file
  -i, --icc-profile=PROFILE  include this ICC profile into TIFF file
  -L, --list-devices show available scanner devices
  -f, --formatted-device-list=FORMAT similar to -L, but the FORMAT of the output
 can be specified: %d (device name), %v (vendor),
 %m (model), %t (type), %i (index number), and
 %n (newline)
  -b, --batch[=FORMAT]   working in batch mode, FORMAT is `out%d.pnm' or
 `out%d.tif' by default depending on --format
  --batch-start=#page number to start naming files with
  --batch-count=#how many pages to scan in batch mode
  --batch-increment=#increase page number in filename by #
  --batch-double increment page number by two, same as
 --batch-increment=2
  --batch-prompt ask for pressing a key before scanning a page
  --accept-md5-only  only accept authorization requests using md5
  -p, --progress print progress messages
  -n, --dont-scanonly set options, don't actually scan
  -T, --test test backend thoroughly
  -A, --all-options  list all available backend options
  -h, --help display this help message and exit
  -v, --verbose  give even more status messages
  -B, --buffer-size=#change input buffer size (in kB, default 32)
  -V, --version  print version information

  Options specific to device `net:10.0.0.50:plustek:libusb:004:002':
Scan Mode:
  --mode Lineart|Gray|Color [Color]
  Selects the scan mode (e.g., lineart, monochrome, or color).
  --depth 8|14bit [8]
  Number of bits per sample, typical values are 1 for "line-art" and 8
  for multibit scans.
  --source Normal|Transparency|Negative [inactive]
  Selects the scan source (such as a document-feeder).
  --resolution 50..1200dpi [50]
  Sets the resolution of the scanned image.
  --preview[=(yes|no)] [no]
  Request a preview-quality scan.
Geometry:
  -l 0..215mm [0]
  Top-left x position of scan area.
  -t 0..297mm [0]
  Top-left y position of scan area.
  -x 0..215mm [103]
  Width of scan-area.
  -y 0..297mm [76.21]
  Height of scan-area.
Enhancement:
  --brightness -100..100% (in steps of 1) [0]
  Controls the brightness of the acquired image.
  --contrast -100..100% (in steps of 1) [0]
  Controls the contrast of the acquired image.
  --custom-gamma[=(yes|no)] [no]
  Determines whether a builtin or a custom gamma-table should be used.
  --gamma-table 0..255,... [inactive]
  Gamma-correction table.  In color mode this option equally affects the
  red, green, and blue channels simultaneously (i.e., it is an intensity
  gamma 

[Desktop-packages] [Bug 1225027] Re: scanimage crashed with SIGSEGV in __libc_message()

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  scanimage crashed with SIGSEGV in __libc_message()

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Yet another crash in a different section
  This crash occurred yesterday, all i did was print out a list of devices and 
try to get help data output from the device

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: sane-utils 1.0.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in `scanimage': double free or corruption (top): 
0x02058f50 ***
  CrashCounter: 1
  Date: Thu Sep 12 22:48:40 2013
  ExecutablePath: /usr/bin/scanimage
  InstallationDate: Installed on 2013-07-27 (47 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
  MarkForUpload: True
  ProcCmdline: scanimage --help -d net:10.0.0.50:plustek:libusb:004:002
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f502e96a6a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x2058f50, str=0x7f502e96a7b0 "double free or 
corruption (top)", action=3) at malloc.c:4902
   _int_free (av=, p=0x2058f40, have_lock=0) at malloc.c:3758
   _IO_new_fclose (fp=0x2058f50) at iofclose.c:85
   internal_endent () at nss_files/files-XXX.c:161
  Title: scanimage crashed with SIGSEGV in __libc_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1225027/+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 1165713] Re: gscan2pdf crashed with SIGSEGV in clamp_value()

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  gscan2pdf crashed with SIGSEGV in clamp_value()

Status in gscan2pdf package in Ubuntu:
  Incomplete
Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I have changed the options for scanning and then crashed gscan2pdf
  complete.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gscan2pdf 1.0.4-5
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Apr  7 12:23:16 2013
  ExecutablePath: /usr/bin/gscan2pdf
  InstallationDate: Installed on 2011-07-08 (639 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/perl
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl /usr/bin/gscan2pdf
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f45c3e96bf3:mov(%r11,%rsi,4),%r8d
   PC (0x7f45c3e96bf3) ok
   source "(%r11,%rsi,4)" (0x7f45e254e000) in non-readable VMA region: 
0x7f45e254e000-0x7f45e254f000 ---p None
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: gscan2pdf
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1
   sane_pixma_control_option () from 
/usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1
   XS_Sane__Device_set_option () from /usr/lib/perl5/auto/Sane/Sane.so
   ?? ()
   ?? ()
  Title: gscan2pdf crashed with SIGSEGV in sane_pixma_control_option()
  UpgradeStatus: Upgraded to raring on 2013-04-06 (0 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1165713/+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 1070987] Re: scanimage crashed with signal 5 in _dl_sysinfo_int80()

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  scanimage crashed with signal 5 in _dl_sysinfo_int80()

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I was just trying to use scanimage.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: sane-utils 1.0.22-7ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Uname: Linux 3.2.0-32-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  Date: Wed Oct 24 22:22:41 2012
  ExecutablePath: /usr/bin/scanimage
  ProcCmdline: scanimage
  Signal: 5
  SourcePackage: sane-backends
  StacktraceTop:
   _dl_sysinfo_int80 () from /lib/ld-linux.so.2
   ___newselect_nocancel () at ../sysdeps/unix/syscall-template.S:82
   ?? () from /lib/i386-linux-gnu/libusb-0.1.so.4
   sanei_usb_write_bulk () from /usr/lib/i386-linux-gnu/sane/libsane-epson2.so.1
   e2_send () from /usr/lib/i386-linux-gnu/sane/libsane-epson2.so.1
  Title: scanimage crashed with signal 5 in _dl_sysinfo_int80()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare tape video
  modified.conffile..etc.default.saned: [modified]
  mtime.conffile..etc.default.saned: 2012-06-24T18:14:13.191201

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1070987/+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 1081415] Re: package sane-utils 1.0.22-7ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  package sane-utils 1.0.22-7ubuntu1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 2

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I don't know anymore other than it would not install
  12x

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: sane-utils 1.0.22-7ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic-pae 3.2.33
  Uname: Linux 3.2.0-34-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Tue Nov 20 16:38:09 2012
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 2
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  SourcePackage: sane-backends
  Title: package sane-utils 1.0.22-7ubuntu1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
  UpgradeStatus: Upgraded to precise on 2012-11-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1081415/+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 1208091] Re: scanimage assert failure: *** Error in `scanimage': double free or corruption (top): 0x0000000002598130 ***

2022-03-27 Thread David Ward
** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  scanimage assert failure: *** Error in `scanimage': double free or
  corruption (top): 0x02598130 ***

Status in sane-backends package in Ubuntu:
  Incomplete
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Similar errors occur when the normal user runs this command
  Accessing sacnner using network, setup notes are here
  http://ubuntuforums.org/showthread.php?t=1519201
  My other virtualbox client has no issue here
  the server is running xubuntu 13.04
  This output is from the saucy client

  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
  
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:003:002","NAME":"UMAX 
3400 flatbed 
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
 Deskjet_F4400_series all-in-one"},
  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d 
'net:10.0.0.50:plustek:libusb:003:002'
  *** Error in `scanimage': double free or corruption (top): 0x02598130 
***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x80996)[0x7f4379829996]
  /lib/x86_64-linux-gnu/libc.so.6(fclose+0x14d)[0x7f43798179bd]
  
/lib/x86_64-linux-gnu/libnss_files.so.2(_nss_files_getservbyname_r+0x11b)[0x7f4373df7adb]
  /lib/x86_64-linux-gnu/libc.so.6(getservbyname_r+0xd2)[0x7f43798bf022]
  /lib/x86_64-linux-gnu/libc.so.6(+0xcb72b)[0x7f437987472b]
  /lib/x86_64-linux-gnu/libc.so.6(+0xcba93)[0x7f4379874a93]
  /lib/x86_64-linux-gnu/libc.so.6(getaddrinfo+0xf4)[0x7f4379878d74]
  /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(+0x6c3c)[0x7f437939cc3c]
  
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(sane_net_init+0x428)[0x7f437939d438]
  /usr/lib/x86_64-linux-gnu/libsane.so.1(+0x3b00)[0x7f4379b73b00]
  /usr/lib/x86_64-linux-gnu/libsane.so.1(sane_dll_open+0xe2)[0x7f4379b74842]
  scanimage[0x401fa8]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f43797cade5]
  scanimage[0x403924]
  === Memory map: 
  0040-0040a000 r-xp  08:01 1355   
/usr/bin/scanimage
  0060a000-0060b000 r--p a000 08:01 1355   
/usr/bin/scanimage
  0060b000-0060c000 rw-p b000 08:01 1355   
/usr/bin/scanimage
  0258d000-025ae000 rw-p  00:00 0  
[heap]
  7f4373bdd000-7f4373bf2000 r-xp  08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373bf2000-7f4373df1000 ---p 00015000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df1000-7f4373df2000 r--p 00014000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df2000-7f4373df3000 rw-p 00015000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df3000-7f4373dff000 r-xp  08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373dff000-7f4373ffe000 ---p c000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373ffe000-7f4373fff000 r--p b000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373fff000-7f437400 rw-p c000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f437400-7f4374021000 rw-p  00:00 0 
  7f4374021000-7f437800 ---p  00:00 0 
  7f437810e000-7f437810f000 ---p  00:00 0 
  7f437810f000-7f437890f000 rw-p  00:00 0  
[stack:17829]
  7f437890f000-7f4378916000 r-xp  08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378916000-7f4378b15000 ---p 7000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b15000-7f4378b16000 r--p 6000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b16000-7f4378b17000 rw-p 7000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b17000-7f4378b5b000 r-xp  08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378b5b000-7f4378d5a000 ---p 00044000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5a000-7f4378d5b000 r--p 00043000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5b000-7f4378d5c000 rw-p 00044000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5c000-7f4378d73000 r-xp  08:01 1617   
/lib/x86_64-linux-gnu/libpthread-2.17.so
  7f4378d73000-7f4378f73000 ---p 00017000 08:01 1617

[Desktop-packages] [Bug 940063] Re: Add "iscan" configuration to Jockey

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: jockey
   Status: Incomplete => Invalid

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

Title:
  Add "iscan" configuration to Jockey

Status in Jockey:
  Invalid
Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I was trying to access my all-in-one Epson EP804AW's scanner through a
  WiFi network.

  This does not work out of the box.

  I had found instructions for generically enabling scan over WifI for epson by 
adding, in /etc/sane.d/epson2.conf:
  net 255.255.255.255 # using the printer's IP

  This is INCORRECT for the EP804AW.

  It caused Simple Scan and xsane to crash (hence the sane-backends bug report).
  It also locked up the EP804AW, which had to be power-cycled and recalibrated.

  I found the correct method in this guide:

  http://edgar.tumblr.com/post/1425668485/scanning-over-wifi-from-an-
  epson-tx550w-using-ubuntu

  This procedure could be simplified by installing the avasys "iscan"
  drivers from jockey.

  Jockey already provides installation options for avasys's printer
  drivers.

  Please include this in Jockey to improve user experience and prevent
  possible damage to hardware.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: sane-utils 1.0.22-7ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Fri Feb 24 12:35:43 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/scanimage
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: scanimage -L
  SegvAnalysis:
   Segfault happened at: 0x7fe5047f07e0:mov0x8(%rsi),%rax
   PC (0x7fe5047f07e0) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: scanimage crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  mtime.conffile..etc.default.saned: 2012-02-14T15:31:24.882599

To manage notifications about this bug go to:
https://bugs.launchpad.net/jockey/+bug/940063/+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 1022650] Re: scanimage -L fails with segmentation error double free

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  scanimage -L fails with segmentation error double free

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Since my upgrade to precise-amd64 from lucid-i386 I'm not able to scan
  anymore. I suspect that the problem is amd64 specific.

  [32568.242721] usb 3-1: new full-speed USB device number 3 using xhci_hcd
  [32568.320350] Did not find alt setting 1 for intf 0, config 1

  33164.011589] scanimage[26665]: segfault at 7fa7d4698275 ip
  7fa7d3f35fde sp 7fffa0e1b4b0 error 6 in
  libc-2.15.so[7fa7d3eb6000+1b3000]

  
  [ 5652.907318] xsane[10518]: segfault at 3 ip 7fd1f64c1b5d sp 
7fff4a48e020 error 4 in libsane-net.so.1.0.22[7fd1f64ba000+e000]

  [ 6790.527904] iscan[10667] general protection ip:7f5c9d128b5d
  sp:7fff640d76b0 error:0 in libsane-net.so.1.0.22[7f5c9d121000+e000]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: sane-utils 1.0.22-7ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Mon Jul  9 19:19:20 2012
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.saned: 2012-07-07T19:14:37.983873
  mtime.conffile..etc.sane.d.saned.conf: 2012-07-07T16:55:04.553123

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1022650/+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 604798] Re: scanimage --batch crashed with SIGSEGV in gt68xx_line_reader_free_delays()

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  scanimage --batch crashed with SIGSEGV in
  gt68xx_line_reader_free_delays()

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I'm using SANE with a Mustek BearPaw 1200CU Plus scanner, using the
  firmware from  (MD5 f2f275c5a8ad5dbdc43793f046612417).
  When I run "scanimage --batch", scanimage segfaults after scanning the
  first page and returning the head to the home position:

  bjh21@sole:~$ scanimage --batch
  Scanning -1 pages, incrementing by 1, numbering from 1
  Scanning page 1
  Scanned page 1. (scanner status = 5)
  Scanning page 2
  scanimage: sane_start: Invalid argument
  Segmentation fault (core dumped)

  Scanning multiple pages in succession using multiple invocations of
  "scanimage" works correctly.

  This bug differs from #117577 in that in my case the scanning head
  moves back to the home position and scanimage segfaults, neither of
  which happened there.  Otherwise it seems very similar.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: sane-utils 1.0.20-13ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Jul 12 21:57:57 2010
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/scanimage
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  ProcCmdline: scanimage --batch
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_GB.utf8
  SegvAnalysis:
   Segfault happened at: 0xde31c9 :   mov
0x88(%eax),%edx
   PC (0x00de31c9) ok
   source "0x88(%eax)" (0x0088) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   gt68xx_line_reader_free_delays (reader=0x0) at gt68xx_mid.c:957
   gt68xx_line_reader_free (reader=0x0) at gt68xx_mid.c:1153
   gt68xx_scanner_stop_scan (scanner=0x9243128)
   sane_gt68xx_cancel (handle=0x9243128) at gt68xx.c:2108
   sane_dll_cancel (handle=0x922a348) at dll.c:1263
  Title: scanimage crashed with SIGSEGV in gt68xx_line_reader_free_delays()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/604798/+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 656478] Re: Init script for saned is spammy on default install needlessly

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  Init script for saned is spammy on default install needlessly

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  The default install of Maverick installs sane-utils which provides an
  init script for saned.  It's disabled by default, but on every boot
  spams the VT with

  
  echo "$NAME disabled; edit /etc/default/saned"

  Looking at how simple the init script and /etc/default/saned are, I would 
contend that this should either:
  1) Be converted to an upstart script that's not enabled by default
  or
  2) Remove the line that tells the user that saned is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/656478/+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 738302] Re: [Canon CanoScan 3200F] Scanner doesn't work with Ubuntu

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  [Canon CanoScan 3200F] Scanner doesn't work with Ubuntu

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: simple-scan

  Simple Scan notes:
  "there is no scanner- check that the scanner is turned on"

  After pushing the "acquire" button it notes:
  "no scanner available, connect a scanner"

  Works fine in Windows XP.

  As per the SANE project, this device has minimal support via experimental CVS:
  http://www.sane-project.org/unsupported/canon-3200f.html

  However, the experimental CVS wasn't transferred over when they moved from 
CVS to git. A copy of the experimental files are found at:
  
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/738302/+attachment/4803236/+files/cs3200f.tar.gz

  A patch that may be needed to compile against master branch: 
  http://lists.alioth.debian.org/pipermail/sane-devel/2013-March/031124.html

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: simple-scan 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  Architecture: i386
  Date: Sat Mar 19 17:14:28 2011
  DriverPackageVersions:
   libsane 1.0.21-2ubuntu2
   libsane-extras N/A
   hplip 3.10.6-1ubuntu10.2
   hpoj N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: American Megatrends Inc. K7S41GX
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=/dev/sda1 
loop=/hostname/disks/root.disk ro quiet splash
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SimpleScanLog:

  SourcePackage: simple-scan
  dmi.bios.date: 10/18/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: K7S41GX
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0123ABC
  dmi.chassis.type: 3
  dmi.chassis.vendor: Uknown Chassis Manufacture
  dmi.chassis.version: Version 1.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd10/18/2006:svnAmericanMegatrendsInc.:pnK7S41GX:pvr1.0:rvn:rnK7S41GX:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
  dmi.product.name: K7S41GX
  dmi.product.version: 1.0
  dmi.sys.vendor: American Megatrends Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/738302/+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 508866] Re: Remote network scanner is not being detected in "scanimage -L" although being published through avahi (karmic)

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Remote network scanner is not being detected in "scanimage -L"
  although being published through avahi (karmic)

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  The problem is as following: I got a HP 4400c USB Scanner connected to one 
machine (running karmic 64). The scanner is identified (scanimage -L) and used 
(xsane) without a problem. I was also able to make it accessible to another 
machine (also running karmic 64) by configuring saned on the server and 
net.conf on the client, and then solving the udev permissions issue, which 
seems to be mentioned in a few other bug reports - not relevant to this bug (I 
think).
  However, later I tried to make the remote machine detect the remote scanner 
automatically, through avahi - without having the saned server's IP address 
written manually to net.conf on the client machine. That didn't work. I 
verified that saned on the machine with the scanner publishes a proper service 
messahe in avahi - and it does. However neither "scanimage -L"  nor xsane are 
able to detect the remote scanner. 
  So, my question is - is the sane client configured with avahi support at all? 
If not - is that intentional?
  The package I report this bug on is sane-utils (because of scanimage).

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 17 21:07:14 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: sane-utils 1.0.20-4ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: sane-backends
  Uname: Linux 2.6.31-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/508866/+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 572246] Re: Sane lib crashes with "buffer overflow detected"

2022-03-27 Thread David Ward
** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Sane lib crashes with "buffer overflow detected"

Status in Simple Scan:
  Invalid
Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: simple-scan

  derosa@bowman:~$ simple-scan 
  *** buffer overflow detected ***: simple-scan terminated
  === Backtrace: =
  /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xfc6350]
  /lib/tls/i686/cmov/libc.so.6(+0xe128a)[0xfc528a]
  /lib/tls/i686/cmov/libc.so.6(+0xe05ba)[0xfc45ba]
  /usr/lib/sane/libsane-epson2.so.1(+0x121ad)[0x45571ad]
  /usr/lib/sane/libsane-epson2.so.1(+0x1257a)[0x455757a]
  /usr/lib/sane/libsane-epson2.so.1(sanei_configure_attach+0x495)[0x454a785]
  /usr/lib/sane/libsane-epson2.so.1(+0x103b7)[0x45553b7]
  /usr/lib/sane/libsane-epson2.so.1(sane_epson2_get_devices+0x39)[0x4556f59]
  /usr/lib/libsane.so.1(sane_dll_get_devices+0xb2)[0xca8ea2]
  /usr/lib/libsane.so.1(sane_get_devices+0x24)[0xca69b4]
  simple-scan[0x805a774]
  /lib/libglib-2.0.so.0(+0x65dcf)[0x8a4dcf]
  /lib/tls/i686/cmov/libpthread.so.0(+0x596e)[0x18996e]
  /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0xfb1a0e]
  === Memory map: 
  0011-00159000 r-xp  08:05 824342 /usr/lib/libORBit-2.so.0.1.0
  00159000-00161000 r--p 00049000 08:05 824342 /usr/lib/libORBit-2.so.0.1.0
  00161000-00163000 rw-p 00051000 08:05 824342 /usr/lib/libORBit-2.so.0.1.0
  00163000-0016a000 r-xp  08:05 1835047
/lib/tls/i686/cmov/librt-2.11.1.so
  0016a000-0016b000 r--p 6000 08:05 1835047
/lib/tls/i686/cmov/librt-2.11.1.so
  0016b000-0016c000 rw-p 7000 08:05 1835047
/lib/tls/i686/cmov/librt-2.11.1.so
  0016c000-00176000 r-xp  08:05 1835127/lib/libudev.so.0.6.1
  00176000-00177000 r--p 9000 08:05 1835127/lib/libudev.so.0.6.1
  00177000-00178000 rw-p a000 08:05 1835127/lib/libudev.so.0.6.1
  00178000-00182000 r-xp  08:05 824631 
/usr/lib/libpangocairo-1.0.so.0.2800.0
  00182000-00183000 r--p 9000 08:05 824631 
/usr/lib/libpangocairo-1.0.so.0.2800.0
  00183000-00184000 rw-p a000 08:05 824631 
/usr/lib/libpangocairo-1.0.so.0.2800.0
  00184000-00199000 r-xp  08:05 1835045
/lib/tls/i686/cmov/libpthread-2.11.1.so
  00199000-0019a000 r--p 00014000 08:05 1835045
/lib/tls/i686/cmov/libpthread-2.11.1.so
  0019a000-0019b000 rw-p 00015000 08:05 1835045
/lib/tls/i686/cmov/libpthread-2.11.1.so
  0019b000-0019d000 rw-p  00:00 0 
  0019d000-0023 r-xp  08:05 824756 
/usr/lib/libgdk-x11-2.0.so.0.2000.0
  0023-00232000 r--p 00093000 08:05 824756 
/usr/lib/libgdk-x11-2.0.so.0.2000.0
  00232000-00233000 rw-p 00095000 08:05 824756 
/usr/lib/libgdk-x11-2.0.so.0.2000.0
  00233000-002aa000 r-xp  08:05 824482 
/usr/lib/libcairo.so.2.10800.10
  002aa000-002ac000 r--p 00076000 08:05 824482 
/usr/lib/libcairo.so.2.10800.10
  002ac000-002ad000 rw-p 00078000 08:05 824482 
/usr/lib/libcairo.so.2.10800.10
  002ad000-002af000 r-xp  08:05 824663 
/usr/lib/libXcomposite.so.1.0.0
  002af000-002b r--p 1000 08:05 824663 
/usr/lib/libXcomposite.so.1.0.0
  002b-002b1000 rw-p 2000 08:05 824663 
/usr/lib/libXcomposite.so.1.0.0
  002b1000-002b3000 r-xp  08:05 824674 /usr/lib/libXdamage.so.1.1.0
  002b3000-002b4000 r--p 1000 08:05 824674 /usr/lib/libXdamage.so.1.1.0
  002b4000-002b5000 rw-p 2000 08:05 824674 /usr/lib/libXdamage.so.1.1.0
  002b5000-002b9000 r-xp  08:05 817026 /usr/lib/libXfixes.so.3.1.0
  002b9000-002ba000 r--p 3000 08:05 817026 /usr/lib/libXfixes.so.3.1.0
  002ba000-002bb000 rw-p 4000 08:05 817026 /usr/lib/libXfixes.so.3.1.0
  002bb000-002bd000 r-xp  08:05 1835034
/lib/tls/i686/cmov/libdl-2.11.1.so
  002bd000-002be000 r--p 1000 08:05 1835034
/lib/tls/i686/cmov/libdl-2.11.1.so
  002be000-002bf000 rw-p 2000 08:05 1835034
/lib/tls/i686/cmov/libdl-2.11.1.so
  002bf000-002c4000 r-xp  08:05 825107 
/usr/lib/libgudev-1.0.so.0.0.1
  002c4000-002c5000 r--p 5000 08:05 825107 
/usr/lib/libgudev-1.0.so.0.0.1
  002c5000-002c6000 rw-p 6000 08:05 825107 
/usr/lib/libgudev-1.0.so.0.0.1
  002c6000-002fd000 r-xp  08:05 1835070/lib/libdbus-1.so.3.4.0
  002fd000-002fe000 r--p 00036000 08:05 1835070/lib/libdbus-1.so.3.4.0
  002fe000-002ff000 rw-p 00037000 08:05 1835070/lib/libdbus-1.so.3.4.0
  002ff000-00318000 r-xp  08:05 824272 
/usr/lib/libatk-1.0.so.0.3009.1
  00318000-00319000 ---p 00019000 08:05 824272 
/usr/lib/libatk-1.0.so.0.3009.1
  00319000-0031a000 r--p 00019000 08:05 824272 
/usr/lib/libatk-1.0.so.0.3009.1
  0031a000-0031b000 rw-p 0001a000 08:05 824272 

[Desktop-packages] [Bug 575090] Re: Simple Scan detect Mustek 1200 UB Plus as Mustek BearPaw 1200 CU

2022-03-27 Thread David Ward
** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Simple Scan detect Mustek 1200 UB Plus as Mustek BearPaw 1200 CU

Status in Simple Scan:
  Won't Fix
Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  A Problem like this I have already had under 9.10 with xsane.
  There it was a comment or uncomment a line.

  Starting form Terminal brings the following message if I use the scan
  button:

  [gt68xx] Couldn't open firmware file
  (`/usr/share/sane/gt68xx/PS1fw.usb'): No such file or directory

  ** (simple-scan:1636): WARNING **: Unable to get open device: Invalid
  argument

  There is no file in the directory /usr/share/sane/gt68xx

  sane-find-scanner reported:

  found USB scanner (vendor=0x05d8, product=0x4002, chip=GT-6801) at
  libusb:005:002

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/575090/+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 438330] Re: Canon CanoScan LiDE 600F (04a9:2224), doesn't work

2022-03-27 Thread David Ward
Basic support is available in Ubuntu 21.10 with sane-backends 1.0.32:
http://www.juergen-ernst.de/info_sane.html

If this version does not work, please change status.

** Changed in: sane-backends (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Canon CanoScan LiDE 600F (04a9:2224), doesn't work

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  Not using ubuntu-bug as I am filing this on behalf of a colleague.

  This scanner is detected and listed as a new USB device but doesn't
  work in Ubuntu.

  As per the SANE project, the scanner is unsupported:
  
http://www.sane-project.org/cgi-bin/driver.pl?manu=Canon==any=04a9=2224

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/438330/+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 493430] Re: without --device arg: WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  without --device arg: WARNING: Unhandled message:
  interface=org.freedesktop.DBus.Introspectable, path=/,
  member=Introspect

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  scanimage produces the following message every time it starts up if a 
--device arg is omitted.  
  Scanning then proceeds to work correctly.  So the problem must have something 
to do with
  the code which searches for the scanner:

  WARNING: Unhandled message:
  interface=org.freedesktop.DBus.Introspectable, path=/,
  member=Introspect

  The scanner is an hp3030 laserjet multi-function device,
  hpaio:/usb/hp_LaserJet_3030?serial=00CNBM066305

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Dec  6 19:57:10 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: sane-utils 1.0.20-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: sane-backends
  Uname: Linux 2.6.31-16-generic x86_64
  XsessionErrors:
   (gnome-settings-daemon:2155): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2155): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2336): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2276): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (rhythmbox:2327): Rhythmbox-WARNING **: Could not open device /dev/radio0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/493430/+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 403340] Re: Sane does not recognize Epson Corp. CX9400Fax out of the box

2022-03-27 Thread David Ward
This model is recognized by libsane1 in all supported versions of
Ubuntu.

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

Title:
  Sane does not recognize Epson Corp. CX9400Fax out of the box

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  This hardware is not recognized when using xsane. I tried adding "usb
  0x04b8 0x083a" to /etc/sane.d/epson.conf

  I was able to get xsane up with the canner name in its options, when
  attempting to acquire preview or scan I get the following error:

  I get the error: Failed to star scanner: operation not supported.

  sane-find-scanner -q finds the scanner: found USB scanner
  (vendor=0x04b8, product=0x083a) at libusb:001:005

  Hardware: ID 04b8:083a Seiko Epson Corp. CX9300F/CX9400Fax/DX9400F

  ii  sane-utils1.0.19-23ubuntu7  API library for 
scanners -- utilities
  ii  xsane 0.996-1ubuntu2featureful graphical 
frontend for SANE (Scanner Access Now Easy)

  Distributor ID:   Ubuntu
  Description:  Ubuntu 9.04
  Release:  9.04
  Codename: jaunty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/403340/+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 403340] Re: Sane does not recognize Epson Corp. CX9400Fax out of the box

2022-03-27 Thread David Ward
This model is recognized by libsane1 in all supported versions of
Ubuntu.

** Changed in: sane-backends (Ubuntu)
   Status: New => Invalid

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

Title:
  Sane does not recognize Epson Corp. CX9400Fax out of the box

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  This hardware is not recognized when using xsane. I tried adding "usb
  0x04b8 0x083a" to /etc/sane.d/epson.conf

  I was able to get xsane up with the canner name in its options, when
  attempting to acquire preview or scan I get the following error:

  I get the error: Failed to star scanner: operation not supported.

  sane-find-scanner -q finds the scanner: found USB scanner
  (vendor=0x04b8, product=0x083a) at libusb:001:005

  Hardware: ID 04b8:083a Seiko Epson Corp. CX9300F/CX9400Fax/DX9400F

  ii  sane-utils1.0.19-23ubuntu7  API library for 
scanners -- utilities
  ii  xsane 0.996-1ubuntu2featureful graphical 
frontend for SANE (Scanner Access Now Easy)

  Distributor ID:   Ubuntu
  Description:  Ubuntu 9.04
  Release:  9.04
  Codename: jaunty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/403340/+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 1729104] Re: loading Ubuntu from restart libsane didn't load

2022-03-27 Thread David Ward
Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: sane-backends (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  loading Ubuntu from restart libsane didn't load

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  from reboot
  says can't load libsane

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 30 19:48:01 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8cdJP1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-23 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729104/+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 1966581] Re: Launcher screenshot UI cannot be added to dock

2022-03-27 Thread C de-Avillez
Importance set to WISHLIST per request on #ubuntu-bugs-announce

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Launcher screenshot UI cannot be added to dock

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 27/03/2022

  The new gnome-shell built-in screenshot UI has a launcher when you search it 
from
  start/applications, but the icon cannot be dragged or added to the dock

  This wishlist is for novice users that might not be familiar with the prt scr 
button
  and might benefit a launcher from the dock, like gnome-screenshot did before.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 13:38:44 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966581/+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 1962761] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

2022-03-27 Thread Apport retracing service
** Tags added: bugpattern-needed

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

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  It's part of a chain of bugs that come one after another as I try to
  report each one of them.

  Never saw this behavior before

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 20:32:37 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-01-03 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5f445b49a8 :   cmp
%rax,(%rbx)
   PC (0x7f5f445b49a8) ok
   source "%rax" ok
   destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince41.3-3
   file-roller   3.41.90-1
   nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
   nautilus-share0.7.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+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 1966608] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() nautilus crashed when opening it during file copying

2022-03-27 Thread Apport retracing service
*** This bug is a duplicate of bug 1962761 ***
https://bugs.launchpad.net/bugs/1962761

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1962761, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573535/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573537/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573541/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573542/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573543/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573544/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966608/+attachment/5573545/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1962761
   nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()  nautilus
  crashed when opening it during file copying

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus in Ubuntu 22.04 beta is very unstable when copying files, and
  it is slower than other versions. When I open it during file copying
  for the 4-5th time it crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 21:55:20 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.compression' b'default-compression-format' 
b"'encrypted_zip'"
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
  InstallationDate: Installed on 2022-03-11 (16 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f7aca697a88 :   cmp
%rax,(%rbx)
   PC (0x7f7aca697a88) ok
   source "%rax" ok
   destination "(%rbx)" (0x0001) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince42.1-1
   file-roller   3.42.0-1
   nautilus-dropbox  2019.02.14-1ubuntu1
   nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
   nautilus-share0.7.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1966608/+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 1966605] Re: mozilla has 2 apps in settings and cant remove of them

2022-03-27 Thread Apport retracing service
*** This bug is a duplicate of bug 1966524 ***
https://bugs.launchpad.net/bugs/1966524

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1966524, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573525/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573527/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573530/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573531/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573532/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573533/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966605/+attachment/5573534/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1966524

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  mozilla has 2 apps in settings and cant remove of them

Status in yelp package in Ubuntu:
  New

Bug description:
  in settings there are 2 mozilla apps and if i go to open in snap store
  it shows that mozilla is not installed. Once i hit install the
  permissions and remove buttons show up.

  But mozilla is not working properly with PIP. PIP is disappearing
  every time i click anywhere. The PIP window goes to desktop rather
  than staying of top of all the windows.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 01:06:11 2022
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcCmdline: yelp
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa80e5c930b:mov0x8,%rax
   PC (0x7fa80e5c930b) ok
   source "0x8" (0x0008) not located in a known VMA region (needed readable 
region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: yelp
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
  Title: yelp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1966605/+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 1966604] Re: [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card

2022-03-27 Thread John Paul Morrison
I managed to get the card back with pulseaudio:

- logout of desktop session/xrdp 
- systemctl restart xrdp
- unplug usb sound card from Ubuntu (this is not a usb redirection issue)
- login to xrdp
- run pulseaudio-dlna python script (not sure if it's related but was running 
previously for dlna, chromecast)
- run: pacmd unload-module module-udev-detect && pacmd load-module 
module-udev-detect

output: Module module-udev-detect not loaded.

After that pulseaudio shows the device and works again





** Attachment added: "Capture.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966604/+attachment/5573524/+files/Capture.PNG

** Summary changed:

- [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card
+ [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect previously 
working card

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

Title:
  [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect
  previously working card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This device was working fine until I applied the latest patches/kernel

  Bus 001 Device 013: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
  Sound Device

  
  Before: logged in to Ubuntu desktop with xrdp. Plugged in the USB sound card 
and pulseaudio detected the card as default. I was also able to map output to 
SPDIF.

  Feb 26 19:55:42 bogomipsnew kernel: Linux version 5.13.0-30-generic
  (buildd@lcy02-amd64-003) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0,
  GNU ld (GNU Binutils for Ubuntu) 2.34) #33~20.04.1-Ubuntu SMP Mon Feb
  7 14:25:10 UTC 2022 (Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19)

  
  After: updated and rebooted. No device detected in pulseaudio. Aplay -l 
showed no devices - added myself to audio group and aplay -l shows

   List of PLAYBACK Hardware Devices 
  card 1: ICUSBAUDIO7D [ICUSBAUDIO7D], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  new kernel:
  Mar 26 14:45:31 bogomipsnew kernel: Linux version 5.13.0-37-generic 
(buildd@lcy02-amd64-111) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 
(Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Mar 27 11:52:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: USB-Audio - ICUSBAUDIO7D
  Title: [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to focal on 2021-11-28 (119 days ago)
  dmi.bios.date: 01/08/2020
  dmi.bios.release: 2.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 0W7H8C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd01/08/2020:br2.9:svnDellInc.:pnPowerEdgeT320:pvr:rvnDellInc.:rn0W7H8C:rvrA01:cvnDellInc.:ct17:cvr:skuSKU=NotProvided;ModelName=PowerEdgeT320:
  dmi.product.name: PowerEdge T320
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge T320
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966604/+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 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

2022-03-27 Thread Sebastien Bacher
** Changed in: xdg-desktop-portal (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-desktop-portal/+bug/1966386/+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 1966603] Re: gnome shell add-on in FF broke with forced move to snap version

2022-03-27 Thread Paul White
*** This bug is a duplicate of bug 1741074 ***
https://bugs.launchpad.net/bugs/1741074

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

This particular bug has already been reported and is a duplicate of bug
1741074, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1741074
   [snap] chrome-gnome-shell extension fails to detect native host connector

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

Title:
  gnome shell add-on in FF broke with forced move to snap version

Status in firefox package in Ubuntu:
  New

Bug description:
  Looks like the FF add-on that allows you to review/alter gnome-shell
  extensions no longer works now that firefox is a snap. It was working
  when I initially installed Ubuntu-22.04 two weeks ago (I chose native
  apt of FF over snap then), but last week there was the announcement-
  and-forced-move over to a snap - I would guess that's when it broke.

  I just now removed the add-on from within FF, restarted FF, added it
  back in - and it still doesn't work. I have a bunch of FF add-ons
  (like uBlock Origin) and I think they are working - so this seems
  fairly specific to "Gnome Shell Extension"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 07:39:22 2022
  InstallationDate: Installed on 2022-03-13 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966603/+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 1966604] [NEW] [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card

2022-03-27 Thread John Paul Morrison
Public bug reported:

This device was working fine until I applied the latest patches/kernel

Bus 001 Device 013: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
Sound Device


Before: logged in to Ubuntu desktop with xrdp. Plugged in the USB sound card 
and pulseaudio detected the card as default. I was also able to map output to 
SPDIF.

Feb 26 19:55:42 bogomipsnew kernel: Linux version 5.13.0-30-generic
(buildd@lcy02-amd64-003) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU
ld (GNU Binutils for Ubuntu) 2.34) #33~20.04.1-Ubuntu SMP Mon Feb 7
14:25:10 UTC 2022 (Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19)


After: updated and rebooted. No device detected in pulseaudio. Aplay -l showed 
no devices - added myself to audio group and aplay -l shows

 List of PLAYBACK Hardware Devices 
card 1: ICUSBAUDIO7D [ICUSBAUDIO7D], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


new kernel:
Mar 26 14:45:31 bogomipsnew kernel: Linux version 5.13.0-37-generic 
(buildd@lcy02-amd64-111) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 
(Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun Mar 27 11:52:13 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: USB-Audio - ICUSBAUDIO7D
Title: [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card
UpgradeStatus: Upgraded to focal on 2021-11-28 (119 days ago)
dmi.bios.date: 01/08/2020
dmi.bios.release: 2.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.0
dmi.board.name: 0W7H8C
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd01/08/2020:br2.9:svnDellInc.:pnPowerEdgeT320:pvr:rvnDellInc.:rn0W7H8C:rvrA01:cvnDellInc.:ct17:cvr:skuSKU=NotProvided;ModelName=PowerEdgeT320:
dmi.product.name: PowerEdge T320
dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge T320
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1966604

Title:
  [USB-Audio - ICUSBAUDIO7D, playback] Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This device was working fine until I applied the latest patches/kernel

  Bus 001 Device 013: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
  Sound Device

  
  Before: logged in to Ubuntu desktop with xrdp. Plugged in the USB sound card 
and pulseaudio detected the card as default. I was also able to map output to 
SPDIF.

  Feb 26 19:55:42 bogomipsnew kernel: Linux version 5.13.0-30-generic
  (buildd@lcy02-amd64-003) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0,
  GNU ld (GNU Binutils for Ubuntu) 2.34) #33~20.04.1-Ubuntu SMP Mon Feb
  7 14:25:10 UTC 2022 (Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19)

  
  After: updated and rebooted. No device detected in pulseaudio. Aplay -l 
showed no devices - added myself to audio group and aplay -l shows

   List of PLAYBACK Hardware Devices 
  card 1: ICUSBAUDIO7D [ICUSBAUDIO7D], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  new kernel:
  Mar 26 14:45:31 bogomipsnew kernel: Linux version 5.13.0-37-generic 
(buildd@lcy02-amd64-111) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 
(Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Mar 27 11:52:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no 

[Desktop-packages] [Bug 1966603] [NEW] gnome shell add-on in FF broke with forced move to snap version

2022-03-27 Thread Jason Haar
Public bug reported:

Looks like the FF add-on that allows you to review/alter gnome-shell
extensions no longer works now that firefox is a snap. It was working
when I initially installed Ubuntu-22.04 two weeks ago (I chose native
apt of FF over snap then), but last week there was the announcement-and-
forced-move over to a snap - I would guess that's when it broke.

I just now removed the add-on from within FF, restarted FF, added it
back in - and it still doesn't work. I have a bunch of FF add-ons (like
uBlock Origin) and I think they are working - so this seems fairly
specific to "Gnome Shell Extension"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 07:39:22 2022
InstallationDate: Installed on 2022-03-13 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  gnome shell add-on in FF broke with forced move to snap version

Status in firefox package in Ubuntu:
  New

Bug description:
  Looks like the FF add-on that allows you to review/alter gnome-shell
  extensions no longer works now that firefox is a snap. It was working
  when I initially installed Ubuntu-22.04 two weeks ago (I chose native
  apt of FF over snap then), but last week there was the announcement-
  and-forced-move over to a snap - I would guess that's when it broke.

  I just now removed the add-on from within FF, restarted FF, added it
  back in - and it still doesn't work. I have a bunch of FF add-ons
  (like uBlock Origin) and I think they are working - so this seems
  fairly specific to "Gnome Shell Extension"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 07:39:22 2022
  InstallationDate: Installed on 2022-03-13 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966603/+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 1966602] [NEW] Screen not locked after inactivity

2022-03-27 Thread Jason Haar
Public bug reported:

I did a fresh install of Ubuntu-22.04 two weeks ago. I don't think the
automatic lock on idle feature has worked the entire time (and I've been
patching all the time when available). If I manually lock the screen it
works - but if I don't, I can go to bed and the next day it's still
unlocked. syslog doesn't show any obvious gnome-screensaver error, so I
wonder if this is actually a Wayland issue - ie it isn't telling gnome-
screensaver about inactivity triggers? I dunno - just guessing.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-screensaver 3.6.1-13ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 07:06:47 2022
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 900
 org.gnome.desktop.session session-name 'ubuntu'
InstallationDate: Installed on 2022-03-13 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen not locked after inactivity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Screen not locked after inactivity

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  I did a fresh install of Ubuntu-22.04 two weeks ago. I don't think the
  automatic lock on idle feature has worked the entire time (and I've
  been patching all the time when available). If I manually lock the
  screen it works - but if I don't, I can go to bed and the next day
  it's still unlocked. syslog doesn't show any obvious gnome-screensaver
  error, so I wonder if this is actually a Wayland issue - ie it isn't
  telling gnome-screensaver about inactivity triggers? I dunno - just
  guessing.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver 3.6.1-13ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 07:06:47 2022
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 900
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2022-03-13 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked after inactivity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966602/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
Ok, so setting "GTK_IM_MODULE=ibus" would work around the issue. That's
valuable knowledge, and thank you for figuring it out.

Unfortunately you are not supposed to set that variable explicitly on a
GNOME desktop, and especially not in a Wayland session. Doing so has
adverse side effects, so we can't do it for all users just like that.

The root cause might be in some GNOME package, e.g. mutter. Not sure how
to proceed. Maybe report it to ibus upstream to ask for help with the
analysis.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Both Xorg and Wayland can be solved this way, and this is what I just tested 
out.
They both seem to have this problem, but both can be solved this way.

Thank you for your positive response and help!

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966593] [NEW] gnome session locks when disconnecting external screen

2022-03-27 Thread Joe Barnett
Public bug reported:

After upgrade to jammy, noticed that the gnome session locks the screen
when I unplug an external screen.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sun Mar 27 08:49:28 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-17 (953 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-03-18 (8 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  gnome session locks when disconnecting external screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to jammy, noticed that the gnome session locks the
  screen when I unplug an external screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Mar 27 08:49:28 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (953 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966593/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Not just Edge, but all applications

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Everything is just as you said it would be.And it correctly on Microsoft
Edge.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
In any case using /etc/environment on Ubuntu for this purpose won't
happen. But maybe your finding can be helpful in figuring out a proper
fix.

Can you please clean up your /etc/environment from IM related variables,
reboot, and run this command:

env | grep -E 'XMOD|_IM'

Probably it outputs:

XMODIFIERS=@im=ibus
QT_IM_MODULE=ibus

Then, as a test, please add only this line to /etc/environment:

GTK_IM_MODULE=ibus

and reboot. Is that sufficient to make the candidate window be shown
correctly on e.g. Microsoft Edge?

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-27 Thread Zhang
Although it works without problems in Wayland, the problem still exists
in Xorg

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966221/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
This is indeed a problem caused by the environment, but I found that my 
/etc/environment file was blank.
I did various tests and could finally determine that this would fix the problem 
directly.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
I doubt that. The page you linked to does not apply to Debian/Ubuntu
systems. On GNOME desktops (including Ubuntu) we let GNOME set the
required environment variables, and on other desktops they are set via
the im-config package.

Also, I don't understand how the page is related to the problem with the
position of the candidate window.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966590] Re: cups segfault when printing or editing printers

2022-03-27 Thread Serge Hallyn
(Forcibly downgrading to the impish packages restored ability to print.)

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

Title:
  cups segfault when printing or editing printers

Status in cups package in Ubuntu:
  New

Bug description:
  Editing a printer in localhost:631, cups keeps segfaulting after
  (possibly related) access denied messages:

  [932068.059601] audit: type=1400 audit(1648388571.894:566): apparmor="DENIED" 
operation="connect" profile="/usr/bin/evince" 
name="/run/user/1000/at-spi/bus_0" pid=853633 comm="evince" requested_mask="wr" 
denied_mask="wr" fsuid=1000 ouid=1000
  [932069.716730] audit: type=1400 audit(1648388573.550:567): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=853664 comm="cupsd" 
capability=12  capname="net_admin"
  [932069.797610] audit: type=1400 audit(1648388573.630:568): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=853668 
comm="cups-browsed" capability=23  capname="sys_nice"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   E [27/Mar/2022:08:39:47 -0500] [Job 13] No suitable destination host found 
by cups-browsed.
   W [27/Mar/2022:08:39:47 -0500] [Job 13] Backend returned status 6 (retry job 
later)
  CurrentDesktop: qtile
  Date: Sun Mar 27 08:43:53 2022
  InstallationDate: Installed on 2022-02-25 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lpstat: device for HP_OfficeJet_200_Mobile_Series: 
ipps://HP%20OfficeJet%20200%20Mobile%20Series%20%5BBAD650%5D._ipps._tcp.local/
  MachineType: LENOVO 20XXS3JC01
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd: Permission denied
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (10 days ago)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1966590/+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 1966590] Re: cups segfault when printing or editing printers

2022-03-27 Thread Serge Hallyn
This makes it impossible for me to print from my laptop :(

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

Title:
  cups segfault when printing or editing printers

Status in cups package in Ubuntu:
  New

Bug description:
  Editing a printer in localhost:631, cups keeps segfaulting after
  (possibly related) access denied messages:

  [932068.059601] audit: type=1400 audit(1648388571.894:566): apparmor="DENIED" 
operation="connect" profile="/usr/bin/evince" 
name="/run/user/1000/at-spi/bus_0" pid=853633 comm="evince" requested_mask="wr" 
denied_mask="wr" fsuid=1000 ouid=1000
  [932069.716730] audit: type=1400 audit(1648388573.550:567): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=853664 comm="cupsd" 
capability=12  capname="net_admin"
  [932069.797610] audit: type=1400 audit(1648388573.630:568): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=853668 
comm="cups-browsed" capability=23  capname="sys_nice"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   E [27/Mar/2022:08:39:47 -0500] [Job 13] No suitable destination host found 
by cups-browsed.
   W [27/Mar/2022:08:39:47 -0500] [Job 13] Backend returned status 6 (retry job 
later)
  CurrentDesktop: qtile
  Date: Sun Mar 27 08:43:53 2022
  InstallationDate: Installed on 2022-02-25 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lpstat: device for HP_OfficeJet_200_Mobile_Series: 
ipps://HP%20OfficeJet%20200%20Mobile%20Series%20%5BBAD650%5D._ipps._tcp.local/
  MachineType: LENOVO 20XXS3JC01
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd: Permission denied
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (10 days ago)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1966590/+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 1966590] Re: cups segfault when printing or editing printers

2022-03-27 Thread Serge Hallyn
The permission denied errors appear unrelated:  after stopping apparmor
and restarting cups, I still get:

[932499.635684] cupsd[855122]: segfault at 0 ip 7f39be2ff98c sp 
7ffc12737718 error 4 in libc.so.6[7f39be176000+195000]
[932499.635695] Code: 1e fa 89 f8 31 d2 62 a1 fd 00 ef c0 09 f0 25 ff 0f 00 00 
3d 80 0f 00 00 0f 8f 70 03 00 00 62 e1 fe 28 6f 0f 62 b2 75 20 26 d1 <62> f3 75 
22 3f 0e 00 c5 fb 93 c9 ff c1 74 45 f3 0f bc d1 0f b6 04
[932503.181032] landscape-packa[855168]: segfault at 7ff7440e7fc0 ip 
7ff32fbd3b7a sp 7ffc2e910360 error 4 in 
apt_pkg.cpython-310-x86_64-linux-gnu.so[7ff32fbcd000+1f000]
[932503.181041] Code: 48 8b 55 20 4c 8b 75 28 49 89 c4 8b 52 08 49 8b 46 50 48 
8d 14 52 4c 8d 3c d0 4c 39 f8 0f 84 b0 00 00 00 4c 8b 2d 0e 04 03 00 <41> 8b 17 
31 f6 4c 89 ef 48 8d 04 d5 00 00 00 00 48 29 d0 49 8b 56

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

Title:
  cups segfault when printing or editing printers

Status in cups package in Ubuntu:
  New

Bug description:
  Editing a printer in localhost:631, cups keeps segfaulting after
  (possibly related) access denied messages:

  [932068.059601] audit: type=1400 audit(1648388571.894:566): apparmor="DENIED" 
operation="connect" profile="/usr/bin/evince" 
name="/run/user/1000/at-spi/bus_0" pid=853633 comm="evince" requested_mask="wr" 
denied_mask="wr" fsuid=1000 ouid=1000
  [932069.716730] audit: type=1400 audit(1648388573.550:567): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=853664 comm="cupsd" 
capability=12  capname="net_admin"
  [932069.797610] audit: type=1400 audit(1648388573.630:568): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=853668 
comm="cups-browsed" capability=23  capname="sys_nice"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   E [27/Mar/2022:08:39:47 -0500] [Job 13] No suitable destination host found 
by cups-browsed.
   W [27/Mar/2022:08:39:47 -0500] [Job 13] Backend returned status 6 (retry job 
later)
  CurrentDesktop: qtile
  Date: Sun Mar 27 08:43:53 2022
  InstallationDate: Installed on 2022-02-25 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lpstat: device for HP_OfficeJet_200_Mobile_Series: 
ipps://HP%20OfficeJet%20200%20Mobile%20Series%20%5BBAD650%5D._ipps._tcp.local/
  MachineType: LENOVO 20XXS3JC01
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd: Permission denied
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (10 days ago)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1966590/+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 1966590] [NEW] cups segfault when printing or editing printers

2022-03-27 Thread Serge Hallyn
Public bug reported:

Editing a printer in localhost:631, cups keeps segfaulting after
(possibly related) access denied messages:

[932068.059601] audit: type=1400 audit(1648388571.894:566): apparmor="DENIED" 
operation="connect" profile="/usr/bin/evince" 
name="/run/user/1000/at-spi/bus_0" pid=853633 comm="evince" requested_mask="wr" 
denied_mask="wr" fsuid=1000 ouid=1000
[932069.716730] audit: type=1400 audit(1648388573.550:567): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=853664 comm="cupsd" 
capability=12  capname="net_admin"
[932069.797610] audit: type=1400 audit(1648388573.630:568): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=853668 
comm="cups-browsed" capability=23  capname="sys_nice"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog:
 E [27/Mar/2022:08:39:47 -0500] [Job 13] No suitable destination host found by 
cups-browsed.
 W [27/Mar/2022:08:39:47 -0500] [Job 13] Backend returned status 6 (retry job 
later)
CurrentDesktop: qtile
Date: Sun Mar 27 08:43:53 2022
InstallationDate: Installed on 2022-02-25 (29 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Lpstat: device for HP_OfficeJet_200_Mobile_Series: 
ipps://HP%20OfficeJet%20200%20Mobile%20Series%20%5BBAD650%5D._ipps._tcp.local/
MachineType: LENOVO 20XXS3JC01
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_OfficeJet_200_Mobile_Series.ppd: Permission denied
ProcEnviron:
 TERM=st-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-03-16 (10 days ago)
dmi.bios.date: 12/02/2021
dmi.bios.release: 1.51
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET75W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XXS3JC01
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 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.32
dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XXS3JC01
dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1966590

Title:
  cups segfault when printing or editing printers

Status in cups package in Ubuntu:
  New

Bug description:
  Editing a printer in localhost:631, cups keeps segfaulting after
  (possibly related) access denied messages:

  [932068.059601] audit: type=1400 audit(1648388571.894:566): apparmor="DENIED" 
operation="connect" profile="/usr/bin/evince" 
name="/run/user/1000/at-spi/bus_0" pid=853633 comm="evince" requested_mask="wr" 
denied_mask="wr" fsuid=1000 ouid=1000
  [932069.716730] audit: type=1400 audit(1648388573.550:567): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=853664 comm="cupsd" 
capability=12  capname="net_admin"
  [932069.797610] audit: type=1400 audit(1648388573.630:568): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=853668 
comm="cups-browsed" capability=23  capname="sys_nice"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   E [27/Mar/2022:08:39:47 -0500] [Job 13] No suitable destination host found 
by cups-browsed.
   W [27/Mar/2022:08:39:47 -0500] [Job 13] Backend returned status 6 (retry job 
later)
  CurrentDesktop: qtile
  Date: Sun Mar 27 08:43:53 2022
  InstallationDate: Installed on 2022-02-25 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lpstat: device for HP_OfficeJet_200_Mobile_Series: 
ipps://HP%20OfficeJet%20200%20Mobile%20Series%20%5BBAD650%5D._ipps._tcp.local/
  MachineType: LENOVO 20XXS3JC01
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 

[Desktop-packages] [Bug 1966581] Re: Launcher screenshot UI cannot be added to dock

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

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

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

Title:
  Launcher screenshot UI cannot be added to dock

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 27/03/2022

  The new gnome-shell built-in screenshot UI has a launcher when you search it 
from
  start/applications, but the icon cannot be dragged or added to the dock

  This wishlist is for novice users that might not be familiar with the prt scr 
button
  and might benefit a launcher from the dock, like gnome-screenshot did before.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 13:38:44 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966581/+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 1966581] [NEW] Launcher screenshot UI cannot be added to dock

2022-03-27 Thread lotuspsychje
Public bug reported:

Ubuntu 22.04 development branch @ 27/03/2022

The new gnome-shell built-in screenshot UI has a launcher when you search it 
from
start/applications, but the icon cannot be dragged or added to the dock

This wishlist is for novice users that might not be familiar with the prt scr 
button
and might benefit a launcher from the dock, like gnome-screenshot did before.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 27 13:38:44 2022
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Launcher screenshot UI cannot be added to dock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 development branch @ 27/03/2022

  The new gnome-shell built-in screenshot UI has a launcher when you search it 
from
  start/applications, but the icon cannot be dragged or added to the dock

  This wishlist is for novice users that might not be familiar with the prt scr 
button
  and might benefit a launcher from the dock, like gnome-screenshot did before.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 13:38:44 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966581/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

2022-03-27 Thread fossfreedom
** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

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

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

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

** Changed in: ubuntukylin-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

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

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

2022-03-27 Thread Bug Watch Updater
** Changed in: xdg-desktop-portal
   Status: New => Fix Released

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

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-desktop-portal/+bug/1966386/+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 1966580] [NEW] Erroneously huge mouse pointer with snap-packaged firefox in jammy

2022-03-27 Thread Max Bowsher
Public bug reported:

I just upgraded to jammy, and the mouse cursor now becomes comically
huge whilst it's over a Firefox window.

I suspect this might be something to do with this being a HiDPI laptop.


I'm also fairly upset about the overcomplicated - and apparently broken - snaps 
being enforced on me, so I've fixed this by uninstalling snapd, and obtaining 
Firefox directly from Mozilla instead - which works absolutely fine.

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

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

Title:
  Erroneously huge mouse pointer with snap-packaged firefox in jammy

Status in firefox package in Ubuntu:
  New

Bug description:
  I just upgraded to jammy, and the mouse cursor now becomes comically
  huge whilst it's over a Firefox window.

  I suspect this might be something to do with this being a HiDPI
  laptop.

  
  I'm also fairly upset about the overcomplicated - and apparently broken - 
snaps being enforced on me, so I've fixed this by uninstalling snapd, and 
obtaining Firefox directly from Mozilla instead - which works absolutely fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

2022-03-27 Thread probono
Apparently this affects most if not all flavors of Ubuntu. Especially
the default flavor.

The AppImage format for distributing applications is centered around the
idea that a user can boot the Ubuntu Live ISO, download an application
in AppImage format, make it executable, and run it without having to
install anything.

Not having libfuse2 and fusermount on the Live ISO breaks this for all
existing AppImages out there.

AppImage tooling (the tools application authors use to produce AppImages
of their software) will have to be updated by the AppImage project, but
even once it is, it will take considerable time until all application
authors release updated AppImages of their software.

Hence, asking for a defined grace period until fuse2 gets removed from
the Ubuntu Live ISO.

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+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 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

2022-03-27 Thread probono
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntukylin-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

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