[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit

[Allie Campbell]

Thank you :)

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  New
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1861262] Re: Add message/rfc822 to thunderbird.desktop

[Lucas Sandery]

@seb128 I'm not sure it's upstream.
 has been around
forever and was marked as duplicate of the still open
 where it appears
Mozilla doesn't want to do anything about it. The earliest ancestor of
that file I can find in the source is from 2010
.

** Bug watch added: Mozilla Bugzilla #371734
   https://bugzilla.mozilla.org/show_bug.cgi?id=371734

** Bug watch added: Mozilla Bugzilla #296568
   https://bugzilla.mozilla.org/show_bug.cgi?id=296568

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

Title:
  Add message/rfc822 to thunderbird.desktop

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Please add message/rfc822 to thunderbird.desktop:

  -MimeType=x-scheme-handler/mailto;application/x-xpinstall;
  +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822;

  It will allow to open *.eml files. I attach an example eml file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+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 1920248] Re: Anker Soundcore Life Q10 microphone not working

[Daniel van Vugt]

Please try:

Settings >
Sound >
Output >
Configuration = Headset Head Unit (HSP/HFP)


** Tags added: focal

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

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

Title:
  Anker Soundcore Life Q10 microphone not working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my
  Soundcore Life Q10 with it, but the microphone doesn't work. I tried
  also to follow some answers here, but no one worked for me.

  I tried to use blueman, but I get Failed to change profile to
  headset_head_unit. I tried to install oFono, but I cannot compile
  phonesim due to some problem with dependencies version.

  I think that PulseAudio does not support HFP out of the box, and I
  found many other people that has this problem (see for example
  https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with-
  microphone-hfp-in-ubuntu-18-04/)

  Is there any way to make my headset working?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+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 1920133] Re: normal use then sys seizure then reboot

[Daniel van Vugt]

Thanks for the bug report.

Next time the problem happens, straight after the reboot please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also follow these steps to check for crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

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

Title:
  normal use then sys seizure then reboot

Status in Ubuntu:
  Incomplete

Bug description:
  I was using VS Code
  system seized up
  then rebooted

  no error messages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 19 12:15:31 2021
  DistUpgraded: 2021-01-09 08:43:22,797 DEBUG /openCache(), new cache size 67902
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
  InstallationDate: Installed on 2015-08-23 (2034 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2021-01-09 (69 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Mon Aug 20 17:24:57 2018
  xserver.configfile: default
  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/+bug/1920133/+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 1920239] Re: Icons in the background when I click on "show applications"

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1918874
   [regression] Application windows appear over the icon grid when Ubuntu Dock 
or Dash To Dock is loaded

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

Title:
  Icons in the background when I click on "show applications"

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

Bug description:
  Ubuntu Hirsute Hippo (development branch)
  gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

  BUG
  When I press on "Show applications" on the dock the animation starts and at 
the end I end up with the application icons in the background. The icons are 
partly overlaid by the program preview.

  Video of the bug https://youtu.be/eodtSxRRiNg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1920239/+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 1886592] Re: Add support for VMware Horizon SSO to gnome-shell

[Matthew Ruffell]

Performing verification for gnome-shell in Bionic.

During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.

I will begin by walking through the SSO workflow, based around the
custom gnome-shell package distributed by VMware.

Firstly, start with a fresh Focal Desktop VM, all up to date.

Visit the VMware website, specifically this link:

https://my.vmware.com/en/web/vmware/evalcenter?p=horizon-eval-8

Sign up for a VMware account and reach the VMware Horizon 8 evaluation
download page. The next step is to locate the "Linux Agent x86_64". The
file is named

VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz

If you have difficulty in obtaining this file and want to reproduce,
please message me.

Download and copy to the Focal VM.

$ scp VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz 
ubuntu@target:~/
$ ssh ubuntu@target
$ tar -xf VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz
$ cd VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770

Next, install the VMware Horizon Linux Agent by following the
instructions at:

https://docs.vmware.com/en/VMware-Horizon-7/7.13/linux-desktops-
setup/GUID-B4111821-34F2-465B-B290-FC2070EFCB5A.html

$ sudo apt install libpam-pkcs11
$ sudo apt install libnss3-tools
$ sudo apt install open-vm-tools
$ sudo apt install python python-dbus python-gobject
$ sudo ./install_viewagent.sh -T yes

Now, this will install a custom patched gnome-shell library, which
contains the following patches:

https://paste.ubuntu.com/p/q4fkNrqHQT/

You can find this, and more in the VMware-horizonagent-linux-
x86_64-2012-8.1.0-17336770/sso directory.

Reboot the VM.

When it comes back up, run "ps aux". You will see:

root  1406  0.0  0.0   4904  2020 ?S15:53   0:00 /bin/sh 
/usr/lib/vmware/viewagent/bin/GetMachineId.sh
root  1447  0.0  0.2 404328 10968 ?Sl   15:53   0:00 
/usr/lib/vmware/viewagent/DesktopDaemon/desktopDaemon
root  1449  2.2  0.2 102060  9060 ?Sl   15:53   0:02 
/usr/lib/vmware/viewagent/VMwareBlastServer/BlastServer
root  1479  0.0  0.1 139968  6528 ?Sl   15:53   0:00 desktopWorker 
-x /usr/lib/vmware/viewagent/bin/StartXServer.sh -d :100 -s 1 -p 13
root  1488  0.2  1.4 611572 56464 ?Sl   15:53   0:00 
/usr/lib/xorg/Xorg :100 -auth /var/vmware/viewagent/xauth/.xauth:100 -once 
-query 127.0.0.1 -config /usr/lib/vmware/viewagent/resource
root  1532  0.0  0.2 258560  8088 ?Sl   15:53   0:00 
gdm-session-worker [pam/gdm-launch-environment]
gdm   1535  0.0  0.0  25464  1528 ?Ss   15:53   0:00 
dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
gdm   1536  0.0  0.1  50244  4528 ?S15:53   0:00 dbus-daemon 
--nofork --print-address 4 --session
gdm   1537  0.0  0.3 551880 13892 ?Sl   15:53   0:00 
/usr/lib/gnome-session/gnome-session-binary --autostart 
/usr/share/gdm/greeter/autostart

Now, the SSO desktop for the VDI is on xorg display :100, and all of
this is launched by
/usr/lib/vmware/viewagent/DesktopDaemon/desktopDaemon.

The dbus-run-session runs a bunch of autostart scripts in
/usr/share/gdm/greeter/autostart, one of which starts up
SsoDBusNotify.py.

Now, when /usr/lib/vmware/viewagent/bin/SsoDBusNotify.py runs, it reads
in a SSO token generated by desktopDaemon from stdin, and then makes
sure the display matches what xorg is running on, and then sends a
UserAuthenticated signal to DBUS on '/org/vmware/viewagent/Credentials'
and 'org.vmware.viewagent.Credentials'.

Lets do this manually, since we are in KVM and not on an actual VMware
Horizon cluster.

Execute:

$ sudo /usr/lib/vmware/viewagent/bin/SsoDBusNotify.py -t sso -d :100

When asked, input the token: "12345DISPLAY:100".

The custom gnome-shell distributed by VMware listens on
org.vmware.viewagent.Credentials.D100 (yes, that is a per-display dbus
address) which then checks to see if the token is any good, and passes
it to PAM for processing.

PAM then calls the module gdm-vmwcred, which then talks to the SSSD and
krb5 PAM modules to authenticate against an AD server. But in our repro
environment, this won't work.

But the main thing is, if you check:

/var/log/auth.log:
Mar 22 15:55:51 ubuntu gdm-vmwcred]: pam_vmw_cred(gdm-vmwcred:auth): Failed to 
acquire user's credentials

and

/var/log/vmware/pam_vmw_log:
2021:03:22 15:55:51 : Authentication begins
2021:03:22 15:55:51 : SSOChannel_AcquireUserCredentials called.
2021:03:22 15:55:51 : VMWARE Token is invaild.
2021:03:22 15:55:51 : Failed to acquire user's credentials
2021:03:22 15:55:51 : Authentication ends

We see gnome-shell does infact call PAM.

On vanilla installs of gnome-shell, i.e. gnome-shell
3.28.4-0ubuntu18.04.3 and earlier, if you attempted to do this, gnome-
shell would not talk to PAM as it does not understand the per-display
dbus logic.

Now, on the 

[Desktop-packages] [Bug 1920121] Re: Unable to do anything after pressing the Super key

[Daniel van Vugt]

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

I can't reproduce the issue but the recurring message in your log
certainly sounds like it would explain clicking/focus problems:

  meta_window_set_stack_position_no_sync: assertion
'window->stack_position >= 0' failed

Since we already have bug 1871262 open for that I am going to mark this
as a duplicate.

** This bug has been marked a duplicate of bug 1871262
   gnome-shell crashes in meta_window_set_stack_position_no_sync: assertion 
'window->stack_position >= 0' failed

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

Title:
  Unable to do anything after pressing the Super key

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I press super key, the various application windows appear on desktop but i'm 
unable to do anything: 
  i can just click on the red 'X' top right of the window to close it but if i 
click on the window i can't get focus on it. to exit this situation i can only 
reboot so I was unable to open the problem while it was active. I can just 
attach the journal relative to it.
  The problem seems random, trying to reproduce it I had the problem 3 times 
out of 6 attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 19 08:49:44 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (18 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2
  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/1920121/+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 1871262] Re: gnome-shell freezes with meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashes in meta_window_set_stack_position_no_sync: assertion 
'window->stack_position >= 0' failed
+ gnome-shell freezes with meta_window_set_stack_position_no_sync: assertion 
'window->stack_position >= 0' failed

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

Title:
  gnome-shell freezes with meta_window_set_stack_position_no_sync:
  assertion 'window->stack_position >= 0' failed

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat 
integration will be disabled.
  Gjs-Message: 20:18:18.189: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
  Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.79/org/ayatana/NotificationItem/software_update_available
  Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch
  GNOME Shell-Message: 20:18:19.742: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

  (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Was the error I got after restarting Gnome after it froze when I
  closed Visual Studio Code but the right-click menu appeared for it
  after Ubuntu froze for a second because I had regions enabled on my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Mon Apr  6 20:16:51 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871262/+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 1842886] Re: Yaru-dark shell menus and dialogs are not dark

[Daniel van Vugt]

Starting in Ubuntu 21.04 this week, the shell menus are now always dark
:)

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

** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu)

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

Title:
  Yaru-dark shell menus and dialogs are not dark

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  When you selected a dark application theme, the gnome-shell top bar
  menus used to also switch to match the theme (ie light text on a dark
  background) - eg see the screenshot showing the top-bar calendar at
  https://micheleg.github.io/dash-to-dock/news/2015/03/01/approaching-
  gnome-3.16.html).

  This is no longer the case - see attached screenshot for yark-dark.
  It's the same with adwaita-dark.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  5 16:01:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (65 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  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/yaru-theme/+bug/1842886/+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 1920130] Re: System icons missing in kubuntu 21.04

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => qtdeclarative-opensource-src
(Ubuntu)

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property "visible"
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: 
QML GridView: Binding loop detected for pro
  perty "rightPadding"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or 

[Desktop-packages] [Bug 1886592] Re: Add support for VMware Horizon SSO to gnome-shell

[Matthew Ruffell]

Performing verification for gnome-shell in Focal.

During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.

I will begin by walking through the SSO workflow, based around the
custom gnome-shell package distributed by VMware.

Firstly, start with a fresh Focal Desktop VM, all up to date.

Visit the VMware website, specifically this link:

https://my.vmware.com/en/web/vmware/evalcenter?p=horizon-eval-8

Sign up for a VMware account and reach the VMware Horizon 8 evaluation
download page. The next step is to locate the "Linux Agent x86_64". The
file is named

VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz

If you have difficulty in obtaining this file and want to reproduce,
please message me.

Download and copy to the Focal VM.

$ scp VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz 
ubuntu@target:~/
$ ssh ubuntu@target
$ tar -xf VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770.tar.gz
$ cd VMware-horizonagent-linux-x86_64-2012-8.1.0-17336770

Next, install the VMware Horizon Linux Agent by following the
instructions at:

https://docs.vmware.com/en/VMware-Horizon-7/7.13/linux-desktops-
setup/GUID-B4111821-34F2-465B-B290-FC2070EFCB5A.html

$ sudo apt install libpam-pkcs11
$ sudo apt install libnss3-tools
$ sudo apt install open-vm-tools
$ sudo ./install_viewagent.sh -T yes

Now, this will install a custom patched gnome-shell library, which
contains the following patches:

https://paste.ubuntu.com/p/q4fkNrqHQT/

You can find this, and more in the VMware-horizonagent-linux-
x86_64-2012-8.1.0-17336770/sso directory.

Reboot the VM.

When it comes back up, run "ps aux". You will see:

oot1410  0.0  0.1 345920 10840 ?Sl   15:09   0:00 
/usr/lib/vmware/viewagent/DesktopDaemon/desktopDaemon
root1411  2.1  0.1  77128  9208 ?Sl   15:09   0:00 
/usr/lib/vmware/viewagent/VMwareBlastServer/BlastServer
root1463  0.0  0.0 107056  6812 ?Sl   15:09   0:00 
desktopWorker -x /usr/lib/vmware/viewagent/bin/StartXServer.sh -d :100 -s 1 -p 
13
root1477  1.4  0.7 1129928 61244 ?   Sl   15:09   0:00 
/usr/lib/xorg/Xorg :100 -auth /var/vmware/viewagent/xauth/.xauth:100 -once 
-query 127.0.0.1 -config /usr/lib/vmware/viewagent/resour
root1530  0.0  0.1 177392  9172 ?Sl   15:09   0:00 
gdm-session-worker [pam/gdm-launch-environment]
gdm 1535  0.0  0.0   5300  1108 ?Ss   15:09   0:00 
dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
gdm 1536  0.2  0.0   7556  4672 ?S15:09   0:00 dbus-daemon 
--nofork --print-address 4 --session
gdm 1537  0.3  0.2 568700 16920 ?Sl   15:09   0:00 
/usr/libexec/gnome-session-binary --systemd --autostart 
/usr/share/gdm/greeter/autostart

Now, the SSO desktop for the VDI is on xorg display :100, and all of
this is launched by
/usr/lib/vmware/viewagent/DesktopDaemon/desktopDaemon.

The dbus-run-session runs a bunch of autostart scripts in
/usr/share/gdm/greeter/autostart, one of which starts up
SsoDBusNotify.py.

Now, when /usr/lib/vmware/viewagent/bin/SsoDBusNotify.py runs, it reads
in a SSO token generated by desktopDaemon from stdin, and then makes
sure the display matches what xorg is running on, and then sends a
UserAuthenticated signal to DBUS on '/org/vmware/viewagent/Credentials'
and 'org.vmware.viewagent.Credentials'.

Lets do this manually, since we are in KVM and not on an actual VMware
Horizon cluster.

Execute:

$ sudo /usr/lib/vmware/viewagent/bin/SsoDBusNotify.py -t sso -d :100

When asked, input the token: "12345DISPLAY:100".

The custom gnome-shell distributed by VMware listens on
org.vmware.viewagent.Credentials.D100 (yes, that is a per-display dbus
address) which then checks to see if the token is any good, and passes
it to PAM for processing.

PAM then calls the module gdm-vmwcred, which then talks to the SSSD and
krb5 PAM modules to authenticate against an AD server. But in our repro
environment, this won't work.

But the main thing is, if you check:

/var/log/auth.log:
Mar 22 15:14:45 ubuntu gdm-vmwcred]: pam_vmw_cred(gdm-vmwcred:auth): Failed to 
acquire user's credentials

and

/var/log/vmware/pam_vmw_log:
2021:03:22 15:14:45 : Authentication begins
2021:03:22 15:14:45 : SSOChannel_AcquireUserCredentials called.
2021:03:22 15:14:45 : VMWARE Token is invaild.
2021:03:22 15:14:45 : Failed to acquire user's credentials
2021:03:22 15:14:45 : Authentication ends

We see gnome-shell does infact call PAM.

On vanilla installs of gnome-shell, i.e. gnome-shell
3.36.4-1ubuntu1~20.04.2 and earlier, if you attempted to do this, gnome-
shell would not talk to PAM as it does not understand the per-display
dbus logic.

Now, on the customer environment, SSO works fine with the custom gnome-
shell library, as they are correctly configured for SSSD / krb5 to their
AD server.

Now, let's 

[Desktop-packages] [Bug 1920036] Re: [DisplayLink] screen flicker on gnome with t450s with ultra dock

[Daniel van Vugt]

"evdi" I think is the kernel driver for DisplayLink.

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

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

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

Title:
  [DisplayLink] screen flicker on gnome with t450s with ultra dock

Status in evdi package in Ubuntu:
  New

Bug description:
  picture on monitor connected to DisplayPort flickers occasionally. between 1 
and 20 times per hour.
  searched for similar bugs or problems, related to docking station. Does not 
happen when using laptop standalone / connect screen manually. 

  DisplayLink Driver is installed/compiled from official website.

  whenever the flickering happens, this appears in log:

  "libinput error: client bug: timer event20 debounce short: scheduled
  expiry is in the past (-10ms), your system is too slow"

  anything I can contribute? fix? 
  I tried to get daily builds of intel-driver but that broke wayland/gdm so I 
rolled back.

  only link I could find that seems relevant is
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572667 - which
  expired.

  thanks

  
  Andreas

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Mar 18 16:18:08 2021
  InstallationDate: Installed on 2021-03-13 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920036/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit

[Daniel van Vugt]

Looks like the fix is in 21.04 now. Not sure about the plan for LTS.

** Changed in: yaru-theme (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  New
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

[Daniel van Vugt]

I think having a secondary keyboard can be the trigger for both this bug
and delays in responses (bug 108). But that does not mean this bug
is related to delays in responses.

If you are using two or more keyboards then please subscribe to bug
108 instead of this one.

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

Title:
  Window manager warning: Overwriting existing binding of keysym 37 with
  keysym 37 (keycode 10).

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

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1920693] Re: Screen Tearing issues

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1846398
   [modeset] xrandr scaling has significant visible tearing in Xorg sessions

** This bug is no longer a duplicate of bug 1846398
   [modeset] xrandr scaling has significant visible tearing in Xorg sessions

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** This bug has been marked a duplicate of bug 1846398
   [modeset] xrandr scaling has significant visible tearing in Xorg sessions

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

Title:
  Screen Tearing issues

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I am having some weird screen tearing issues. It worsens while viewing
  videos especially in full screen mode. But is is always present like
  in scrolling etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 22 03:59:36 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics [1d72:1901]
  InstallationDate: Installed on 2021-03-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: TIMI Mi  NoteBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=4fc15fe0-df3a-4920-8bbb-9f92cc23a989 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: TIMI
  dmi.bios.version: XMRCM400P0904
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnTIMI:bvrXMRCM400P0904:bd04/01/2020:br1.9:efr1.4:svnTIMI:pnMiNoteBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: Mi  NoteBook 14
  dmi.product.sku: TM1901-27749
  dmi.sys.vendor: TIMI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920693/+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 1920239] Re: Icons in the background when I click on "show applications"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Icons in the background when I click on "show applications"

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

Bug description:
  Ubuntu Hirsute Hippo (development branch)
  gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

  BUG
  When I press on "Show applications" on the dock the animation starts and at 
the end I end up with the application icons in the background. The icons are 
partly overlaid by the program preview.

  Video of the bug https://youtu.be/eodtSxRRiNg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1920239/+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 1920670] Re: screen glitches

[Daniel van Vugt]

Please:

1. Attach screenshots or photos of the whole screen when the problem
happens; and

2. Check if the problem only occurs after the system resumes from sleep.

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

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

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

Title:
  screen glitches

Status in Ubuntu:
  Incomplete

Bug description:
  Time by time screen glitches for some seconds. This problem happens
  independent of PC load (with both Intel and NVIDIA graphic cards).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-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  460.39  Thu Jan 21 21:54:06 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 21 16:41:39 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! 
Diff between built and installed module!) (WARNING! Diff between built and 
installed module!) (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0906]
 Subsystem: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] 
[10de:]
  InstallationDate: Installed on 2021-03-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Precision 5540
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=d9d861fa-ee39-4c30-a652-d4c285927a01 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 0WWHJ2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd12/14/2020:br1.9:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5540
  dmi.product.sku: 0906
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1920670/+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 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel

[Ubuntu Tinkerer]

I don't understand. I currently have nvidia-driver-460 and linux kernel
versions 5.8.0-43 to 45 installed (45 is being used). But I have no
linux-modules-nvidia-460 packages installed. E.g. I don't have linux-
modules-nvidia-460-5.8.0-45-generic and neither for 44 and 43. Is this
ok or should I install linux-modules-nvidia-460-5.8.0-XY-generic.

If the linux-modules-nvidia-460-5.8.0-XY-generic packages are not
necessary for my system then why were they pre-installed in the first
place, especially since they caused problems for me when I wanted to
downgrade nvidia-driver-450?

Please if you can answer my questions here and if you don't regard these
as issues then close this bug report.

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

Title:
  After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't
  update nvidia modules in kernel

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  SYSTEM:

  Laptop: ASUS ROG GL552VW
  OS: Ubuntu 20.04.2 LTS
  GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics
  Linux kernel version: 5.8.0-44-generic

  SUMMARY:

  From a fresh working install of Ubuntu 20.04, I downgraded from
  nvidia-driver-460 by installing nvidia-driver-440 (which actually is a
  transitional package to nvidia-driver-450 but I didn't know this).
  After reboot I couldn't reach login-screen and instead got a black
  screen.

  Problem was that sudo apt-get install nvidia-driver-440 did not insert
  nvidia modules v450 in kernel since never versions v460 were found.

  This was solved by uninstalling linux-modules-nvidia-460 packages and
  instead installing linux-modules-nvidia-450 packages (see WORKAROUND
  below for instructions).

  STEPS TO REPRODUCE:

  Install Ubuntu 20.04. During installation, allow for the installation
  of proprietary drivers.

  Once Ubuntu 20.04 has started, open a terminal and run the following:

  sudo add-apt-repository ppa:graphics-drivers/ppa
  sudo apt-get update
  sudo apt-get install nvidia-driver-440
  sudo shutdown reboot now

  PROBLEM:

  After reboot, you can't reach login screen. Instead you get stuck
  during bootup.

  WORKAROUND:

  WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE
  INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL
  VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to
  see what linux kenrel versions you have installed.

  Remove the linux-modules-nvidia-460 packages and install the
  corresponding linux-modules-nvidia-450 packages. In my case I had
  Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed
  so I did as follows from recovery mode with network (instead of
  entering recovery mode, you should be able to press CTRL+ALT+F1 from
  the blank screen after bootup, login with username and password and
  then running these commands):

  sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic 
linux-modules-nvidia-460-5.8.0-43-generic
  sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic 
linux-modules-nvidia-450-5.8.0-43-generic
  sudo shutdown reboot now

  QUESTION:

  Why was the linux-modules-nvidia-460 packages installed by the Ubuntu
  installer to begin with? I ask since I later removed the linux-
  modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the
  Additional Drivers GUI to update back to nvidia-driver-460. Now linux-
  modules-nvidia-460 packages are NOT installed but the following still
  outputs 460:

  modinfo nvidia | grep -i version

  LOG:

  This is a relevant part of /var/log/apt/term.log for when I installed
  nvidia-driver-440

  nvidia.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-modeset.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-modeset.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-drm.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-drm.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-uvm.ko:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/

  This is a relevant part of /var/log/apt/term.log for when I installed
  packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules-
  nvidia-450-5.8.0-43-generic

  Building module:
  cleaning build area...

[Desktop-packages] [Bug 1919143] Re: Update mutter to 3.36.9

[Daniel van Vugt]

The "About" page should be ignored on Ubuntu because it displays only
the version of the gnome-desktop3-data package.

We don't have the luxury of ensuring all packages are always the same
version so you should check your package versions instead of using the
About page.

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

Title:
  Update mutter to 3.36.9

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  This is a request to update mutter to version >= 3.36.8 to fix various
  issues that have been fixed upstream.

  See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654
  for the original mutter issue report that will be fixed by 3.36.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmutter-6-0 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 15 10:40:58 2021
  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/1919143/+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 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel

[Ubuntu Tinkerer]

Sorry for my late reply.

What do you mean by "... in the live session"? Instead I executed that
command from my Ubuntu installation (where I observed the bug) and the
output is here further below.

@Dimitri are you saying that securedboot devices should avoid using the
device drivers PPA? Also I'm currently on nvidia-driver-460 but I have
no linux-modules-nvidia-460 packages installed. My system seems to work
correctly. Is it OK that I don't have the linux-modules-nvidia-460
packages installed?

Output of "sudo ubuntu-drivers list":

nvidia-driver-418-server, (kernel modules provided by 
linux-modules-nvidia-418-server-generic-hwe-20.04)
nvidia-driver-450-server, (kernel modules provided by 
linux-modules-nvidia-450-server-generic-hwe-20.04)
nvidia-driver-460, (kernel modules provided by 
linux-modules-nvidia-460-generic-hwe-20.04)
nvidia-driver-450, (kernel modules provided by 
linux-modules-nvidia-450-generic-hwe-20.04)
nvidia-driver-390, (kernel modules provided by 
linux-modules-nvidia-390-generic-hwe-20.04)
nvidia-driver-460-server, (kernel modules provided by 
linux-modules-nvidia-460-server-generic-hwe-20.04)

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

Title:
  After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't
  update nvidia modules in kernel

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  SYSTEM:

  Laptop: ASUS ROG GL552VW
  OS: Ubuntu 20.04.2 LTS
  GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics
  Linux kernel version: 5.8.0-44-generic

  SUMMARY:

  From a fresh working install of Ubuntu 20.04, I downgraded from
  nvidia-driver-460 by installing nvidia-driver-440 (which actually is a
  transitional package to nvidia-driver-450 but I didn't know this).
  After reboot I couldn't reach login-screen and instead got a black
  screen.

  Problem was that sudo apt-get install nvidia-driver-440 did not insert
  nvidia modules v450 in kernel since never versions v460 were found.

  This was solved by uninstalling linux-modules-nvidia-460 packages and
  instead installing linux-modules-nvidia-450 packages (see WORKAROUND
  below for instructions).

  STEPS TO REPRODUCE:

  Install Ubuntu 20.04. During installation, allow for the installation
  of proprietary drivers.

  Once Ubuntu 20.04 has started, open a terminal and run the following:

  sudo add-apt-repository ppa:graphics-drivers/ppa
  sudo apt-get update
  sudo apt-get install nvidia-driver-440
  sudo shutdown reboot now

  PROBLEM:

  After reboot, you can't reach login screen. Instead you get stuck
  during bootup.

  WORKAROUND:

  WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE
  INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL
  VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to
  see what linux kenrel versions you have installed.

  Remove the linux-modules-nvidia-460 packages and install the
  corresponding linux-modules-nvidia-450 packages. In my case I had
  Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed
  so I did as follows from recovery mode with network (instead of
  entering recovery mode, you should be able to press CTRL+ALT+F1 from
  the blank screen after bootup, login with username and password and
  then running these commands):

  sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic 
linux-modules-nvidia-460-5.8.0-43-generic
  sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic 
linux-modules-nvidia-450-5.8.0-43-generic
  sudo shutdown reboot now

  QUESTION:

  Why was the linux-modules-nvidia-460 packages installed by the Ubuntu
  installer to begin with? I ask since I later removed the linux-
  modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the
  Additional Drivers GUI to update back to nvidia-driver-460. Now linux-
  modules-nvidia-460 packages are NOT installed but the following still
  outputs 460:

  modinfo nvidia | grep -i version

  LOG:

  This is a relevant part of /var/log/apt/term.log for when I installed
  nvidia-driver-440

  nvidia.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-modeset.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-modeset.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-drm.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-drm.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying 

[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi

[Daniel van Vugt]

Fixed upstream in https://github.com/micheleg/dash-to-dock/pull/1366

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Confirmed => Fix Committed

** Tags added: fixed-upstream

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

Title:
  Syslog is flooded with Object St.Bin (0x565425162c80), has been
  already deallocated — impossible to set any property on it. This might
  be caused by the object having been destroyed from C code using
  something such as destroy(), dispose(), or remove() vfuncs.

Status in Dash to dock:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  The syslog is full of these messages, continuously written all day
  long

  Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 
0x56541fffb220 ==
  Nov 25 07:46:42 pc1 gnome-shell[2980]: #0   7ffddbfa1940 b   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1839cb6a2420 @ 208)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 07:42:45 2020
  InstallationDate: Installed on 2014-06-03 (2366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+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 1919972] Re: Icon grid flashes briefly before the spring animation

[Daniel van Vugt]

Fixed upstream in https://github.com/micheleg/dash-to-dock/pull/1361

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-upstream

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

Title:
  Icon grid flashes briefly before the spring animation

Status in Dash to dock:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  When clicking 'Show Applications', the icon grid flashes up briefly
  before vanishing again and the spring animation reveals it properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1919972/+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 1920693] [NEW] Screen Tearing issues

[Aryan Pathania]

Public bug reported:

I am having some weird screen tearing issues. It worsens while viewing
videos especially in full screen mode. But is is always present like in
scrolling etc.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 22 03:59:36 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Xiaomi UHD Graphics [1d72:1901]
InstallationDate: Installed on 2021-03-18 (2 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
 |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: TIMI Mi  NoteBook 14
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=4fc15fe0-df3a-4920-8bbb-9f92cc23a989 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2020
dmi.bios.release: 1.9
dmi.bios.vendor: TIMI
dmi.bios.version: XMRCM400P0904
dmi.board.name: TM1901
dmi.board.vendor: TIMI
dmi.chassis.type: 10
dmi.chassis.vendor: TIMI
dmi.ec.firmware.release: 1.4
dmi.modalias: 
dmi:bvnTIMI:bvrXMRCM400P0904:bd04/01/2020:br1.9:efr1.4:svnTIMI:pnMiNoteBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
dmi.product.family: Mi Laptop
dmi.product.name: Mi  NoteBook 14
dmi.product.sku: TM1901-27749
dmi.sys.vendor: TIMI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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

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

Title:
  Screen Tearing issues

Status in xorg package in Ubuntu:
  New

Bug description:
  I am having some weird screen tearing issues. It worsens while viewing
  videos especially in full screen mode. But is is always present like
  in scrolling etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 22 03:59:36 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics [1d72:1901]
  InstallationDate: Installed on 2021-03-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: TIMI Mi  NoteBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=4fc15fe0-df3a-4920-8bbb-9f92cc23a989 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: TIMI
  dmi.bios.version: XMRCM400P0904
  dmi.board.name: 

[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Bob H]

successfully create a thumb drive from:
hirsute-desktop-amd64.iso   2021-03-21 05:492.7GDesktop image 
for 64-bit PC (AMD64) computers (standard download)
boot from thumb drive:
"Installation failed - KDialog \n
The installer encountered an unrecoverable error.
A desktop session will now be run so that you may
investigate the problem or try installing again"

Installation cannot proceed.

I don't have the know how to be able to investigate, unfortunately.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1920690] [NEW] File chooser dialog cause flatpak applications to hang in KDE

[Sergio Callegari]

Public bug reported:

Flatpak seems to have serious issues on kubuntu 20.04, at least with
some applications that immediately hang when a file dialog is shown.

One of them that makes the issue well reproducible for me on kubuntu
20.04 is shotcut
(https://www.flathub.org/apps/details/org.shotcut.Shotcut). Just install
it and then press the "Projects Folder" button in the "New Project" to
make the app hang.

Trying the more recent flatpak on the ppa:alexlarsson/flatpak ppa, which
is at 1.10.2 provides a slightly less catastrophic outcome, since the
app doesn't hang. However the "open" button of the file dialog does not
work and the dialog cannot be closed.

The issue may have to do with the xdg-desktop-portal-kde rather than
flatpak itself.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: flatpak (not installed)
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Mar 21 22:13:27 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (399 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: flatpak
UpgradeStatus: Upgraded to focal on 2020-05-23 (302 days ago)

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

Title:
  File chooser dialog cause flatpak applications to hang in KDE

Status in flatpak package in Ubuntu:
  New

Bug description:
  Flatpak seems to have serious issues on kubuntu 20.04, at least with
  some applications that immediately hang when a file dialog is shown.

  One of them that makes the issue well reproducible for me on kubuntu
  20.04 is shotcut
  (https://www.flathub.org/apps/details/org.shotcut.Shotcut). Just
  install it and then press the "Projects Folder" button in the "New
  Project" to make the app hang.

  Trying the more recent flatpak on the ppa:alexlarsson/flatpak ppa,
  which is at 1.10.2 provides a slightly less catastrophic outcome,
  since the app doesn't hang. However the "open" button of the file
  dialog does not work and the dialog cannot be closed.

  The issue may have to do with the xdg-desktop-portal-kde rather than
  flatpak itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: flatpak (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Mar 21 22:13:27 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (399 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: flatpak
  UpgradeStatus: Upgraded to focal on 2020-05-23 (302 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1920690/+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 1920690] [NEW] File chooser dialog cause flatpak applications to hang in KDE

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Flatpak seems to have serious issues on kubuntu 20.04, at least with
some applications that immediately hang when a file dialog is shown.

One of them that makes the issue well reproducible for me on kubuntu
20.04 is shotcut
(https://www.flathub.org/apps/details/org.shotcut.Shotcut). Just install
it and then press the "Projects Folder" button in the "New Project" to
make the app hang.

Trying the more recent flatpak on the ppa:alexlarsson/flatpak ppa, which
is at 1.10.2 provides a slightly less catastrophic outcome, since the
app doesn't hang. However the "open" button of the file dialog does not
work and the dialog cannot be closed.

The issue may have to do with the xdg-desktop-portal-kde rather than
flatpak itself.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: flatpak (not installed)
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Mar 21 22:13:27 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (399 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: flatpak
UpgradeStatus: Upgraded to focal on 2020-05-23 (302 days ago)

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


** Tags: amd64 apport-bug focal
-- 
File chooser dialog cause flatpak applications to hang in KDE
https://bugs.launchpad.net/bugs/1920690
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to flatpak in Ubuntu.

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

[Desktop-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color

[Norbert]

** Tags added: hirsute

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

Title:
  Human, Human-Clearlooks and other themes have incorrect gray window
  title color

Status in community-themes package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in human-theme package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
  2. Install Human theme from `human-theme` package
  3. Select Human theme from `mate-control-center` Appearance

  Expected results:
  window title color is set to Ubuntu's orange (#FFBE6B)

  Actual results:
  window title color is set to different gray/silver color (#a5a5a2)

  Note:
  other themes are affected too.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: human-theme 0.39.2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 15:43:03 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170925.1)
  PackageArchitecture: all
  SourcePackage: human-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS, 18.10, 19.04 and 19.10

[Norbert]

** Tags added: hirsute

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS, 18.10, 19.04 and 19.10

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1810745/+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 1887220] Re: Clicking on preinstalled /usr/share/applications/vim.desktop ends with "There was an error launching the application." and Vim is not launched

[Norbert]

** Tags removed: eoan
** Tags added: hirsute

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

Title:
  Clicking on preinstalled  /usr/share/applications/vim.desktop ends
  with "There was an error launching the application." and Vim is not
  launched

Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE installed
  2. Open Caja, navigate to 

 /usr/share/applications/

  3. Click on Vim

  Expected result:
  * Vim is launched

  Actual result:
  * Vim is not launched, the error window is shown with text "There was an 
error launching the application."

  Notes:

  the /usr/share/applications/vim.desktop refers to `vim` executable which is 
not installed.
  The /usr/share/applications/vim.desktop came from 

  ```
  $ dpkg -S /usr/share/applications/vim.desktop 
  vim-common: /usr/share/applications/vim.desktop

  $ aptitude why vim-common 
  i   vim-tiny Depends vim-common (= 2:7.4.1689-3ubuntu1.2)

  $ aptitude why vim-tiny 
  i   ubuntu-minimal Depends vim-tiny
  ```

  So it is a dependency issue. Having vim.desktop without installed `vim` 
executable is useless.
  All Ubuntu versions are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-minimal 1.361.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Jul 11 11:05:44 2020
  InstallationDate: Installed on 2018-08-07 (703 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1887220/+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 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display

[Axel Hack]

nut shure about the package

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

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

Title:
  Lenovo x1 Yoga freeze after stylus touches the display

Status in libwacom package in Ubuntu:
  New

Bug description:
  Had no problem with stylus. Since one of the last updates the stylus
  freezes the notebook. No reaction to nothing. Only power off by
  holding hardware button works. Is also mentionned in
  https://askubuntu.com/questions/1324000/thinkpad-yoga-x1-gen-2
  -freezes-completely-when-stylus-is-used-ubuntu-20-04-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1920682/+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 1920036] Re: [DisplayLink] screen flicker on gnome with t450s with ultra dock

[Andreas]

greetings!

So.. what exactly is this "evdi" that you were mentioning? 
I just returned the laptop from a few hours unattended (did not suspend, just 
lock / walk away) and was greeted by flickering, this time only a part of the 
screen but all the time. 

the flicker that I usually see is short, then results in a black screen
for 2-10 seconds, then it's all good again.

This time, it was ongoing and the syslog was full of those:

mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected
mrt 21 21:32:12 moya kernel: evdi: [D] evdi_detect:94 (dev=0) poll connector 
state: disconnected

undock > dock and all was good again.

still can't correltate the event.. sometimes hours pass without a
flicker, then 10 per hour.

anything else I can do/test?

thanks for any hints


Andreas

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

Title:
  [DisplayLink] screen flicker on gnome with t450s with ultra dock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  picture on monitor connected to DisplayPort flickers occasionally. between 1 
and 20 times per hour.
  searched for similar bugs or problems, related to docking station. Does not 
happen when using laptop standalone / connect screen manually. 

  DisplayLink Driver is installed/compiled from official website.

  whenever the flickering happens, this appears in log:

  "libinput error: client bug: timer event20 debounce short: scheduled
  expiry is in the past (-10ms), your system is too slow"

  anything I can contribute? fix? 
  I tried to get daily builds of intel-driver but that broke wayland/gdm so I 
rolled back.

  only link I could find that seems relevant is
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572667 - which
  expired.

  thanks

  
  Andreas

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Mar 18 16:18:08 2021
  InstallationDate: Installed on 2021-03-13 (5 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  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/1920036/+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 1920682] [NEW] Lenovo x1 Yoga freeze after stylus touches the display

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Had no problem with stylus. Since one of the last updates the stylus
freezes the notebook. No reaction to nothing. Only power off by holding
hardware button works. Is also mentionned in
https://askubuntu.com/questions/1324000/thinkpad-yoga-x1-gen-2-freezes-
completely-when-stylus-is-used-ubuntu-20-04-2

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


** Tags: bot-comment
-- 
Lenovo x1 Yoga freeze after stylus touches the display
https://bugs.launchpad.net/bugs/1920682
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libwacom in Ubuntu.

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

[Desktop-packages] [Bug 13319] Re: nautilus should sort by extensions

[Goury]

2021 and we are still fed shit

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

Title:
  nautilus should sort by extensions

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In Warty I have a folder with tons of still pics, bmp and jpg, and a few WMV
  video files.
  Normally when I sort them by type, all the video files are put the bottom, 
which
  make sit easy to find them.

  Now with Hoary, it doesn't work anymore, the WMV files are in the middle of 
all
  the bmp and jpg files, it's a pain to find them :o(

  I think Warty used the file extension to sort the files, hence "WMV" came 
after
  "bmp" then "jpg".
  But it looks like Hoary uses the "MIME" (?) description.

  "bmp" is called "Windows BMP image" and "WMV" is called "Microsfot WMV video".
  "Windows" comes after "Microsoft", and here you go, the video files end up 
lost
  in the middle of all the other image types :-/
  Is there a way to change the sorting mechanism/method back to what it used to 
be
  ? Or is it configurable somewhere ?

  http://bugzilla.gnome.org/show_bug.cgi?id=168663:
  http://bugzilla.gnome.org/show_bug.cgi?id=168663

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/13319/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Leandro]

The command 

sudo hda-verb /dev/snd/hwC0D0 0x1a 0x707 0x05

works for me, but the patch proposed (I added the files), do not seem to
be working after reboots. Currently I have to run the command above
everytime I reboot.

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 

[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

[Butterfly]

Hi @pigeonskiller,

nvidia-340 driver is not required any patch for kernel 5.12.

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

Title:
  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  As usual I have opened this (no more) new bug report...

  As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
  needed for old Nvidia 340.108 drivers, that is, with each release of a
  new kernel...

  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.11 is not yet available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Anyway thanks for your great contribution to community and hope you
  publish new patched drivers without having to always report the same
  bug...

  Good day to all the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 36156]

[Ilmari-lauhakangas]

(In reply to Alexandr from comment #4)
> Created attachment 103135 [details]
> Comparative screenshot of MS Word 2007 and LO Writer 4.3.0
> 
> Reproducible with LibreOffice 4.2.5 and 4.3.0 on Debian and Windows 7. I
> attach a screenshot which demonstrates a correct representation and the
> issue. I do not see any problem with font clor in a footer.

The box in page 5 is now in the correct position, but the position
problem on page 1 persists

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 005adbefc746f9024adcf572c287dc061acbcf00
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded

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

Title:
  [Upstream] [hardy] Writer mis-shifts OLE object in Microsoft Word .doc

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
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.04
  Release:11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/36144/+attachment/8047/+files/pd18.doc
  && lowriter -nologo pd18.doc

  it looks as it does in Word.

  4) What happens instead is the OLE object at the top of page 1 is mis-
  shifted to the left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/36156/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Rik Mills]

Testing a no change rebuild of ubiquity 21.04.11 in a PPA, it seems this
is all that is required to remedy the crash with the latest ISO build.

https://launchpad.net/~rikmills/+archive/ubuntu/hirsute/+sourcepub/12212560
/+listing-archive-extra

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1913333] Re: Calc auto-filter menu inaccessible with fractional scaling enabled

[Christians]

THis problem made working very troublesome and I therefore upgraded to
21.04 containing LibreOffice 7.1.2.1.. The problem has not resurfaced
for a week in the development version and I consider it solved for me.

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

Title:
  Calc auto-filter menu inaccessible with fractional scaling enabled

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  PROBLEM
  The auto-filter pull-down menu becomes inaccessible the very moment I move 
the mouse down to access the filter menu. This happens most of the time, but 
not always, when fractional scaling is not 100% on my 4K monitor. The menu 
remains inaccessible for all other scaling factors but 100%.

  FREQUENCY
  This happens quite often, but not always, and makes working in CALC with 
fractional scaling on impossible. Sometimes changing fractional scaling back to 
100% and then say to 150% fixes the issue. But most of the time the only way 
out is to switch the screen to 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libreoffice-core 1:7.0.3-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 26 18:19:16 2021
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (93 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/191/+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 1916640] Kernel 5.12 patch for Nvidia 340.108

[ppp]

Hi Butterfly,

thanks for the info. Actually I am on Kubuntu 20.04 with kernel 5.11.8
but I'll test your drivers on Hirsute in a month as soon as it becomes
available.

Just for info there is already a patch for kernel 5.12.
If interested you may take a look here:

http://rglinuxtech.com/?p=2896

Have a nice day.


 
> Il 21/03/2021 00:23 Butterfly <1916...@bugs.launchpad.net> ha scritto:
> 
>  
> Hi,
> 
> Nvidia-340 driver added to PPA for hirsute (21.04) base. You can install
> nvdia-340 driver from PPA. The driver in PPA repository currently
> supports up to 5.12 of Linux kernel .
> https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy
> 
> PPA repository supports bionic, focal, groovy and hirsute bases.
> 
> ---
> 
> Nvidia-340 driver's official support for hirsute base is no longer
> available.
> 
> nvidia-graphics-drivers-340 (340.108-0ubuntu8) hirsute; urgency=medium
> 
>   * Drop support for the 340 driver, in favour of the nouveau driver
> since it is no longer supported by NVIDIA:
> 
> https://nvidia.custhelp.com/app/answers/detail/a_id/3142/~/support-timeframes-for-unix-legacy-gpu-releases
> 
>  -- Alberto Milone <...> Wed, 10 Mar 2021 17:18:43 +0100
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1916640
> 
> Title:
>   Nvidia 340.108 fails to install with kernels 5.11.x - new patches
>   needeed
> 
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   As usual I have opened this (no more) new bug report...
> 
>   As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
>   needed for old Nvidia 340.108 drivers, that is, with each release of a
>   new kernel...
> 
>   Nvidia 340.108 fails to install with kernels 5.11.x - new patches
>   needeed
> 
>   Just to inform develepers that a new patch for Nvidia 340.108 and
>   kernel 5.11 is not yet available here:
> 
>   
> https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/
> 
>   Anyway thanks for your great contribution to community and hope you
>   publish new patched drivers without having to always report the same
>   bug...
> 
>   Good day to all the developers.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions

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

Title:
  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  As usual I have opened this (no more) new bug report...

  As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
  needed for old Nvidia 340.108 drivers, that is, with each release of a
  new kernel...

  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.11 is not yet available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Anyway thanks for your great contribution to community and hope you
  publish new patched drivers without having to always report the same
  bug...

  Good day to all the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Rik Mills]

** Summary changed:

- Ubiquity crash on try/install and from live session with "malloc(): unaligned 
tcache chunk detected"
+ Ubiquity KDE crash on try/install and from live session with "malloc(): 
unaligned tcache chunk detected"

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

[Bugzilla-gtalbot]

(In reply to YUKI "Piro" Hiroshi from comment #100)
> This is a testcase for my XHTML Ruby Support addon. There are some examples
> of "broken" markups.
> http://www.cozmixng.org/repos/piro/rubysupport/trunk/tests/general.html

http://www.gtalbot.org/BrowserBugsSection/CSS3Ruby/yuki-hiroshi-
example.xhtml

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

Title:
  Gecko Engine does not support the XHTML 1.1 ruby tag

Status in Epiphany Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: epiphany-browser

  Visit a website such as http://icculus.org/~mongoose/index-jp2.html --
  notice Ruby tags are ignored.  This works in IE and can work with a
  plugin in firefox ( http://piro.sakura.ne.jp/xul/_rubysupport.html.en
  ).  Ruby is part of the XHTML 1.1 standard.

  
  http://www.w3.org/TR/ruby/

  ProblemType: Bug
  Architecture: amd64
  Date: Sun May 13 11:42:29 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/epiphany
  Package: epiphany-browser 2.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/epiphany
  ProcCwd: /home/mongoose
  ProcEnviron:
   LANGUAGE=en_US:en
   
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: epiphany-browser
  Uname: Linux namie 2.6.20-14-generic #2 SMP Thu Apr 12 22:25:02 UTC 2007 
x86_64 GNU/Linux

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

[Sledru]

I think we can close it now.
Feel free to reopen if I am wrong.

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

Title:
  Gecko Engine does not support the XHTML 1.1 ruby tag

Status in Epiphany Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: epiphany-browser

  Visit a website such as http://icculus.org/~mongoose/index-jp2.html --
  notice Ruby tags are ignored.  This works in IE and can work with a
  plugin in firefox ( http://piro.sakura.ne.jp/xul/_rubysupport.html.en
  ).  Ruby is part of the XHTML 1.1 standard.

  
  http://www.w3.org/TR/ruby/

  ProblemType: Bug
  Architecture: amd64
  Date: Sun May 13 11:42:29 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/epiphany
  Package: epiphany-browser 2.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/epiphany
  ProcCwd: /home/mongoose
  ProcEnviron:
   LANGUAGE=en_US:en
   
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: epiphany-browser
  Uname: Linux namie 2.6.20-14-generic #2 SMP Thu Apr 12 22:25:02 UTC 2007 
x86_64 GNU/Linux

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

[Cmills-4]

I checked out Ruby documentation, and it turns out we were doin g pretty
well; we were just missing a page on the  element. I've added this
now, along with associated compat data and an interactive example:

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rb
https://github.com/mdn/browser-compat-data/pull/2422
https://github.com/mdn/interactive-examples/pull/1016

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

Title:
  Gecko Engine does not support the XHTML 1.1 ruby tag

Status in Epiphany Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: epiphany-browser

  Visit a website such as http://icculus.org/~mongoose/index-jp2.html --
  notice Ruby tags are ignored.  This works in IE and can work with a
  plugin in firefox ( http://piro.sakura.ne.jp/xul/_rubysupport.html.en
  ).  Ruby is part of the XHTML 1.1 standard.

  
  http://www.w3.org/TR/ruby/

  ProblemType: Bug
  Architecture: amd64
  Date: Sun May 13 11:42:29 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/epiphany
  Package: epiphany-browser 2.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/epiphany
  ProcCwd: /home/mongoose
  ProcEnviron:
   LANGUAGE=en_US:en
   
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: epiphany-browser
  Uname: Linux namie 2.6.20-14-generic #2 SMP Thu Apr 12 22:25:02 UTC 2007 
x86_64 GNU/Linux

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

[Jonathan Watt]

Mass bug change to replace various 'parity' whiteboard flags with the
new canonical keywords. (See bug 1443764 comment 13.)

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

Title:
  Gecko Engine does not support the XHTML 1.1 ruby tag

Status in Epiphany Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: epiphany-browser

  Visit a website such as http://icculus.org/~mongoose/index-jp2.html --
  notice Ruby tags are ignored.  This works in IE and can work with a
  plugin in firefox ( http://piro.sakura.ne.jp/xul/_rubysupport.html.en
  ).  Ruby is part of the XHTML 1.1 standard.

  
  http://www.w3.org/TR/ruby/

  ProblemType: Bug
  Architecture: amd64
  Date: Sun May 13 11:42:29 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/epiphany
  Package: epiphany-browser 2.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/epiphany
  ProcCwd: /home/mongoose
  ProcEnviron:
   LANGUAGE=en_US:en
   
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: epiphany-browser
  Uname: Linux namie 2.6.20-14-generic #2 SMP Thu Apr 12 22:25:02 UTC 2007 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/114441/+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 1920665] Re: Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1920665

** Tags added: iso-testing

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

Title:
  Ubiquity crash on try/install and from live session with "malloc():
  unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

[Phip]

I had the same log but the action was different.
Situations where I get the same messages:
- connect/disconnect my secondary keyboard
- when I press a key on the first keyboard and then I press the key on the 
second keyboard
- on same keyboard: pressing on a letter key and then using an FN key 
combination

After a while, causing a delay in the response when a key was pressed.

After some testing, I removed the "gnome-shell-extension-ubuntu-dock"
package and no longer had this problem.

To have the dock showing again, I installed the "Dash to Dock" extension
and had to disable (using Gnome Tweak Tool) the option "Use keyboard
shortcuts to activate apps" (in Behavior extension tab). With this
option enabled, messages continue to appear as normal.

Description of the extension option:
"Use keyboard shortcuts to activate apps.
Enable Super+(0-9) as shortcuts to active apps. It can also be used together 
with Shift and Ctrl".

I hope this helps in something.

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

Title:
  Window manager warning: Overwriting existing binding of keysym 37 with
  keysym 37 (keycode 10).

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

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1920130] Re: System icons missing in kubuntu 21.04

[Paul Chaffey]

I have sorted this out by using the following from another post:

sudo service sddm stop
sudo apt remove libqt5quick5-gles
sudo apt install libqt5quick5
sudo service sddm start

For me, when removing libqt5quick5-gles, libqt5quick5 was automatically
install, so line 3 wasn't needed. Not sure why it was installed in the
first place...

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

Title:
  System icons missing in kubuntu 21.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property "visible"
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: 
QML GridView: Binding loop detected for pro
  perty "rightPadding"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent 

[Desktop-packages] [Bug 1920665] Re: Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Rik Mills]

Some diagnosis as follows:

- Loaded a previous snapshot of a Kubuntu 21.04 VM from before 16th March 2021.
- Installed ubiquity.
- Tested whether ubiquity launches.
- Ubiquity launches.

- Then looked at what was upgradable in the release pocket.
- Sequentially upgraded likely culprits, rebooted, and tried to launch ubiquity 
after each small update.

Result:

Found that upgrading Mesa packages from 20.3.4-1 to 21.0.0-1 is all that
is required to trigger the crash.

Upgraded the following packages:
libegl-mesa0 (20.3.4-1) to 21.0.0-1
libgbm1 (20.3.4-1) to 21.0.0-1
libgl1-mesa-dri (20.3.4-1) to 21.0.0-1
libglapi-mesa (20.3.4-1) to 21.0.0-1
libglx-mesa0 (20.3.4-1) to 21.0.0-1
libxatracker2 (20.3.4-1) to 21.0.0-1
mesa-va-drivers (20.3.4-1) to 21.0.0-1
mesa-vdpau-drivers (20.3.4-1) to 21.0.0-1
mesa-vulkan-drivers (20.3.4-1) to 21.0.0-1

** Also affects: ubiquity (Ubuntu Hirsute)
   Importance: Critical
   Status: New

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

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

Title:
  Ubiquity crash on try/install and from live session with "malloc():
  unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1920670] [NEW] screen glitches

[Ando Ghuyan]

Public bug reported:

Time by time screen glitches for some seconds. This problem happens
independent of PC load (with both Intel and NVIDIA graphic cards).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-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  460.39  Thu Jan 21 21:54:06 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 21 16:41:39 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0906]
   Subsystem: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] 
[10de:]
InstallationDate: Installed on 2021-03-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. Precision 5540
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=d9d861fa-ee39-4c30-a652-d4c285927a01 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2020
dmi.bios.release: 1.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.1
dmi.board.name: 0WWHJ2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd12/14/2020:br1.9:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5540
dmi.product.sku: 0906
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
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 corruption focal ubuntu

** Attachment added: "Screenshot from 2021-03-21 16-47-10.png"
   
https://bugs.launchpad.net/bugs/1920670/+attachment/5478668/+files/Screenshot%20from%202021-03-21%2016-47-10.png

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

Title:
  screen glitches

Status in xorg package in Ubuntu:
  New

Bug description:
  Time by time screen glitches for some seconds. This problem happens
  independent of PC load (with both Intel and NVIDIA graphic cards).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-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  460.39  Thu Jan 21 21:54:06 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Butterfly]

@hstoellinger1, this not related PPA repository. Open Software and
Updates (software sources) and disable DVD/CD repository.

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1879206] Re: cups hplip not install printer

[Alain Baeckeroot]

The bug is present for 3 different HP printers , 
via Wifi or via USB

It worked nicely , and began to fail maybe one month ago (near february
/ march 2021)

I guess some upgrade messed-up the printers.

** Changed in: hplip (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

Re: [Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Heinrich Stoellinger]

Hello,
I added the PPA and then tried to install the driver package. But - 
during fetching packages,
apt asks me to insert the following DVD/CD:
»Kubuntu 21.04 _Hirsute Hippo_ - Alpha amd64 (20210224)«
how/where can I get that DVD/CD?
Thanks for your help
H. Stoellinger

Am 21.03.21 um 00:20 schrieb Butterfly:
> @hstoellinger1, Nvidia-340 driver added to PPA for hirsute (21.04) base.
> You can install nvdia-340 driver from PPA. The driver in PPA repository
> currently supports up to 5.12 of Linux kernel.
> https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy
>
>
> ---
>
>
> Nvidia-340 driver's official support for hirsute base is no longer available.
>
> nvidia-graphics-drivers-340 (340.108-0ubuntu8) hirsute; urgency=medium
>
>* Drop support for the 340 driver, in favour of the nouveau driver
>  since it is no longer supported by NVIDIA:
>  
> https://nvidia.custhelp.com/app/answers/detail/a_id/3142/~/support-timeframes-for-unix-legacy-gpu-releases
>
>   -- Alberto Milone <...>  Wed, 10 Mar 2021 17:18:43 +0100
>

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1920661] [NEW] package texlive-plain-generic (not installed) failed to install/upgrade: 正试图覆盖 /usr/share/doc/texlive-doc/fonts/fontname/8a.html，它同时被包含于软件包 texlive-generic-recom

[HuGuanqing]

Public bug reported:

no more details

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: texlive-plain-generic (not installed)
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Mar 21 17:37:13 2021
ErrorMessage: 正试图覆盖 
/usr/share/doc/texlive-doc/fonts/fontname/8a.html，它同时被包含于软件包 
texlive-generic-recommended 2013.20140215-1
InstallationDate: Installed on 2021-03-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: texlive-extra
Title: package texlive-plain-generic (not installed) failed to install/upgrade: 
正试图覆盖 /usr/share/doc/texlive-doc/fonts/fontname/8a.html，它同时被包含于软件包 
texlive-generic-recommended 2013.20140215-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package texlive-plain-generic (not installed) failed to
  install/upgrade: 正试图覆盖 /usr/share/doc/texlive-
  doc/fonts/fontname/8a.html，它同时被包含于软件包 texlive-generic-recommended
  2013.20140215-1

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  no more details

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: texlive-plain-generic (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Mar 21 17:37:13 2021
  ErrorMessage: 正试图覆盖 
/usr/share/doc/texlive-doc/fonts/fontname/8a.html，它同时被包含于软件包 
texlive-generic-recommended 2013.20140215-1
  InstallationDate: Installed on 2021-03-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: texlive-extra
  Title: package texlive-plain-generic (not installed) failed to 
install/upgrade: 正试图覆盖 
/usr/share/doc/texlive-doc/fonts/fontname/8a.html，它同时被包含于软件包 
texlive-generic-recommended 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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