[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

[Mayank Dedhia]

I couldn't locate manual sync option. I'm on Ubuntu 20.04.1 and having
gnome-calendar 3.36.2-0ubuntu1

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 303140]

[firestormx2k]

I tried to "clean" some (actually many) of my e-mails (I wanted to keep
the text while reducing the file size by deleting the attachments) and
this still seems to be a big problem after 16 years (!)... as I use TB
in a corporate environment, many of the e-mails are signed and thus they
become blank when deleting the attachment (the text ist still there when
exporting to .eml and using some text editor to read them, but alas,
that's not the way to read an archived email :)...

Is there a possibility that somebody fixes this and somehow makes it possible 
that the text is still readable and - as suggested before - a message appears 
with something like "The digital signature has been removed from this message 
because the attachment
was removed, thus altering the e-mail."?

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

Title:
  No more "Save all" / "detach all" / "delete all" for attachments

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  After receiving an email with more than one attachment, I have to 
open/detach/save them one by one, cause "Save all" / "detach all" / "delete 
all" in the GUI are not available
  This happens since version 2.0.0.18

  1) Description:Ubuntu 8.04.1 Release:8.04
  User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
  MIME-Version: 1.0

  2) Package: Linux-Mint 5

  3) "Save all" / "detach all" / "delete all" available when right-
  klicking on an attachment

  4 )"Save all" / "detach all" / "delete all" greyed out, so not
  available

  ProblemType: Bug
  Architecture: i386
  Date: Fri Nov 28 11:34:16 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: wl fglrx
  Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1
  PackageArchitecture: all
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-21-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/303140/+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 1551949]

[acebone]

This bug makes Firefox less attractive to business. Not that I care, but
maybe the Firefox team does?

Also it forces me to start Chrome again and again, and it's the only
reason I ever have for starting Chrome.

+1 for a fix!

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

Title:
  Printing to PDF file loses URLs/links

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. File -> Print...
  2. Select "Print to File".
  3. Enter the file name.
  4. Enter the save-to folder.
  5. Leave the output format as-is, or select PDF if it's not the default.
  6. Hit the Print button.
  7. Open the resulting PDF in any PDF viewer.

  
  Actual results:

  The URLs within the document are not actually hyperlinks.  They are
  simply text, coloured blue and underlined.

  
  Expected results:

  Any clickable links on the original e-mail message should be retained
  when converting the document to PDF format.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunderbird 1:38.5.1+build2-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colan  2383 F pulseaudio
   /dev/snd/controlC0:  colan  2383 F pulseaudio
  BuildID: 20160106101030
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Mar  1 15:53:53 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.140  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1abc004a-043e-4a15-bdc0-45ade2150908
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=38.5.1/20160106101030 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   rhythmbox-mozilla 3.2.1-1ubuntu3.1
   adobe-flashplugin 1:20160209.1-0ubuntu0.15.10.1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-1abc004a-043e-4a15-bdc0-45ade2150908
   bp-c8c94f9f-0c39-42d2-97ac-f2c7d2150713
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to wily on 2015-11-30 (92 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1551949/+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 1896333] Re: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack.

[Launchpad Bug Tracker]

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [Dell Inspiron 5548] "Select an audio" menu when user have not even
  inserted headphone jack.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  GNOME 3.36.3 | Ubuntu 20.04.1

  It has been a month and I have been experiencing this weird behavior.

  Earphone option like this 3 while unlocking the laptop as if I
  have inserted earphones.

  Some details this issue:
  I have to wait like 10 min or so after the lock of the screen. This will 
trigger something and when I open the lid or touch mouse pad to unlock, I get 
earphone options to chooose in the screen as if I have inserted headphone jack.

  Something is wrong. I want to know why. This didn't used to happen a
  month ago. I waited a month to report this issue thinking it will get
  resolved in upcoming updates but sadly no changes so far. I think some
  Ubuntu's GNOME update might have something to do this. This is my wild
  guess. But very certain about it. Let me know.

  Although the issue might seems really small issue but very annoying to
  go throw this EVERYDAY.

  I would love to know what is causing this? When its fixed? Is there
  something wrong on my side?

  Note: This happens ONLY when I try to unlock the screen after like >10
  min or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pranav 3554 F pulseaudio
   /dev/snd/controlC0:  pranav 3554 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 19 20:54:36 2020
  InstallationDate: Installed on 2020-02-16 (216 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago)
  dmi.bios.date: 05/28/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FFJC4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 5548
  dmi.product.sku: 0641
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+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 1896375] Re: 25% cpu always for gnome-shell

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  25% cpu always for gnome-shell

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Tasks: 308 total,   1 running, 307 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  9.5 us,  3.6 sy,  0.0 ni, 86.3 id,  0.5 wa,  0.0 hi,  0.1 si,  0.0 
st
  MiB Mem :   3841.7 total,159.0 free,   1895.3 used,   1787.4 buff/cache
  MiB Swap:   7628.0 total,   7603.7 free, 24.2 used.   1624.8 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND
 2423 akhil 20   0 4310384 312188 115812 S  24.8   7.9  33:36.18 
gnome-shell
 2153 root  20   0  238576  82840  50104 S  12.6   2.1  10:59.90 Xorg   

 4193 akhil 20   0  938912 119056  82000 S   9.9   3.0  10:03.15 
gnome-control-c
 5308 akhil 20   0  977816  54544  40272 S   3.3   1.4   0:17.72 
gnome-terminal-
 1337 root -51   0   0  0  0 S   2.6   0.0   3:44.30 
irq/40-nvidia  
1 root  20   0  168984  12960   8392 S   0.3   0.3   0:12.09 
systemd
  210 root  20   0   0  0  0 S   0.3   0.0   0:01.63 
usb-storage
  952 root  20   0  418364  20028  16836 S   0.3   0.5   0:09.29 
NetworkManager

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 16:07:16 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-08-09 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  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/1896375/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled

[Andrés]

I'm unable to install Ubuntu because my ps2 keyboard doesn't work on the
live cd, and the accesibility keyboard doesn't work on the installation
app, so while I was able to copy and paste text from a text document to
the text fields, because I can't copy/paste anything to a password field
and the field itself doesn't open the on screen keyboard, I can't start
the installation.

Given that the on screen keyboard is an accessibility feature, I don't
know why it goes away on it's own without an option to keep it open. A
keyboard is not only useful on a text field, also with shortcuts and
more.

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

Title:
  [Focal regression] On-screen keyboard (OSK) does not appear on touch
  under Xorg on convertible laptops in tablet mode when physical
  keyboard disabled

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  OSK doesn't appear in X11 when disabling physical keyboard

  [ Test case ]

  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this
 disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as
 gnome-shell > Activities > Search:
 - The OSK appear
  4. Swipe from bottom of screen in order to summon OSK on demand:
 - occurred on Ubuntu 18.04 through 19.10)

  [ Regression potential ]

  The OSK shows when not needed in setup with no touch-screen or with
  touch screen but when not required.

  ---

  Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
  Related upstream bugs:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1242

  [Note: Please someone add a bug watch for
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
  for the other and then Launchpad somehow did not let me again]

  Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS 
9575 2-in-1:
  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as  
gnome-shell > Activities > Search
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text
  4. Swipe from bottom of screen in order to summon OSK on demand:
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text 
fields of foreign toolkits that are expected not to trigger the OSK 
automatically)

  Note that the EXPECTED RESULT still happens under Wayland in 20.04.
  Only the Xorg session is affected by the issue described in this bug.

  Also note that Accessibility was NOT necessary to be enabled in 19.10
  and before. (When enabling it in 20.04, the OSK does appear under
  Xorg, but this should not be necessary)

  (On Wayland there is a different changed behavior with the OSK not appearing 
in the device's laptop mode, i.e. with the physical keyboard enabled. This 
seems intended and a different issue as per 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )

  This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
  I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this 
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
  It probably also worked with 19.04 and possibly 18.10, but I ran mostly 
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)

  Other hardware reported to reproduce the issue (and in part are said
  to have been working in 19.10 and before, down to 18.04) include:

  In bug #1866556;
  Lenovo ThinkPad L390 Yoga
  Asus ZenBook UX370UAF
  Acer Switch 11 V sw5-173 (said to have worked with 18.04)
  (Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the 
tablet mode seems unsupported on these devices and so the issue might be 
different)

  In upstream bug:
  Dell Inspiron 15 700 2-in-1

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 19:59:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (619 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  RelatedPac

[Desktop-packages] [Bug 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Gunnar Hjalmarsson]

** Also affects: gobject-introspection via
   https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/305
   Importance: Unknown
   Status: Unknown

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream source package in Groovy:
  Confirmed
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.

[Bug Watch Updater]

Launchpad has imported 22 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=85677.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-10-31T03:41:52+00:00 Evan Driscoll wrote:

I am running LO 4.3.3 (tried upgrading from 4.2.2) on Windows 8 on a
Thinkpad Helix.

For almost every program on Windows, trying to pan using the touchscreen
scrolls. This is a very useful behavior.

However, on the LO applications (and Apache OOO as well), it acts like a
traditional mouse drag, simply changing the selection.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/0


On 2014-10-31T15:10:02+00:00 Adolfo Jayme wrote:

Thank you for your bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/1


On 2015-08-28T10:24:43+00:00 Patrick Smits wrote:

Same problem here under Windows 10. The only way to scroll through an
open document is the little scroll bar on the right of the document's
window, however this was designed to be accessed by a
mouse/trackpad/trackball. It's a real pain to use by fingertip.

Now that Windows 10 on <14" touch screens are the new standard, it would
be nice if LibreOffice could distinguish between a swipe gesture to
scroll a document up and down and a tap-hold-drag to select text within
a document.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/2


On 2015-11-07T22:56:01+00:00 Floydwaters67 wrote:

I can verify this behavior on a Windows 8.1 ASUS T100 tablet.
Additionally to swiping highlighting instead of scrolling, it is
impossible in a spreadsheet to copy a formula by touch into a series of
cells with a click and drag, the way you can do in MS Word.

This is a pretty big quality-of-life issue with using this program.
Please update to include true touchscreen compatibility ASAP.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/3


On 2015-11-11T06:55:53+00:00 Krasnaya Ploshchad’ wrote:

I can also verify this behavior on a Lenovo Yoga 13 ultrabook (upgraded
to Windows 10). In this case touch the page can swiping highlighting
texts in LO Writer instead of scrolling, but touch the scrollbar can
scroll page, that’s so uncomfortable for touch screen devices.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/4


On 2016-04-16T04:59:22+00:00 Adolfo Jayme wrote:

*** Bug 99331 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/5


On 2017-07-23T15:15:23+00:00 Krasnaya Ploshchad’ wrote:

A file previewing utility QuickLook, which uses macOS like quick preview
feature to view the file on Windows, have already made an implementation
for this, so let’s how does it get the solution:

https://github.com/xupefei/QuickLook/commit/b0e8a29f856cf6b9d3c8da52754240e7875b64e3

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/6


On 2017-07-23T15:16:25+00:00 Krasnaya Ploshchad’ wrote:

A file previewing utility QuickLook, which uses macOS like quick preview
feature to view the file on Windows, have already made an implementation
for this, so let’s see how does it get the solution:

https://github.com/xupefei/QuickLook/commit/b0e8a29f856cf6b9d3c8da52754240e7875b64e3

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/7


On 2017-10-25T22:41:43+00:00 Mikecgoss wrote:

I can verify this behavior on my 10 inch Asus tablet using LO 5.4. I am
really surprised by this. MS Office 2007 fully supported touch screen
yet in 2017 Libre Office does not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/8


On 2018-10-29T17:02:46+00:00 Miguelangelrv wrote:

*** Bug 121000 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/comments/9


On 2019-01-29T23:23:38+00:00 Martin-plamondon-g wrote:

Li

[Desktop-packages] [Bug 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Matthias Klumpp]

The bug is actually this one, in gobject-introspection:
https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/305


** Bug watch added: gitlab.gnome.org/GNOME/gobject-introspection/-/issues #305
   https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/305

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in appstream package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream source package in Groovy:
  Confirmed
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1903574/+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 1904939] [NEW] Monitor Settings Don't Get Applied in Wayland

[Patrick Garraud]

Public bug reported:

When configuring a 1080p monitor and a 4k monitor in extended screen
mode while using Wayland, when trying to change the screen positions or
which screen is the primary screen in the Monitor Settings, the settings
reset to default when Apply is clicked. Choosing to "Revert the
Settings" during the 15-second timer causes it to apply the changed
settings, but this resets whenever a pop-up message appears or when
returning to the Monitor Settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 16:47:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

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

Title:
  Monitor Settings Don't Get Applied in Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When configuring a 1080p monitor and a 4k monitor in extended screen
  mode while using Wayland, when trying to change the screen positions
  or which screen is the primary screen in the Monitor Settings, the
  settings reset to default when Apply is clicked. Choosing to "Revert
  the Settings" during the 15-second timer causes it to apply the
  changed settings, but this resets whenever a pop-up message appears or
  when returning to the Monitor Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 16:47:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrec

[Desktop-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Launchpad Bug Tracker]

This bug was fixed in the package pango1.0 - 1.46.2-3

---
pango1.0 (1.46.2-3) unstable; urgency=medium

  * Team upload
  * d/p/fc_Sort-faces-of-a-family.patch,
d/p/fontconfig_Try-harder-to-return-a-default-face.patch:
- Show regular monospace fonts in gnome-terminal's profile editor
  and not arbitrary font styles (LP: #1900729)

  [ Simon McVittie ]
  * d/gbp.conf: Use upstream/1.46.x branch

 -- Gunnar Hjalmarsson   Tue, 10 Nov 2020 21:41:00
+0100

** Changed in: pango1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  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/1900729/+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 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Gunnar Hjalmarsson]

The PPA proposal has proved to be problematic:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974107#83

So no solution in sight at the moment.

** Changed in: appstream (Ubuntu Groovy)
   Status: In Progress => Confirmed

** Changed in: appstream (Ubuntu Groovy)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: appstream (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in appstream package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream source package in Groovy:
  Confirmed
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1903574/+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 1904930] [NEW] USB Mouse removed and added intermittently

[bol]

Public bug reported:

When installing 20.04.1 on my workstation I experienced that there was
some lag or stutter when using the mouse when navigating the desktop,
and even more while playing a game where reliance on the mouse is quite
extensive.

I opened my log and saw these messages where the device was removed and
added anew due to that Ubuntu diagnoses it as removed, and re-adds it
again. See the log below.

I also tried to reinstall with Ubuntu 20.10 which I'm now running,
hoping that the issue wouldn't be present in a later release with a
newer kernel and surrounding packages. But to my disappointment it
unfortunately had the same flaw.

This issue has never been present in Fedora 32, nor in previous versions
that I've been using prior to my newfound acquaintance with Ubuntu, so
it would suggest the problem is with Ubuntu and not the hardware.

I have also put this issue up on askubuntu prior to posting it as a bug, but 
from my perspective it sure looks like it.
https://askubuntu.com/questions/1286301/ubuntu-20-04-1-lts-mouse-removed-and-added-intermittently

System information

Description:Ubuntu 20.10
Release:20.10

xserver-xorg-input-libinput:
  Installed: 0.30.0-1
  Candidate: 0.30.0-1
  Version table:
 *** 0.30.0-1 500
500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status

dmesg:
[ 1088.975507] usb 2-1.6: USB disconnect, device number 8
[ 1089.257584] usb 2-1.6: new full-speed USB device number 9 using ehci-pci
[ 1089.376858] usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, 
bcdDevice=69.00
[ 1089.376862] usb 2-1.6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[ 1089.376873] usb 2-1.6: Product: Gaming Mouse G400
[ 1089.376874] usb 2-1.6: Manufacturer: Logitech
[ 1089.378986] input: Logitech Gaming Mouse G400 as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.000A/input/input23
[ 1089.437806] hid-generic 0003:046D:C245.000A: input,hidraw1: USB HID v1.10 
Mouse [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0
[ 1089.439108] hid-generic 0003:046D:C245.000B: hiddev0,hidraw2: USB HID v1.10 
Device [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1

journalctl:

kernel: usb 2-1.6: USB disconnect, device number 5
/usr/libexec/gdm-x-session[10696]: (II) config/udev: removing device Logitech 
Gaming Mouse G400
/usr/libexec/gdm-x-session[10696]: (**) Option "fd" "50"
/usr/libexec/gdm-x-session[10696]: (II) event3  - Logitech Gaming Mouse G400: 
device removed
/usr/libexec/gdm-x-session[10696]: (II) UnloadModule: "libinput"
/usr/libexec/gdm-x-session[10696]: (II) systemd-logind: releasing fd for 13:67
kernel: usb 2-1.6: new full-speed USB device number 8 using ehci-pci
kernel: usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, 
bcdDevice=69.00
kernel: usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 2-1.6: Product: Gaming Mouse G400
kernel: usb 2-1.6: Manufacturer: Logitech
kernel: input: Logitech Gaming Mouse G400 as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.0008/input/input22
kernel: hid-generic 0003:046D:C245.0008: input,hidraw1: USB HID v1.10 Mouse 
[Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0
kernel: hid-generic 0003:046D:C245.0009: hiddev0,hidraw2: USB HID v1.10 Device 
[Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1
mtp-probe[21570]: checking bus 2, device 8: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6"
mtp-probe[21570]: bus: 2, device: 8 was not an MTP device
/usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device 
Logitech Gaming Mouse G400 (/dev/input/mouse0)
/usr/libexec/gdm-x-session[10696]: (II) No input driver specified, ignoring 
this device.
/usr/libexec/gdm-x-session[10696]: (II) This device may have been added with 
another device file.
/usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device 
Logitech Gaming Mouse G400 (/dev/input/event3)
/usr/libexec/gdm-x-session[10696]: (**) Logitech Gaming Mouse G400: Applying 
InputClass "libinput pointer catchall"
/usr/libexec/gdm-x-session[10696]: (II) Using input driver 'libinput' for 
'Logitech Gaming Mouse G400'
mtp-probe[21579]: checking bus 2, device 8: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6"
mtp-probe[21579]: bus: 2, device: 8 was not an MTP device
/usr/libexec/gdm-x-session[10696]: (II) systemd-logind: got fd for 
/dev/input/event3 13:67 fd 90 paused 0
/usr/libexec/gdm-x-session[10696]: (**) Logitech Gaming Mouse G400: always 
reports core events
/usr/libexec/gdm-x-session[10696]: (**) Option "Device" "/dev/input/event3"
/usr/libexec/gdm-x-session[10696]: (**) Option "_source" "server/udev"
/usr/libexec/gdm-x-session[10696]: (II) event3  - Logitech Gaming Mouse G400: 
is tagged by udev as: Mouse
/usr/libexec/gdm-x-session[10696]: (II) event3  - Logitech Gaming Mouse G400: 
device set to 800 DPI
/usr/libexec/gdm-x-session[10696]: (II) event3  - 

[Desktop-packages] [Bug 1904616] Re: after upgrade analog audio output vanished

[Darko Veberic]

*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965

i confirm that purging pipewire solves the issue. the analog audio
output is back.

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

Title:
  after upgrade analog audio output vanished

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  after an upgrade from 20.04 to 20.10 the analog audio output vanished.
  in pavucontrol there is no corresponding profile available for the
  built-in audio in the configuration tab.

  additional info:

  > aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0


  
  > pacmd list-cards
  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "02c8"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 65, 
available: no)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) 
Output + Analog Stereo Input (priority 5965, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo 
(HDMI 2) Output + Analog Stereo Input (priority 5765, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround-extra1+input:analog-stereo: Digital 
Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1+input:analog-stereo: Digital 
Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo 
(HDMI 3) Output + Analog Stereo Input (priority 5765, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output 
(priority 5700, available: no)
output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo 
(HDMI 4) Output + Analog Stereo Input (priority 5765, available: no)
output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) 
Output (priority 600, available: no)
output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) 
Output (priority 600, available: no)
output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output 
(priority 5700, available: no)
output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo 
(HDMI 5) Output + Analog Stereo Input (priority 5765, available: no)
output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) 
Output (priority 600, available: no)
output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
sinks:
alsa_

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Linard Verstraete]

Hi Po-Hsu Lin,

As mentioned in comment #30, the fix for nvidia-340 has been released
and available in xenial-updates since January 2018. I can confirm on the
relevant hardware it has been working ever since.

I can't comment for another package channel or nvidia-304.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  6 18:17:29 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+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 1904924] [NEW] Xorg freeze

[Ben Cordes]

Public bug reported:

Sounds like a fairly common problem according to [this
page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
freezes, and while I'm still able to move the mouse around, I can't
successfully click or type at any windows. It takes about 30 seconds for
gnome-shell to restart, and then the clock starts running (and the
system monitor starts updating) again.

This problem has been bugging me for a few months now, but I'm not sure
when it started. It tends to happen in clumps; sometimes it will go
several days without happening, but once it starts it often happens
twice pretty quickly, and often a few times across a day. I haven't been
able to isolate what causes it, but more often than not it has something
to do with clicking on a window or tab in Chrome. (It definitely also
happens in other applications, though.)

Every time it happens, dmesg contains a stack dump for gnome-shell
("page allocation failure"). I can provide gists of these dumps if
that's helpful (and not already included in the apport data). So I'm not
sure if this is actually an xorg thing or a gnome-shell thing.

% lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

% dpkg -l xorg* gnome-shell* | grep '^ii'
ii  gnome-shell  3.38.1-1ubuntu1.1  
amd64graphical shell for the GNOME desktop
ii  gnome-shell-common   3.38.1-1ubuntu1.1  
all  common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator   34-1   
all  AppIndicator/KStatusNotifierItem support for GNOME Shell
ii  gnome-shell-extension-desktop-icons  20.04.0+git20200908-1  
all  desktop icon support for GNOME Shell
ii  gnome-shell-extension-prefs  3.38.1-1ubuntu1.1  
amd64tool to enable / disable GNOME Shell extensions
ii  gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1   
all  Display system information in GNOME Shell status bar
ii  gnome-shell-extension-system76-power 2.0.0~1602857239~20.10~914b531~dev 
all  Gnome-shell extension for System76 Power Management
ii  gnome-shell-extension-ubuntu-dock68ubuntu20.10.1
all  Ubuntu Dock for GNOME Shell
ii  gnome-shell-extensions   3.38.1-1   
all  Extensions to extend functionality of GNOME Shell
ii  xorg 1:7.7+19ubuntu15   
amd64X.Org X Window System
ii  xorg-docs-core   1:1.7.1-1.1
all  Core documentation for the X.org X Window System
ii  xorg-sgml-doctools   1:1.11-1   
all  Common tools for building X.Org SGML documentation

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic 
5.8.17
Uname: Linux 5.8.0-7630-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
 GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 15:05:17 2020
DistUpgraded: 2020-11-16 10:15:57,099 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
InstallationDate: Installed on 2018-01-19 (1035 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System76, Inc. Wild Dog Performance
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7630-generic 
root=UUID=e12a4ebc-6235-4471-a2da-3f9da9d48f74 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to groovy on 2020-11-16 

[Desktop-packages] [Bug 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.

[Heather Ellsworth]

Thanks for reporting this! Seems it's been an issue in the upstream
Libreoffice project so we'll consume a fix from them.

** Bug watch added: Document Foundation Bugzilla #85677
   https://bugs.documentfoundation.org/show_bug.cgi?id=85677

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=85677
   Importance: Unknown
   Status: Unknown

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Touchscreen can't be used to scroll anymore. Instead it will select
  everything on its way.

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue.
  There are times when a user might want to scroll their screen by touching 
their screen. But I can't do this anymore.

  I want to know what went wrong? What can I do?

  Any info is appreciated.

  Note:
  Currently, I can scroll without in issue in Nautilus. But I can't do the same 
in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select 
words on screen whenever I touch my screen to scroll. 

  But we all know, SCROLL ≠ SELECT.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 09:25:39 2020
  DistUpgraded: 2020-10-28 23:47:17,717 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0641]
  InstallationDate: Installed on 2020-02-16 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5548
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago)
  dmi.bios.date: 05/28/2019
  dmi.bios.release: 5.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FFJC4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 5548
  dmi.product.sku: 0641
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/df-libreoffice/+bug/1903632/+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 1904258] Re: Nautilus (Files) app shows drive that was pulled out without unmount

[Sebastien Bacher]

Thanks for the log, from the backend it looks like the backend correct
detects it being removed

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

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

Title:
  Nautilus (Files) app shows drive that was pulled out without unmount

Status in nautilus package in Ubuntu:
  New

Bug description:
  I mount a flash drive onto my Ubuntu 18.04.5 instance.

  Started writing data to it. While data is still being written to the
  flash drive I pulled out the flash drive.

  Looking at the Nautilus (Files) window, I still see the drive. Running
  findmnt -S , produces some output. None is produced when
  offically unmounted.

  When I plug the flash drive back in, a second instance of the drive
  appears.

  When drive is pulled, but Nautilus displays the drive, clicking on it
  displays "Folder Empty" (or something close).

  When drive is put back in and the second instance appears, clicking
  either drive displays contents of drive.

  This might be caused by a reference being held by the program writing
  data to the drive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904258/+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 1904258] Re: Nautilus (Files) app shows drive that was pulled out without unmount

[Aleksandr]

Here are the requested logs when running:

gio mount -o

I have added comments to the text file to where drive was removed and
re-inserted.

** Attachment added: "gioLogsForRepro.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904258/+attachment/5436061/+files/gioLogsForRepro.txt

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

Title:
  Nautilus (Files) app shows drive that was pulled out without unmount

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I mount a flash drive onto my Ubuntu 18.04.5 instance.

  Started writing data to it. While data is still being written to the
  flash drive I pulled out the flash drive.

  Looking at the Nautilus (Files) window, I still see the drive. Running
  findmnt -S , produces some output. None is produced when
  offically unmounted.

  When I plug the flash drive back in, a second instance of the drive
  appears.

  When drive is pulled, but Nautilus displays the drive, clicking on it
  displays "Folder Empty" (or something close).

  When drive is put back in and the second instance appears, clicking
  either drive displays contents of drive.

  This might be caused by a reference being held by the program writing
  data to the drive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904258/+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 1904622] Re: boto3+s3 bucket fails

[Reed Dier]

** Attachment added: "boto3 credential verification"
   
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1904622/+attachment/5436048/+files/boto3_demo_working.log

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

Title:
  boto3+s3 bucket fails

Status in Duplicity:
  Incomplete
Status in duplicity package in Ubuntu:
  New

Bug description:
  I have a duplicity job that runs on multiple hosts, and am now having 
failures on my 20.04 hosts.
  The syntax for the job (as I am currently testing to debug) is:
  duplicity --dry-run  list-current-files --name $name --s3-use-ia 
--archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 
--s3-use-multiprocessing --volsize 1024 --verbosity 8 
boto3+s3://s3.amazonaws.com/bucket.name

  Using the duplicity packages from focal/main
  duplicity=0.8.11.1612-1
  And I installed the boto packages from focal/universe
  python3-boto3=1.9.253-1
  python3-botocore=1.14.14+repack-1

  This runs into the error:
  Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir
  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
85, in __init__
  self.reset_connection()
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
96, in reset_connection
  self.s3.meta.client.head_bucket(Bucket=self.bucket_name)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 357, in _api_call
  return self._make_api_call(operation_name, kwargs)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 676, in _make_api_call
  raise error_class(parsed_response, operation_name)
   botocore.exceptions.ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I then tried the duplicity snap from the snap store, both the stable and edge 
builds, with the same issue:
  Main action: list-current
  

  duplicity 0.8.17
  Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  Main action: list-current
  

  duplicity 0.8.18.dev11
  Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I also tried to update the boto3/botocore packages by way of pip3:
  pip3 freeze | grep boto
  boto3==1.16.19
  botocore==1.19.19

  And lastly as a last ditch, I tried to pull the packages from the 
groovy/universe repo, bringing them to:
  python3-boto3  1.13.14-1
  python3-botocore   1.17.22+repack-1_all

  I have also tried in a 20.10 system as well to see if any changes
  there, but same results.

  Hoping for something I can look at to get this back working as it was
  in 18.04 since 14.04.

  For good measure, I verified in a bionic build that using the same arguments 
as above with duplicity=0.7.17
  python-bo

[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails

[Reed Dier]

For the sake of pointing out the AWS creds which I think is what you are 
hinting at with "check permission keys".
As I was in my original bash script, and for testing I am exporting in my shell:
AWS_ACCESS_KEY_ID=$akey
AWS_SECRET_ACCESS_KEY=$sakey
PASSPHRASE=$passphrase

s3cmd seemed to like this without intervention, but I manually made
~/.s3cfg and verified that working as well.

I also created an .aws/credentials file with
[default]
aws_access_key_id = $akey
aws_secret_access_key = $sakey

I then verified that boto3 was seeing this with
ubuntu@duplicity-f:~$ python3
Python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import boto3
>>> client = boto3.client('s3')
>>> client.list_buckets()
{'ResponseMetadata': {'RequestId': '$responseid', 'HostId': '$hostid', 
'HTTPStatusCode': 200, 'HTTPHeaders': {'x-amz-id-2': '$amz-id-2', 
'x-amz-request-id': 'amz-request-id',[snip],}}

And this properly returns the buckets in this IAM account, so I assume boto3 is 
properly able to hit the s3 credentials file. I sanitized some data, hopefully 
which doesn't nullify the utility.
Attaching the full sanitized response as boto3_demo_working.log

My python is very rusty, I'm more or less bashing my way through
verifying all of this so if something would be more effective please let
me know.

That said, I am still unable to get past the 403 in the duplicity run.
Attaching full 2>&1 output as duplicity_demo_nonworking.log.
Again, sanitized as much as possible, while still not obfuscating the important 
parts (hopefully).

And just to provide some clean and clear repro steps:
I am using a fresh focal image in multipass for consistent clean testing.
# apt update; apt dist-upgrade; apt install duplicity python3-boto3

ubuntu@duplicity-f:~$ lsb_release -a ; uname -a ; dpkg -l | grep duplicity ; 
dpkg -l | grep -i boto
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename:   focal
Linux duplicity-f 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
ii  duplicity  0.8.11.1612-1 amd64  
  encrypted bandwidth-efficient backup
ii  python3-boto3  1.9.253-1 all
  Python interface to Amazon's Web Services - Python 3.x
ii  python3-botocore   1.16.19+repack-1ubuntu0.20.04.1   all
  Low-level, data-driven core of boto 3 (Python 3)

Please let me know what else I may be able to provide.

** Attachment added: "duplicity -v9 output with command"
   
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1904622/+attachment/5436047/+files/duplicity_demo_nonworking.log

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

Title:
  boto3+s3 bucket fails

Status in Duplicity:
  Incomplete
Status in duplicity package in Ubuntu:
  New

Bug description:
  I have a duplicity job that runs on multiple hosts, and am now having 
failures on my 20.04 hosts.
  The syntax for the job (as I am currently testing to debug) is:
  duplicity --dry-run  list-current-files --name $name --s3-use-ia 
--archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 
--s3-use-multiprocessing --volsize 1024 --verbosity 8 
boto3+s3://s3.amazonaws.com/bucket.name

  Using the duplicity packages from focal/main
  duplicity=0.8.11.1612-1
  And I installed the boto packages from focal/universe
  python3-boto3=1.9.253-1
  python3-botocore=1.14.14+repack-1

  This runs into the error:
  Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir
  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
85, in __init__
  self.reset_connection()
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
96, in reset_connection
  self.s3.meta.client.head_bucket(Bucket=self.bucket_name)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 357, in _api_call
  return self._make_api_call(operation_name, kwargs)
File "/home/

[Desktop-packages] [Bug 1904903] [NEW] Pulseaudio always defaults to any external audio device connected when booting up

[Matheus Reich]

Public bug reported:

When I am booting the computer up, it never sets the default output to
the one I was using previously, which should be the norm. This is also
the same for audio inputs. It works perfectly fine when connecting any
new sound sources to the PC, which then pulseaudio sets the output/input
to. But regarding it's state when booting up, it should stay on the last
used audio device.

1) Description: Ubuntu 20.10
Release:20.10

2) pulseaudio:
  Instalado: 1:13.99.2-1ubuntu2
  Candidato: 1:13.99.2-1ubuntu2
  Tabela de versão:
 *** 1:13.99.2-1ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:13.99.2-1ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

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

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

Title:
  Pulseaudio always defaults to any external audio device connected when
  booting up

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I am booting the computer up, it never sets the default output to
  the one I was using previously, which should be the norm. This is also
  the same for audio inputs. It works perfectly fine when connecting any
  new sound sources to the PC, which then pulseaudio sets the
  output/input to. But regarding it's state when booting up, it should
  stay on the last used audio device.

  1) Description:   Ubuntu 20.10
  Release:  20.10

  2) pulseaudio:
Instalado: 1:13.99.2-1ubuntu2
Candidato: 1:13.99.2-1ubuntu2
Tabela de versão:
   *** 1:13.99.2-1ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904903/+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 1904902] [NEW] Pulseaudio produces a lot of crackling audio after awhile

[Matheus Reich]

Public bug reported:

1) Description: Ubuntu 20.10
   Release: 20.10

2) pulseaudio:
  Instalado: 1:13.99.2-1ubuntu2
  Candidato: 1:13.99.2-1ubuntu2
  Tabela de versão:
 *** 1:13.99.2-1ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:13.99.2-1ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

3) What you expected to happen: It shouldn't produce any crackles in the audio 
after a set amount of time.
4) What happened instead: It starts to crackle with a very low volume, then it 
keeps increasing until it reaches the same volume as the music/audio. Running 
systemctl --user restart pulseaudio.service fixes the issue until the next 
restart.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 19 14:09:37 2020
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2020-06-16 (156 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2202
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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: System manufacturer

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


** Tags: amd64 apport-bug groovy

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

Title:
  Pulseaudio produces a lot of crackling audio after awhile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.10
 Release: 20.10

  2) pulseaudio:
Instalado: 1:13.99.2-1ubuntu2
Candidato: 1:13.99.2-1ubuntu2
Tabela de versão:
   *** 1:13.99.2-1ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

  3) What you expected to happen: It shouldn't produce any crackles in the 
audio after a set amount of time.
  4) What happened instead: It starts to crackle with a very low volume, then 
it keeps increasing until it reaches the same volume as the music/audio. 
Running systemctl --user restart pulseaudio.service fixes the issue until the 
next restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 19 14:09:37 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2020-06-16 (156 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt

[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

[Sebastian Gürtler]

I made some experiments to define the behaviour, the problem is, that 3
computers with installed ubuntu 20.04.1 LTS behave(d) differently
(installing fuse-exfat 1.3.0 stopped the described behaviour in two of
the computers, seems, that nautilus is able to bypass fuse-exfat in some
conditions).

I made the tests in an alternative terminal session without active GUI
and manually mounting without the fstab-entries.

I repeatedly mounted the device, created files, read them with cat,
modified them with touch. I did not apply status changes. Then I
unmounted, mounted read-only, checked changes and changeability, seeing,
that mount with -r option really protected the file system from being
changed.

touch xy creates a file, the time applied to the system was correct in
atime, ctime, mtime but highly fractioned below milliseconds, which is
not really in accordance to the exfat system where the time resolution
is 2 seconds and in an additional field 10 ms.

if unmounted and mounted read only again the newly created files were advanced 
1 month and the seconds were rounded to the next lower even number (conforming 
to the time resolution of 2 seconds in the mtime and ctime, the atime was set 
to Dec, 31, 1979, 1:00 (+001).
cat and touch (which results in the expected error message) made no changes to 
the files, also if unmounted and remounted rw.

The same results came with remounting read/writeable.

After using cat the mtime and ctime remains unchanged (1 month advanced), atime 
is set to the correct timestamp. 
After using touch all three timestamps are updated to the actual time and date 
(without fraction, just even seconds!)

if unmounted and mounted again files that were only read, showed a further 
advance of the date by one month in mtime and ctime and again Dec, 31,1979 in 
atime.
The touched files advanced by 1 month in mtime and ctime and also showed Dec, 
31, 1979 in atime.
Files that were only listed showed no change (remained the one month advanced 
as happend by the unmounting after their creation).

It seems that the procedure that writes some buffers back to the hard
drive during unmounting has bugs in converting to the exfat file
entries. The month in the c time-structure is 0-11, in exfat 1-12, this
may be an issue. The field for last access seems to be left empty. And
the fractions below the 2 seconds seem to be omitted in the procedures
that work with the filesystem even before flushing the buffers, but they
seem to be used in the procedure, that creates a file newly.

After installing fuse-exfat this behaviour stopped in one computer, in
the other not (where I will try uninstall and reinstall...). A bit less
important, but now with cat even the atime stays unchanged completely
(other than with ext4); ctime is changed together with mtime.

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Brian Murray]

** Tags removed: champagne

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error response from GetN

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Simon Ryu]

>This effects me also:
>
>ubuntu 20.04
>GeForce GTX 1050 Ti Mobile
>4k monitor - usb-c port
>
>That work find in ubuntu 19.10 and same driver.


Above my problem is solved with grub setting.

nvidia_drm.modeset=1


Thanks everyone!!

Now I'm using Ubuntu 20.10.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1869734] Re: openjade segfaults on all arch

[Christian Ehrhardt ]

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

** Also affects: openjade (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975242
   Importance: Unknown
   Status: Unknown

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

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New
Status in openjade package in Debian:
  Unknown

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869734] Re: openjade segfaults on all arch

[Christian Ehrhardt ]

** Summary changed:

- openjade segfaults on arm (due to gcc optimization)
+ openjade segfaults on all arch

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

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1904474] Re: Black/purple screen after booting Ubuntu

[Rabensteiner Alexander]

Ok,

I booted, waited some minutes where the screen gets stuck black/purple,
powered off and booted to recovery mode to collect `journalctl -b-1`.
You can find the file appended.

Maybe my system is booting correctly but the X Windows System is not
able to load?

Best
Alexander

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435977/+files/prevboot.txt

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

Title:
  Black/purple screen after booting Ubuntu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my
  ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark
  screen, Ubuntu is not booting (also after 15mins of waiting ...).

  I first thought my issue would be a *Black/purple screen after you
  boot Ubuntu for the first time* like over here:
  https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-
  screen-what-options-do-i-have-to-fix-it

  So I added ```ǹomodeset``` in the script executed before booting
  Ubuntu. Interestingly I was able to boot and then made this change
  persistent by updating the bootloader. I tried some more times to boot
  and suddenly it stopped working properly (with same blackscreen as
  before). I also took a look to the bootscript, ```ǹomodeset``` was
  present there.

  Then I played around with some other obscure suggestions like adding
  ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace
  ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but
  nothing gave me a soultion which did not get stuck with black screen
  of death after some reboots.

  I am a little bit clueless at the moment, so I have appended the uncompressed 
logs in ```/var/log```, captured like in 
https://wiki.ubuntu.com/DebuggingKernelBoot .
  The files appended are from a boot that got stuck, I have killed my laptop 
after 10mins of nothing happening.

  Btw. I have a dual boot with Windows 10, but I do not know if this is
  relevant for this issue.

  Best
  Alexander
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
  Tags:  bionic
  Uname: Linux 5.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.1-1~ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 281053] Re: [Upstream] Math equation editor: "newline" fails after symbols

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [Upstream] Math equation editor: "newline" fails after symbols

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libreoffice-math
  libreoffice-math:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/281053/+attachment/2417117/+files/math_newline_issue.tar.gz
  && file-roller -h math_newline_issue.tar.gz && cd math_newline_issue
  && lowriter -nologo math_newline_issue.odt

  is no upside down question marks are presented in the Math formulas.

  4) What happens is the upside down question marks are present
  erroneously due to "newline" command. If "newline" is preceded or
  followed by some characters (as +, -, =, which are often needed), some
  error marks "¿" are obtained, and perhaps only a single line if
  displayed (it depends on the character and its relative position to
  "newline"). Examples :

  a+b_ij = newline = c+d# single line; error mark
  a+b_ij newline = c+d  # two lines; missing "="; error mark
  a+b_ij newline + c+d  # correct behaviour !!  The "+" sign does fine 
after newline...
  a+b_ij + newline c+d # ... but not before: single line, error mark here
  a+b_ij = newline c+d # single line, error mark. The "=" sign does bad 
whether after or before newline

  WORKAROUND: {} newline {}

  ProblemType: Bug
  Architecture: i386
  Date: Fri Oct 10 03:31:54 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:2.4.1-1ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.24-19-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/281053/+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 1785262] Re: arm64 autopkgtests are flaky

[Christian Ehrhardt ]

This recently showed up often enough that I bothered to find this bug :-/
I think it degraded again into a state where we should consider:

IRC:
[13:16]  Was there any hope to not expect this to be a retry-monster 
forever?
[13:17]  The desktop team should be asked if they can work on making 
that less flaky
[13:17]  I don't think ignoring the tests there is a good answer
[13:18]  Reducing the coverage would be preferable if that gets it to be 
more stable, for example, assuming the flakiness can't be easily fixed

I have a simple test stats gatherer [1] that also shows the subtests
which helps a lot in those cases to identify potential candidates to
skip.

I attached the output, best viewed in monospace
AFAICS up until recently we had <15% on all architectures.
But in Hirsute on arm* I see a bump to 22% of the subtest "uicheck-sw".
Could be bad-luck / noise - but maybe it is worth considering to skip that on 
arm?

[1]: https://git.launchpad.net/~ubuntu-server/ubuntu-
helpers/tree/cpaelzer/check-autopkgtest-stats.sh

** Attachment added: "recent test statistics"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+attachment/5435973/+files/libreoffice-test-stats.txt

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

Title:
  arm64 autopkgtests are flaky

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+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 1785262] Re: arm64 autopkgtests are flaky

[Iain Lane]

Christian raised this with us just now - I think we should consider
taking a look at this.

Looking at

http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/arm64
http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/armhf

the tests are basically OK but one of the uicheck-* ones ends up timing
out often enough that it can be described as flaky. When this happens it
causes a problem for other migrations, doubly so as the runs take many
hours to complete whether they fail or not, which slows down migration
speed.

If it's not possible to fix the timeouts (feels like it might be hard or
take a while) then disabling these subtests (only) on arm would be an
option - stable tests with less coverage are better than flaky ones with
more.

We had

https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=baf5a581da7ce3bb27a5b8ed44fadeb6e245e1ff

in the past which might be a basis for what to do now, but that would
want to be extended to arm64 too.

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

Title:
  arm64 autopkgtests are flaky

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

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

[Vstuart-foote]

(In reply to dante19031999 from comment #19)
> Your starmath syntax is just wrong. The command = needs valid expressions at
> both sides, newline indicates end of expression, it is not an expression on
> itself.
> a+b_ij = {} newline {} = c+d

Agree. That is how we handle the NEWLINE command. As pointed out in
comment 4 and comment 5 above. And, attempt to modify parser behavior
were not viable.

And this becomes a documentation issue against describing behavior of
NEWLINE on formula layout [1][2]. What should be said about SM use of
NEWLINE command and its effect on parsing starmath/mathml syntax for
rendering of formula(s) to canvas?

=-ref-=
[1] 
https://help.libreoffice.org/latest/en-US/text/smath/guide/newline.html?DbPAR=MATH#bm_id1295205
[2] 
https://help.libreoffice.org/latest/en-US/text/smath/01/0504.html?DbPAR=MATH#bm_id3148730

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

Title:
  [Upstream] Math equation editor: "newline" fails after symbols

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libreoffice-math
  libreoffice-math:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/281053/+attachment/2417117/+files/math_newline_issue.tar.gz
  && file-roller -h math_newline_issue.tar.gz && cd math_newline_issue
  && lowriter -nologo math_newline_issue.odt

  is no upside down question marks are presented in the Math formulas.

  4) What happens is the upside down question marks are present
  erroneously due to "newline" command. If "newline" is preceded or
  followed by some characters (as +, -, =, which are often needed), some
  error marks "¿" are obtained, and perhaps only a single line if
  displayed (it depends on the character and its relative position to
  "newline"). Examples :

  a+b_ij = newline = c+d# single line; error mark
  a+b_ij newline = c+d  # two lines; missing "="; error mark
  a+b_ij newline + c+d  # correct behaviour !!  The "+" sign does fine 
after newline...
  a+b_ij + newline c+d # ... but not before: single line, error mark here
  a+b_ij = newline c+d # single line, error mark. The "=" sign does bad 
whether after or before newline

  WORKAROUND: {} newline {}

  ProblemType: Bug
  Architecture: i386
  Date: Fri Oct 10 03:31:54 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:2.4.1-1ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.24-19-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/281053/+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 281053]

[Dante19031999]

Your starmath syntax is just wrong. The command = needs valid expressions at 
both sides, newline indicates end of expression, it is not an expression on 
itself.
a+b_ij = {} newline {} = c+d

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

Title:
  [Upstream] Math equation editor: "newline" fails after symbols

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libreoffice-math
  libreoffice-math:
    Installed: 1:3.4.3-3ubuntu2
    Candidate: 1:3.4.3-3ubuntu2
    Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/281053/+attachment/2417117/+files/math_newline_issue.tar.gz
  && file-roller -h math_newline_issue.tar.gz && cd math_newline_issue
  && lowriter -nologo math_newline_issue.odt

  is no upside down question marks are presented in the Math formulas.

  4) What happens is the upside down question marks are present
  erroneously due to "newline" command. If "newline" is preceded or
  followed by some characters (as +, -, =, which are often needed), some
  error marks "¿" are obtained, and perhaps only a single line if
  displayed (it depends on the character and its relative position to
  "newline"). Examples :

  a+b_ij = newline = c+d# single line; error mark
  a+b_ij newline = c+d  # two lines; missing "="; error mark
  a+b_ij newline + c+d  # correct behaviour !!  The "+" sign does fine 
after newline...
  a+b_ij + newline c+d # ... but not before: single line, error mark here
  a+b_ij = newline c+d # single line, error mark. The "=" sign does bad 
whether after or before newline

  WORKAROUND: {} newline {}

  ProblemType: Bug
  Architecture: i386
  Date: Fri Oct 10 03:31:54 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:2.4.1-1ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.24-19-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/281053/+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 1846790]

[Xiscofauli]

Hello perneg...@gmail.com,
Could you please try to reproduce it with the latest version of LibreOffice 
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 
'UNCONFIRMED' if the bug is still present in the latest version.

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

Title:
  [upstream] Saving files with a '#' in the name silently(!) fails on
  GVFS smb:// paths (Samba share)

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  [Reported via ubuntu-bug, I'm assuming it has gathered all relevant
  system info. More, especially on the Samba server, if required, is
  available on request.]

  What I'm trying to do:
  Save a file whose name contains a '#' character to a Samba share accessed via 
a GVFS smb:// path.
  Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test 
#1.odt" on a Samba share mounted via Nautilus.
  Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or 
File-Open, make some changes, save it & quit. 

  What I'm expecting to happen:
  The file shows up under the assigned name on both the client and the Samba 
server (in case of a new file); or the existing file now contains the changes 
made (in case of an existing file being modified).
  Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory.
  Ex. 2: I'd expect "Test #2.odt" to contain my changes. 

  What happens instead:
  Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen 
from the client, "Test " [note the space at the end] on the server.
  Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" 
(client), or "Test " (server) is created with the saved data.
  Effectively, the save operation does not succeed -- without any error message.

  Analysis:
  This is based on experiments with more complex filenames. Somehow, when 
LibreOffice saves a file in this constellation, the filename gets truncated at 
the first '#', inclusive, first, suffix and all. (This in turn leaves a 
filename ending in a space, which isn't legal under Windows, so Samba's name 
mangling kicks in.)

  The problem does not occur with local files or on a sshfs-mount. Gedit has no 
problem even on smb://.
  It's unclear whether '#' is the only character affected.

  Some kind of URL handling/escaping bug in LibreOffice's GIO support?

  In any case, this cost me a day of work. (By the time I realised my
  changes hadn't actually been lost but landed in a new, cryptically-
  named file, I'd already recreated it to meet the deadline.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 17:12:21 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+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 1846790] Re: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share)

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: New => Incomplete

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

Title:
  [upstream] Saving files with a '#' in the name silently(!) fails on
  GVFS smb:// paths (Samba share)

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  [Reported via ubuntu-bug, I'm assuming it has gathered all relevant
  system info. More, especially on the Samba server, if required, is
  available on request.]

  What I'm trying to do:
  Save a file whose name contains a '#' character to a Samba share accessed via 
a GVFS smb:// path.
  Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test 
#1.odt" on a Samba share mounted via Nautilus.
  Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or 
File-Open, make some changes, save it & quit. 

  What I'm expecting to happen:
  The file shows up under the assigned name on both the client and the Samba 
server (in case of a new file); or the existing file now contains the changes 
made (in case of an existing file being modified).
  Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory.
  Ex. 2: I'd expect "Test #2.odt" to contain my changes. 

  What happens instead:
  Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen 
from the client, "Test " [note the space at the end] on the server.
  Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" 
(client), or "Test " (server) is created with the saved data.
  Effectively, the save operation does not succeed -- without any error message.

  Analysis:
  This is based on experiments with more complex filenames. Somehow, when 
LibreOffice saves a file in this constellation, the filename gets truncated at 
the first '#', inclusive, first, suffix and all. (This in turn leaves a 
filename ending in a space, which isn't legal under Windows, so Samba's name 
mangling kicks in.)

  The problem does not occur with local files or on a sshfs-mount. Gedit has no 
problem even on smb://.
  It's unclear whether '#' is the only character affected.

  Some kind of URL handling/escaping bug in LibreOffice's GIO support?

  In any case, this cost me a day of work. (By the time I realised my
  changes hadn't actually been lost but landed in a new, cryptically-
  named file, I'd already recreated it to meet the deadline.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 17:12:21 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+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 1785262] Re: arm64 autopkgtests are flaky

[Iain Lane]

** Tags added: rls-hh-incoming

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

Title:
  arm64 autopkgtests are flaky

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Jimmy K]

Olivier. Thank you for working on this.

Do you have any ETA when it will be released?

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

Since I before had only arm traces here, this is x86:

Program received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
384 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file 
or directory.
(gdb) bt
#0  __memmove_avx_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
#1  0x77eec459 in 
OpenSP::Vector::erase (p1=, p2=0x55fc23a0, this=, this=)
at /usr/include/OpenSP/Vector.cxx:134
#2  0x55c3b378 in ?? ()
#3  0x77eede35 in OpenJade_DSSSL::ProcessingMode::addRootRule 
(this=, expr=..., 
ruleType=OpenJade_DSSSL::ProcessingMode::constructionRule, loc=..., interp=...)
at ProcessingMode.cxx:376
#4  0x77ef4ab7 in OpenJade_DSSSL::SchemeParser::doRoot 
(this=0x7fffe150) at SchemeParser.cxx:484
#5  0x77efba28 in OpenJade_DSSSL::SchemeParser::parse 
(this=this@entry=0x7fffe150) at SchemeParser.cxx:190
#6  0x77f00f1f in OpenJade_DSSSL::StyleEngine::parseSpec 
(this=this@entry=0x556201c0, specParser=..., charset=..., id=..., mgr=..., 
defVars=...) at StyleEngine.cxx:166
#7  0x77e8a580 in OpenJade_DSSSL::DssslApp::processSysid 
(this=0x7fffe400, sysid=...) at DssslApp.cxx:138
#8  0x77963c7f in OpenSP::EntityApp::processArguments(int, char**) () 
from /usr/lib/libosp.so.5
#9  0x7795339b in OpenSP::CmdLineApp::run(int, char**) () from 
/usr/lib/libosp.so.5
#10 0x5557496b in main (argc=16, argv=0x7fffeb18) at jade.cxx:206

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

Notes to myself for another day if I need to revisit this

Repro:
# enable sources for apt
$ apt upgrade
$ apt install dpkg-dev openjade docbook-dsssl
$ apt source pgpool2
$ cd pgpool2-4.1.1/doc/src/sgml/
$ openjade  -wall -wno-unused-param -wno-empty -wfully-tagged  -c 
/usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t 
sgml -i output-html  -V html-index pgpool.sgml

That confirms Ubuntu breaking while Debian works.

Build openjade from the very same source (upstream is dead btw):
$ apt install ubuntu-dev-tools
$ apt build-dep openjade
$ pull-debian-source openjade
$ cd openjade-1.4devel1
$ ./debian/rules build

Then test with this path to the binary-wrapper
/root/openjade-1.4devel1/jade/openjade

$ /root/openjade-1.4devel1/jade/openjade  -wall -wno-unused-param -wno-
empty -wfully-tagged  -c
/usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d
stylesheet.dsl -t sgml -i output-html  -V html-index pgpool.sgml

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

I've found that:
- recompiling openjade on Debian nowadays makes it exhibit the same behavior
- recompiling openjade in Debian&Ubuntu with gcc-9 also fails the same way

I'd love to find the root cause, but my hope of identifying either a
compiler-default-option or compiler-version that made it break failed.
It stays as it was before, you better not recompile openjade otherwise
you'll need -O0 or find the yet unknown root cause.

IMHO for mostly a doc conversion tool (that also seems mostly dead
upstream) speed isn't super-important and while not perfect -O0 should
be ok'ish for the time being.


For now the mitigation worked, pgpool2 for example now built fine:
  https://launchpad.net/ubuntu/+source/pgpool2/4.1.4-2

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[Kent Lin]

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

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

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  Confirmed
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1900348] Re: Canon TS705 printer stopped working

[Sven N.]

I now connected the printer with the network cable instead of USB and it
seems I can use "driverless printing" for this one. Still strange with
the canon driver. Also there should be more users with this issue.

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

Title:
  Canon TS705 printer stopped working

Status in cups package in Ubuntu:
  Invalid

Bug description:
  My Canon TS705 printer stopped working in Ubuntu. Last time I used it
  was over a week ago so it could be something with the updates
  installed in the last two weeks. The printer queue says "filter
  failed". I've attached the cups log of the last print job.

  I already tried (besides rebooting) removing / installing the printer
  and reinstalling the canon driver package.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 18 20:42:50 2020
  InstallationDate: Installed on 2019-09-20 (394 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  Lpstat: Gerät für CanonTS705: cnijbe2://canon/?port=usb&serial=10746E
  MachineType: Dell Inc. Latitude 5591
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonTS705.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonTS705.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic 
root=UUID=c0cdf9a7-59c9-4ce4-8dfa-06ad760e34a5 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0CGP1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd05/23/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0CGP1G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1900348/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[Kent Lin]

The comment#12 is tested on Focal.

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

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  Confirmed
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[Kent Lin]

Test WD19TB with Dell Precision 7750
Kernel: 5.6.0-1035-OEM#37
xorg-server (2:1.20.8-2ubuntu2.5)
NV driver:450.80.02

The issue is fixed.

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

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  Confirmed
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1904872] Re: In Yaru-dark, the data labels on the charts are not visible

[Gabor Botzheim]

visible text in light mode

** Attachment added: "visible text in light mode"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1904872/+attachment/5435971/+files/Screenshot%20from%202020-11-19%2012-33-01.png

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

Title:
  In Yaru-dark, the data labels on the charts are not visible

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  In Yaru-dark, the data labels on the charts are not visible, as they use the 
same dark font color. In normal light Yaru they are well visible
  Open power statistics, select the battery and open the history or statistics 
tab. Switch between Dark and Light theme in appearance, and you see the hidden 
text.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  gnome-power-manager:
Installed: 3.32.0-2
Candidate: 3.32.0-2
Version table:
   *** 3.32.0-2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-power-manager 3.32.0-2
  Uname: Linux 5.9.8-050908-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 12:20:55 2020
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2020-11-12 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1904872/+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 1904872] [NEW] In Yaru-dark, the data labels on the charts are not visible

[Gabor Botzheim]

Public bug reported:

In Yaru-dark, the data labels on the charts are not visible, as they use the 
same dark font color. In normal light Yaru they are well visible
Open power statistics, select the battery and open the history or statistics 
tab. Switch between Dark and Light theme in appearance, and you see the hidden 
text.

Description:Ubuntu 20.04.1 LTS
Release:20.04

gnome-power-manager:
  Installed: 3.32.0-2
  Candidate: 3.32.0-2
  Version table:
 *** 3.32.0-2 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-power-manager 3.32.0-2
Uname: Linux 5.9.8-050908-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 12:20:55 2020
ExecutablePath: /usr/bin/gnome-power-statistics
InstallationDate: Installed on 2020-11-12 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "invisible text in dark mode"
   
https://bugs.launchpad.net/bugs/1904872/+attachment/5435965/+files/Screenshot%20from%202020-11-19%2012-32-36.png

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

Title:
  In Yaru-dark, the data labels on the charts are not visible

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  In Yaru-dark, the data labels on the charts are not visible, as they use the 
same dark font color. In normal light Yaru they are well visible
  Open power statistics, select the battery and open the history or statistics 
tab. Switch between Dark and Light theme in appearance, and you see the hidden 
text.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  gnome-power-manager:
Installed: 3.32.0-2
Candidate: 3.32.0-2
Version table:
   *** 3.32.0-2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-power-manager 3.32.0-2
  Uname: Linux 5.9.8-050908-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 12:20:55 2020
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2020-11-12 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1904872/+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 1904794] Re: Graphical error in Disks app

[Norbert]

** Tags added: groovy rpi

** Also affects: gnome-disk-utility (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Graphical error in Disks app

Status in Ubuntu MATE:
  New
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  When loading the disks app I see the close item missing. I am
  enclosing a screenshot. I am using Mate 20.10 on a Raspberry Pi 4B 4Gb
  Ram.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1904794/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

FYI These issues might exist for a long time, but seem to grow recently
  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489482
  - 
https://sources.debian.org/src/vim/2:8.2.1913-1/debian/changelog/?hl=2026#L2026

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

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1904865] [NEW] apt-secure(8) manpage

[hadi saeedi]

Public bug reported:

apt-secure(8) manpage for repository creation and user configuration
details.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-terminal 3.36.2-1ubuntu1~20.04
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 14:16:52 2020
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2020-11-06 (12 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  apt-secure(8) manpage

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  apt-secure(8) manpage for repository creation and user configuration
  details.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 14:16:52 2020
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-11-06 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1904865/+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 1890141] Re: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling

[Joseph]

Affects me too. Extension helped, thx!

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

Title:
  Can't fullscreen, or windows get automatically un-fullscreened, when
  using fractional scaling

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Same issue as this one: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1863391

  Some websites like YouTube will attempt to fullscreen, just not
  successfully. Other websites, like Netflix, will fullscreen for a
  second and de-fullscreen after that. Some games act weirdly in
  fullscreen mode (this might be related, as I've never had this issue
  before now: https://github.com/ValveSoftware/csgo-osx-
  linux/issues/2429).

  EDIT: This only happens when fractional scaling is enabled. My config;
  main 4K screen at 150% and secondary 1080p screen to the right at
  100%. YouTube fullscreens fine on the sec. screen (1080 100%).

  This is a gif I posted in the related bug report showing exactly what
  happens: https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  3 14:03:00 2020
  InstallationDate: Installed on 2020-07-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+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 1904859] [NEW] [snap] cannot send file from Nautilus

[Francois Thirioux]

Public bug reported:

TB 78.5.0 snap
Focal

Nothing happens when I right-click on a file (using Nautilus) from my
home and choose 'send to'. I did not have such a problem using TB deb.

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

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

Title:
  [snap] cannot send file from Nautilus

Status in thunderbird package in Ubuntu:
  New

Bug description:
  TB 78.5.0 snap
  Focal

  Nothing happens when I right-click on a file (using Nautilus) from my
  home and choose 'send to'. I did not have such a problem using TB deb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904859/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libclc into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190827-7~ubuntu0.20.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libclc (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Confirmed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

This now indeed breaks on all architectures:
https://launchpadlibrarian.net/507574538/buildlog_ubuntu-hirsute-amd64.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507575283/buildlog_ubuntu-hirsute-armhf.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507578381/buildlog_ubuntu-hirsute-riscv64.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507575848/buildlog_ubuntu-hirsute-s390x.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507576954/buildlog_ubuntu-hirsute-ppc64el.pgpool2_4.1.4-2_BUILDING.txt.gz

It still doesn't do so on Debian.
For the time being - as predicted - set -O0 on all architectures to avoid the 
issue.

Right now this issue also breaks the build of pgpool2 4.1.4-2 which is required 
to have things working with PG-13.
=> https://launchpad.net/ubuntu/+source/pgpool2/4.1.4-2

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

** Tags added: update-excuse

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1904777] Re: Xorg randomly crashes under xrdp

[Michał Sawicz]

There doesn't seem to be a related "Assertion" in the logs. I've
installed the debug symbols now, will report back.

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

Title:
  Xorg randomly crashes under xrdp

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm using xrdp to log into a remote machine. Since upgrading it to
  20.04, my sessions started failing randomly. They would either not
  start at all, or get interrupted hours later.

  Here's a backtrace I found in a .xorgxrdp.log

  [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off
  [ 92697.915] rdpInDeferredRepeatCallback:
  [ 92697.916] rdpkeybChangeKeyboardControl:
  [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off
  [ 92712.569] (EE) 
  [ 92712.586] (EE) Backtrace:
  [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c]
  [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7ffa5424f41f]
  [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7ffa5408c18b]
  [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7ffa5406b859]
  [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a]
  [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) 
[0x7ffa5407cf36]
  [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) 
[0x5559b0103095]
  [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) 
[0x5559b01046e2]
  [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4]
  [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x5559affd6f34]
  [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4]
  [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7ffa5406d0b3]
  [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e]
  [ 92712.621] (EE) 
  [ 92712.621] (EE) 
  Fatal server error:
  [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting
  [ 92712.621] (EE) 
  [ 92712.623] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for 
additional information.
  [ 92712.623] (EE) 
  [ 92712.627] rdpmouseControl: what 4
  [ 92712.627] rdpkeybControl: what 4
  [ 92712.629] rdpLeaveVT:
  [ 92712.634] (EE) Server terminated with error (1). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Nov 18 20:07:37 2020
  DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609]
  MachineType: HP ProLiant MicroServer
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic 
root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 07/29/2011
  dmi.bios.vendor: HP
  dmi.bios.version: O41
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr:
  dmi.product.name: ProLiant MicroServer
  dmi.product.sku: 664447-425
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-

[Desktop-packages] [Bug 1904845] [NEW] [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails after a while

[Cyrille Caron]

Public bug reported:

sounds stops after few seconds
I tried to modify the list order of the sound cards as alsamixer was showing me 
that the chip ATI R6xx HDMI set as 0 HD-Audio Generic seems to have no output 
when the chip Realtek ALC294 set as 1 HD-Audio Generic displays all controls
That's why I did edit /etc/modprobe.d/alsa-base.conf
I also tried to change with sudo nano /etc/group 
audio:x:29:pulse to audio:x:29:cyrille
as advised there 
https://fluoblog.wordpress.com/2008/01/13/resolution-des-problemes-de-son-sous-ubuntu/
but it didn't seem to have made any change as grep 'audio' /etc/group returns 
audio:x:29:pulse

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 09:57:10 2020
InstallationDate: Installed on 2020-11-05 (13 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog: nov. 19 08:38:26 cyrille-ASUS-Vivo-AIO-V241DA-M241DA 
dbus-daemon[819]: [system] Activating via systemd: service 
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by 
':1.37' (uid=121 pid=1237 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails 
after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2020
dmi.bios.vendor: ASUSTeK COMPUTER INC.
dmi.bios.version: V241DA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: V241DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 13
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvrV241DA.300:bd05/18/2020:svnASUSTeKCOMPUTERINC.:pnASUSVivoAIOV241DA_M241DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnV241DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0:
dmi.product.family: ASUS Vivo AIO
dmi.product.name: ASUS Vivo AIO V241DA_M241DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-19T09:44:02.150839

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


** Tags: amd64 apport-bug bionic

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

Title:
  [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sounds stops after few seconds
  I tried to modify the list order of the sound cards as alsamixer was showing 
me that the chip ATI R6xx HDMI set as 0 HD-Audio Generic seems to have no 
output when the chip Realtek ALC294 set as 1 HD-Audio Generic displays all 
controls
  That's why I did edit /etc/modprobe.d/alsa-base.conf
  I also tried to change with sudo nano /etc/group 
  audio:x:29:pulse to audio:x:29:cyrille
  as advised there 
  
https://fluoblog.wordpress.com/2008/01/13/resolution-des-problemes-de-son-sous-ubuntu/
  but it didn't seem to have made any change as grep 'audio' /etc/group returns 
audio:x:29:pulse

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 09:57:10 2020
  InstallationDate: Installed on 2020-11-05 (13 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: nov. 19 08:38:26 cyrille-ASUS-Vivo-AIO-V241DA-M241DA 
dbus-daemon[819]: [system] Activating via systemd: service 
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by 
':1.37' (uid=121 pid=1237 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2020
  dmi.bios.vend