date:20210801

The feature will not appear in the GUI if you're running a kernel
version that doesn't support it (or on ~50% of laptops that also don't
support it). You can force the setting off unconditionally with:

gsettings set org.gnome.settings-daemon.plugins.power ambient-enabled
false

But the setting is different for each user, so the above command will
only stop it happening on the desktop but won't stop it happening on the
login screen (user 'gdm').

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

Title:
Screen brightness changing randomly

Status in gnome-settings-daemon package in Ubuntu:
Won't Fix

Bug description:
Hello guys!

The brightness of the screen on my laptop (Dell 7573 with touch ips
1080 panel) slightly changes randomly when using the laptop builtin
display. It feels the same as I changed the brightness one step using
the keyboard keys.

Here is a video:

https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I suffer with this problem since a long time ago. I think since ubuntu
19. I tried everything you can imagine, I will make a list of things
I've tried. I had gave up trying to fix this already but in a
beautiful sunny day suddenly the bug stopped happening. So I decided
to report this bug now because this bug does NOT happen with only this
version of the kernel: Linux 5.11.0-16-generic. So that can probably e
useful to help discovering the bug reason.

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

List of things I've tried:
- Changing i915 parameters like enable_psr to false and many others.
- Upgrading BIOS version.
- Installing windows and applying all the patches on dell's website and
installing ubuntu again.
- Disabling "dynamic backlight control" on BIOS.

Some maybe useful info:
- I've tried other distros like Fedora and PopOS and the same bug happens.
- The bug does not happen when using live ubuntu from usb.
- When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the
bug doesn't happen when you have just installed the os but it starts again
after the first update. The same applies to the other distro's mentioned above.
- When you disable i915 driver with modeset parameter, it does not happen.
- The bug does NOT happen only with this kernel version 5.11.0-16-generic,
BUT it starts happening again if I lock screen and login again. So I am never
locking my screen and holding this kernel version for now.

Thanks guys!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 29 20:54:14 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA
controller])
Subsystem: Dell UHD Graphics 620 [1028:07ec]
InstallationDate: Installed on 2021-07-25 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Inspiron 7573
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2021
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.1
dmi.board.name: 023FRC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7573
dmi.product.sku: 07EC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-

[Desktop-packages] [Bug 1930591] Re: Not able to attach secondary display through HDMI

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Not able to attach secondary display through HDMI

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Not able to attach secondary display through HDMI

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  2 19:09:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  InstallationDate: Installed on 2021-05-01 (32 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=4b855eaf-8204-49cb-8e54-11983d2916a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2013
  dmi.bios.release: 15.69
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3244HK1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 100.42
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr098E130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.sku: E4X59PA#ACJ
  dmi.product.version: 098E130059160
  dmi.sys.vendor: Hewlett-Packard
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1930591/+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 1930594] Re: Nautilus needs very long to open (1+ minute)

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

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

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

Title:
  Nautilus needs very long to open (1+ minute)

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  1.) lsb_release -rd:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  2.) apt-cache policy nautilus:
  nautilus:
Installiert:   1:3.36.3-0ubuntu1
Installationskandidat: 1:3.36.3-0ubuntu1
Versionstabelle:
   *** 1:3.36.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3.) What you expected to happen:
  I expected that when I press "Files" or type in "nautilus" in the terminal, 
that Nautilus shows up within a few seconds.

  4.) What happend instead:
  It took about 1 minute until nautilus showed up. If i close it, it takes 
another minute to show up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  2 16:07:05 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1072, 550)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2021-05-10 (23 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1930594/+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 1938477] Re: Screen brightness changing randomly

2021-08-01 Thread Felipe Butcher

Hey thanks. If it's feature why it doesn't happen on this particular
kernel version?

Also my power settings does not show this option. I already tried
changing it with dconf-editor.

I still think it's a bug.

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

Title:
Screen brightness changing randomly

Status in gnome-settings-daemon package in Ubuntu:
Won't Fix

Bug description:
Hello guys!

Here is a video:

https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

Thanks guys!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1938477/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.laun

[Desktop-packages] [Bug 1938613] Re: Gnome desktop does not properly support icons.

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

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 1813441, 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.


** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons (Ubuntu)

** This bug has been marked a duplicate of bug 1813441
   Can no longer drag and drop files between desktop and applications

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

Title:
  Gnome desktop does not properly support icons.

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

Bug description:
  I cannot drag and drop icons directly onto the Gnome desktop.  Even
  when I use the Files windows, all I can do is get them to appear, but
  then I cannot arrange them as I wish.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 31 09:02:45 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-09 (447 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  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-extension-desktop-icons/+bug/1938613/+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 1938477] Re: Screen brightness changing randomly

** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)

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

Title:
Screen brightness changing randomly

Status in gnome-settings-daemon package in Ubuntu:
Won't Fix

Bug description:
Hello guys!

Here is a video:

https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

Thanks guys!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1938477/+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 1938477] Re: Screen brightness changing randomly

I know this issue is annoying but it's also a feature and not a bug. To
turn it off (after you have logged in) go to:

Settings > Power > Power Saving > Automatic Brightness = OFF

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

** Changed in: ubuntu
Status: New => Won't Fix

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

Title:
Screen brightness changing randomly

Status in gnome-settings-daemon package in Ubuntu:
Won't Fix

Bug description:
Hello guys!

Here is a video:

https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

Thanks guys!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1938477/+subscriptions

--
Mailing list: https://launchpad.net/~de

[Desktop-packages] [Bug 1938477] [NEW] Screen brightness changing randomly

You have been subscribed to a public bug:

Hello guys!

The brightness of the screen on my laptop (Dell 7573 with touch ips 1080
panel) slightly changes randomly when using the laptop builtin display.
It feels the same as I changed the brightness one step using the
keyboard keys.

Here is a video:
https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I suffer with this problem since a long time ago. I think since ubuntu
19. I tried everything you can imagine, I will make a list of things
I've tried. I had gave up trying to fix this already but in a beautiful
sunny day suddenly the bug stopped happening. So I decided to report
this bug now because this bug does NOT happen with only this version of
the kernel: Linux 5.11.0-16-generic. So that can probably e useful to
help discovering the bug reason.

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

List of things I've tried:
- Changing i915 parameters like enable_psr to false and many others.
- Upgrading BIOS version.
- Installing windows and applying all the patches on dell's website and 
installing ubuntu again.
- Disabling "dynamic backlight control" on BIOS.

Some maybe useful info:
- I've tried other distros like Fedora and PopOS and the same bug happens.
- The bug does not happen when using live ubuntu from usb.
- When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the 
bug doesn't happen when you have just installed the os but it starts again 
after the first update. The same applies to the other distro's mentioned above.
- When you disable i915 driver with modeset parameter, it does not happen.
- The bug does NOT happen only with this kernel version 5.11.0-16-generic, BUT 
it starts happening again if I lock screen and login again. So I am never 
locking my screen and holding this kernel version for now.

Thanks guys!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 29 20:54:14 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
 virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:07ec]
InstallationDate: Installed on 2021-07-25 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Inspiron 7573
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2021
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.1
dmi.board.name: 023FRC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7573
dmi.product.sku: 07EC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug hirsute ubuntu
-- 
Screen brightness changing randomly
https://bugs.launchpad.net/bugs/1938477
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1938435] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch inpu

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

** This bug has been marked a duplicate of bug 1938352
   [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes 
unresponsive to touch / mouse while windows & desktop are still responsive to 
touch input

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

Title:
  [wayland] gnome-shell elements (dock, top bar, on-screen keyboard)
  becomes unresponsive to touch / mouse while windows & desktop are
  still responsive to touch input  (2nd entry, with 3rd party extensions
  disabled)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  filed for new attachments - see https://bugs.launchpad.net/gnome-
  shell/+bug/1938352 & https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/4508

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 29 06:12:21 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-15 (13 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435/+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 1937126] Re: Multiple docks visible

This bug is now closed. If you have any other problems then please open
new bugs for them.

---

Este bug está fechado. Se você tiver quaisquer outros problemas, abra
novos bugs para eles.

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

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

Title:
  Multiple docks visible

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+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 1937126] Re: Multiple docks visible

You have two docks installed, which is the cause of the problem:

  'dash-to-d...@micxgx.gmail.com'
  'ubuntu-d...@ubuntu.com'

Please use the 'Extensions' app to disable one of them.

---

Você tem dois docks instalados, o que é a causa do problema:

   'dash-to-d...@micxgx.gmail.com'
   'ubuntu-d...@ubuntu.com'

Use o aplicativo 'Extensões' para desativar um deles.

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

Title:
  Multiple docks visible

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+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 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

I've tried to give this bug a more unique title to distinguish it from
the other SIGABRTs:

  https://bugs.launchpad.net/ubuntu/+source/xorg-
server?field.searchtext=SIGABRT

Also note the stack trace in the Bug Description is not unique. It
should probably be deleted. Only stack traces with debug symbols are
useful with Xorg.

** Summary changed:

- Xorg xserver got signal 6 to abort
+ Xorg crashed with SIGABRT when under memory pressure

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1916851] Re: module-echo-cancel fails on first run

** Tags removed: groovy
** Tags added: focal

** Changed in: pulseaudio (Ubuntu)
   Status: Won't Fix => Confirmed

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

Title:
  module-echo-cancel fails on first run

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have the following in `.config/pulse/default.pa`:

  ```
  .include /etc/pulse/default.pa
  load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
  ```

  After a reboot, there is no echo cancelled device.

  And then I run `systemctl --user restart pulseaudio` and the echo
  cancelled devices appear.

  That's a bit of a hassle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shahar39906 F pulseaudio
   /dev/snd/controlC1:  shahar39906 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:05:48 2021
  InstallationDate: Installed on 2010-10-12 (3788 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1916851/+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 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously

** Changed in: gnome-control-center
   Status: New => Unknown

** Changed in: gnome-control-center
 Remote watch: gitlab.gnome.org/GNOME/gnome-control-center/issues #681 => 
gitlab.gnome.org/GNOME/gnome-control-center/issues #53

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-41 fixed-upstream

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

Title:
  Bluetooth and Wi-Fi items in Power are worded ambiguously

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  In the gnome-control-center, in the power section, there is a checkbox
  that says:

  Wi-Fi
  Turn off Wi-Fi to save power

  I have it checked, so after a few minutes without using my computer,
  the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked
  this box, but it disables my wi-fi immediately.

  So, it's obviously wrong to disable the wi-fi when I click that
  checkbox. And I don't seem to have a way to keep my wi-fi enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 18:27:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-04 (145 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eo
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.

2021-08-01 Thread Balazs Pere

** Attachment added: "Képernyőkép erről: 2021-08-02 02-02-48.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+attachment/5515158/+files/K%C3%A9perny%C5%91k%C3%A9p%20err%C5%91l%3A%202021-08-02%2002-02-48.png

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

Title:
  Week view goes blank when changing weeks or when user screen focus
  changes.

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  gnome-calendar:
Installed: 3.36.2-0ubuntu1
Candidate: 3.36.2-0ubuntu1
Version table:
   *** 3.36.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Week view goes blank when changing weeks or when user screen focus changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] [NEW] Week view goes blank when changing weeks or when user screen focus changes.

2021-08-01 Thread Balazs Pere

Public bug reported:

Description:Ubuntu 20.04.2 LTS
Release:20.04

gnome-calendar:
  Installed: 3.36.2-0ubuntu1
  Candidate: 3.36.2-0ubuntu1
  Version table:
 *** 3.36.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.36.1-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


Week view goes blank when changing weeks or when user screen focus changes.

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

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

Title:
  Week view goes blank when changing weeks or when user screen focus
  changes.

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  gnome-calendar:
Installed: 3.36.2-0ubuntu1
Candidate: 3.36.2-0ubuntu1
Version table:
   *** 3.36.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Week view goes blank when changing weeks or when user screen focus changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1928080] Re: Noto Sans Hebrew is not set as the fallback font of Noto Sans

2021-08-01 Thread Omer I.S.

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

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

Title:
  Noto Sans Hebrew is not set as the fallback font of Noto Sans

Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  [This is a minor issue]

  Hello, Noto Sans Hebrew is not set as the fallback font of Noto Sans in 
Kubuntu, and the current fallback font of Noto Sans is Liberation Sans, and not 
Noto Sans Hebrew.
  May you fix it, please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1928080/+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 1933365] Re: [Minor] The localization pack is not installed by default

2021-08-01 Thread Omer I.S.

** Summary changed:

- [MINOR] The localization pack is not installed by default
+ [Minor] The localization pack is not installed by default

** Summary changed:

- [Minor] The localization pack is not installed by default
+ [Minor] The l10n pack is not installed by default

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

Title:
  [Minor] The l10n pack is not installed by default

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello, the Ubuntu installer does not install localization packs for
  Firefox. Instead, Firefox uses English by default and the packages
  have to be downloaded manually.

  This may affect other users too, and this may be bad for their user
  experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1933365/+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 1938596] Re: Always on top windows obscure context menus and tooltips

2021-08-01 Thread abcdef

** Attachment added: "Illustrating how a Files window's context menu is hidden 
by another, always on top Files window"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+attachment/5515157/+files/aot%20on%20context%20menu.png

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

Title:
  Always on top windows obscure context menus and tooltips

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  "Always on top" windows are meant to be on top of other non-transient
  windows (its peers), but they're also on top of other windows'
  transient GUI components like context menus and tooltips.

  It is not constructive to obscure menus and tooltips with always on
  top windows any more than it is helpful to obscure the actual mouse
  cursor with AOT windows. They are short lived. Users can't decide
  where to place them. They will disappear by themselves when the user
  is done with them. A hidden tooltip or context menu helps no one.

  ubuntu 21.04 gnome wayland
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-30 (274 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-25-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-04-23 (99 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd

This bug was fixed in the package jackd2 - 1.9.19~dfsg~ubuntu-0ubuntu2

---
jackd2 (1.9.19~dfsg~ubuntu-0ubuntu2) impish; urgency=medium

  * Remove LTO in build (LP: #1937325)
  * Add new internal zalsa client

 -- Erich Eickmeyer   Sun, 01 Aug 2021 15:16:22
+

** Changed in: jackd2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Jack clients have segmentation fault when trying to connect to jackd

Status in jackd2 package in Ubuntu:
  Fix Released

Bug description:
  Steps to show this bug. Start jackd either as jackd or jackdbus (with
  jack_control). run jack_lsp from the command line to show jackd's
  port. Jack_lsp will segfault. Other jack clients will have similar
  problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not
  have this problem.

  jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
  Uname: Linux 5.11.0-20-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jul 22 18:09:18 2021
  InstallationDate: Installed on 2021-06-15 (37 days ago)
  InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613)
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 11544] Re: Single click doesn't work in file chooser dialog box

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #228
   https://gitlab.gnome.org/GNOME/gtk/issues/228

** Changed in: gtk
   Importance: Wishlist => Unknown

** Changed in: gtk
   Status: Expired => Unknown

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #121113 => gitlab.gnome.org/GNOME/gtk/issues 
#228

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

Title:
  Single click doesn't work in file chooser dialog box

Status in GTK+:
  Unknown
Status in One Hundred Papercuts:
  In Progress
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  when you select single click in file management it works for nautilus and the
  desktop but not for applications that use the "file chooser dialog box" to 
open
  files, i.e. you have to double click to open directories even with single 
click
  selected as the gnome default.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/11544/+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 1901829] Re: thunderbird fails to open, xml parse error

2021-08-01 Thread Jerry Quinn

I see this issue in 20.04 but it  interfere with starting thunderbird.
I'm using en-US.

jlquinn@cerberus:~/Videos/summits$ lsb_release -a; uname -a; apt-cache policy 
thunderbird
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal
Linux cerberus 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux
thunderbird:
  Installed: 1:78.11.0+build1-0ubuntu0.20.04.2
  Candidate: 1:78.11.0+build1-0ubuntu0.20.04.2
  Version table:
 *** 1:78.11.0+build1-0ubuntu0.20.04.2 500
500 http://us.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
 1:68.7.0+build1-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  thunderbird fails to open, xml parse error

Status in thunderbird package in Ubuntu:
  Confirmed
Status in thunderbird source package in Groovy:
  Won't Fix

Bug description:
  launching thunderbird opens a small browser window displaying the
  following error:

  XML Parsing Error: undefined entity
  Location: chrome://messenger/content/messenger.xhtml
  Line Number 905, Column 3:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1551599] Re: Remove button missing after package installation

Further to comment #9 this issue seems fixed. I tested with gnome-
software version 3.38.1-1 in the current development version (impish)
and the 'Remove' button was displayed immediately after installation
completed.

xenial, yakkety and zesty are no longer supported so closing bug report.

** Changed in: hundredpapercuts
 Assignee: Lawrence Young (lorenzojoven) => (unassigned)

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: Confirmed => Invalid

** Changed in: gnome-software (Ubuntu Zesty)
   Status: Confirmed => Invalid

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

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

Title:
  Remove button missing after package installation

Status in One Hundred Papercuts:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Invalid
Status in gnome-software source package in Yakkety:
  Invalid
Status in gnome-software source package in Zesty:
  Invalid

Bug description:
  [What Happens]
  ==
  Installing
  --
  1. Open the Software app (GNOME Software). Search for clocks.
  2. Click Install next to Clocks.
  3. The Install button becomes insensitive and changes to Installing...
  4. The Install button becomes sensitive again and changes back to Install (it 
should have changed to Remove)
  5. If you click the Clocks row (still in the All page), the Clocks info page 
opens with an Install button (it should have a Launch button and a Remove 
button).
  6. If you switch to the Installed page, Clocks correctly shows up with a 
Remove button.
  7. If you click the Clocks row in the Installed page, the Clocks info page 
correctly opens with a Launch button and a Remove button.
  8. Close the Software app then reopen it. Same results as #4-7 above.
  9. $ pkill gnome-software
  10. Open the Software app. Now Clocks shows up correctly in the All page with 
a Remove button and the Clocks info page correctly includes the Launch and 
Remove buttons but not the Install button.

  Removing
  
  11. Click the Remove button to uninstall Clocks.
  12. The Remove button becomes insensitive again and changes to Removing...
  12. We basically get the same broken results as before. In the All page, the 
Clocks row shows Remove still. Clicking the Clocks row shows the Info page with 
Launch and Remove.
  One change is that in the Installed page, Clocks shows up twice, once with an 
Install button, once with a Remove button.
  Completely stopping the gnome-software process (via logging out or the pkill 
trick mentioned in #9) is necessary for the Software app to correctly register 
Clocks as being removed.

  I was unable to reproduce this bug with Fedora 24.

  Other Info
  ==
  See also bug 1582959 which is similar but a bit different.

  In bug 1679417, a user reported that the package disappears from the
  Installed list if Remove is selected but password authentication is
  cancelled or failed.

  [Original bug report]
  =
  Used gnome-software to install a package.

  Once it was installed I expected to see an option to remove it.

  As can be seen all I see is the option to Install the package.

  If you click Install you are then given the option to remove the
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar  1 08:05:06 2016
  InstallationDate: Installed on 2015-10-29 (123 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1551599/+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 1377029] Re: Default filenames contain colons, making it hard to share screenshots

Further to comment #4, belatedly closing the Papercuts task.

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

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

Title:
  Default filenames contain colons, making it hard to share screenshots

Status in One Hundred Papercuts:
  Fix Released
Status in gnome-screenshot package in Ubuntu:
  Fix Released

Bug description:
  Colons aren't allowed on "Microsoft-based" filesystems (NTFS, VFAT),
  and quite a few websites also don't allow colons in filenames of
  uploaded files (because downloading a file with such a name on a
  Windows system is, apparently, problematic).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-screenshot 3.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  3 08:54:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-13 (323 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to utopic on 2014-09-16 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1377029/+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 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)

Reporter no longer uses Launchpad.
Issue confirmed by only one other user over 5 years ago.
Does anyone else see this issue in a supported release of Ubuntu?


** Changed in: hundredpapercuts
   Status: Confirmed => Incomplete

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: network-manager
   Status: New => Incomplete

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

Title:
  My phone's bluetooth  is displayed dozens of times under the network
  list (wifi icon)

Status in One Hundred Papercuts:
  Incomplete
Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I can hardly even start describing how screwed up this is.
  Have a look at the screenshot.

  I had seen this before and hadn't even realized that "XT1039 Network"
  repeated like 37 times had something to do with my own Android phone,
  a motorola Moto G. Needless to say I have only one.

  Out of curiosity I clicked on one of "them" (thinking this was some
  neighboor's device, obviously suspecting it was just one device
  repeated several times because of a bug), and then my phone vibrated
  prompting me whether to accept the connection from the computer.

  Which I did. As a result, the bluetooth indicator next to the network
  indicator showed a lock icon for a fraction of a second, which
  immediately disappeared. I guess that means that the computer and the
  phone peered via bluetooth for a few instants. At the same time, the
  wifi icon started animating (as if the computer was connecting to a
  wifi network... or a network of any kind I guess, since the same
  stupidly designed wifi-like animation is used when connecting to LAN
  via an ethernet cable). After that, the small lock below the bluetooth
  icon disappeared, the wifi icon stopped animating and went back to its
  normal "connected" status (I was previously and still connected to my
  home router's wifi network), and a baloon saying "Disconnected [NL]
  Network" appeared and disappeared.

  Then I repeated the test several times with the same result, except
  that the phone didn't prompt me any more to accept the connection.

  
  This is totally screwed up in several ways.

  First, there's no reason "XT1039 Network" should be listed AT ALL
  together with wifi and ethernet networks. What kind of "network" is it
  supposed to be?? Of course I have not turned on bluetooth tethering on
  the phone, and bluetooth connection to the phone is already available
  under the bluetooth indicator.

  If it makes any sense at all to show the mobile device as a "network" 
alongside with wifi and cable networks because, well, bluetooth is a network as 
well, then
  1) the list of bluetooth "networks" should have a header, just like "wifi 
networks" and "ethernet network". Right now, there is just a list of networks 
that you don't know what kind they are
  2) the device should be only listed once, not 37  times
  3) I also suspect the 3 items called just "network" are related
  4) If it is there at all, it must work. What is it supposed to do? The same 
as unfolding the menu under the Bluetooth indicator, hovering on the device 
there (which is listed only once there) and turning on the "Connection" switch? 
That one does work. This one (in the list of networks) doesn't. And if it is 
supposed to do something different, it's clearly failing as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 03:29:50 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (871 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1551515/+subscriptions

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

Closing as seems this issue was fixed in Ubuntu 16.04.

** Changed in: hundredpapercuts
   Status: Incomplete => Fix Released

** Changed in: xserver-xorg-video-intel
   Status: New => Fix Released

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Fix Released
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xser

[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

This issue has sat incomplete for more than 60 days now without any
response so I'm closing it now as "Invalid".

Please feel free to re-open this bug report if this is still an issue
when using any currently supported release of Ubuntu.

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

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: lightdm (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: lxsession (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: lxsession (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: lightdm/1.18
   Status: Incomplete => Invalid

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

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Invalid
Status in Light Display Manager:
  Invalid
Status in Light Display Manager 1.18 series:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in lxsession package in Ubuntu:
  Invalid
Status in lightdm source package in Xenial:
  Invalid
Status in lxsession source package in Xenial:
  Invalid

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd

2021-08-01 Thread Erich Eickmeyer 

** Changed in: jackd2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Jack clients have segmentation fault when trying to connect to jackd

Status in jackd2 package in Ubuntu:
  Fix Committed

Bug description:
  Steps to show this bug. Start jackd either as jackd or jackdbus (with
  jack_control). run jack_lsp from the command line to show jackd's
  port. Jack_lsp will segfault. Other jack clients will have similar
  problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not
  have this problem.

  jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
  Uname: Linux 5.11.0-20-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jul 22 18:09:18 2021
  InstallationDate: Installed on 2021-06-15 (37 days ago)
  InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613)
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd

2021-08-01 Thread Erich Eickmeyer 

Unfortunately, all of this comes down to the forced LTO. Disabling this
in d/rules, per upstream, fixes the problem. He had a few more notes as
well. It seems as though the Debian package is doing some unnecessary
gymnastics, so this is a decent divergence.

diff --git a/debian/rules b/debian/rules
index a36f71d..6f12983 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,8 +1,8 @@
 #!/usr/bin/make -f
 
 # Let's try to cut down noisy symbols to the official API
-export DEB_CFLAGS_MAINT_APPEND = -fvisibility=hidden
-export DEB_CXXFLAGS_MAINT_APPEND = -fvisibility=hidden
+export DEB_CFLAGS_MAINT_APPEND = -fvisibility=hidden -fno-lto
+export DEB_CXXFLAGS_MAINT_APPEND = -fvisibility=hidden -fno-lto
 
 -include /usr/share/cdbs/1/rules/upstream-tarball.mk
 -include /usr/share/cdbs/1/rules/utils.mk


** Changed in: jackd2 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Jack clients have segmentation fault when trying to connect to jackd

Status in jackd2 package in Ubuntu:
  In Progress

Bug description:
  Steps to show this bug. Start jackd either as jackd or jackdbus (with
  jack_control). run jack_lsp from the command line to show jackd's
  port. Jack_lsp will segfault. Other jack clients will have similar
  problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not
  have this problem.

  jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
  Uname: Linux 5.11.0-20-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jul 22 18:09:18 2021
  InstallationDate: Installed on 2021-06-15 (37 days ago)
  InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613)
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1082922] Re: "Open with" bar breaks the extra pane with

Further to comment #4 I'm closing the remaining tasks as Ubuntu 12.04
hasn't been supported since April 2017.

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

** Changed in: hundredpapercuts
   Status: New => Invalid

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

Title:
  "Open with" bar breaks the extra pane with

Status in One Hundred Papercuts:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in nautilus source package in Precise:
  Invalid

Bug description:
  Description:
  When you insert a media that can be handled using a specific app, Nautilus 
shows a bar with an "Open with" button, on were it suggest a proper app.
  If you have the extra pane active (F3), this bar forces the pane to expand, 
narrowing the other one.

  Test case:
  Insert a media containing, for example, music (if asked for an app, just 
close the window).
  Open Nautilus
  Create another pane using F3.
  Select the inserted media.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic-pae 3.2.33
  Uname: Linux 3.2.0-34-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  CheckboxSubmission: 1c569236429244c2837ef2720aaa3765
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Sun Nov 25 14:11:58 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '767x838+831+33'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 204
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1082922/+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 1799856] Re: Software Boutique crashes after applying fixes

Can you reproduce this bug with newer version of Ubuntu MATE?

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

Title:
  Software Boutique crashes after applying fixes

Status in Ubuntu MATE:
  Incomplete
Status in gnome-software package in Ubuntu:
  Invalid
Status in ubuntu-mate-welcome package in Ubuntu:
  Incomplete

Bug description:
  After Software Boutique installed the software I selected I clicked
  "fixes". After checking for incomplete and broken packages, I clicked
  "More Software".

  What I got was a list of "Software" and "Synaptic Package Manager"
  repeated 3 times. (Before installing apps, the list occurred only
  once.)

  Ubuntu 18.04.1 LTS (just reinstalled when 18.10 went into meltdown).
  AMD 64-bit

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3.6-minimal 3.6.6-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 24 21:56:10 2018
  ExecutablePath: /usr/bin/python3.6
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: python3.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1799856/+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 1395301] Re: Inconsistent terminology for Bluetooth pairing

Can you reproduce this bug with newer version of Ubuntu MATE?

** Tags removed: trusty

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

Title:
  Inconsistent terminology for Bluetooth pairing

Status in gnome-user-share package in Ubuntu:
  Fix Released
Status in mate-user-share package in Ubuntu:
  Incomplete

Bug description:
  The "Personal File Sharing Preferences" window has two sections
  relating to Bluetooth, and those use different terminology (and user
  interface features) to describe Bluetooth pairing, both from one
  another and from the main Bluetooth settings.

  Under "Share Files over Bluetooth", the requirement for pairing is
  controlled by a tickbox labelled "Require remote devices to bond with
  this computer", while under "Receive Files over Bluetooth", it's
  controlled by a pop-up menu labelled "Accept files:" with options
  "Always" and "Only for set up devices".  As far as I can tell from the
  docuementation (which disagrees slightly about how the user interface
  should look), these controls have equivalent effects and control
  whether files can be respectively browsed or sent by unpaired devices.
  Meanwhile, the Bluetooth indicator menu uses the phrase "Set-up [sic]
  New Device", the Bluetooth pane of System Settings describes certain
  devices as "Paired", and the Ubuntu Desktop Guide explains how to
  "Connect your computer to a Bluetooth device" but helpfully explains
  that "This is also called pairing the Bluetooth devices".

  Personally, I think that both of these settings should be tickboxes,
  and their labels should both be phrased in terms of "paired" deviced,
  since that's standard Bluetooth terminology.  For consistency with the
  Ubuntu Desktop Guide, perhaps "connected" would be better (but I think
  it's less obvious what it means).

  PS: I've just found the "Control sharing over Bluetooth" page of the
  Ubuntu Desktop Guide, which adds to the fun by introducing "trusted
  devices", which are apparently yet another way of talking about paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-share 3.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Nov 22 10:53:26 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-file-share-properties
  InstallationDate: Installed on 2010-06-09 (1626 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: gnome-user-share
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1395301/+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 956834] Re: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder

Can you reproduce this bug with newer version of Ubuntu MATE?

** Tags removed: precise

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

Title:
  gnome-file-share-properties states to receive files over bluetooth in
  Downloads folder, while it actually receives in Public folder

Status in gnome-user-share package in Ubuntu:
  Fix Released
Status in mate-user-share package in Ubuntu:
  Incomplete

Bug description:
  In gnome-file-share-properties, the option to enable receiving files
  over bluetooth is labeled “Receive files in Downloads folder over
  Bluetooth”. In fact, however, it receives files in Public folder.

  I am not exactly sure which is the desired behavior (Downloads folder
  would actually make sense to me, but one could also argue in favor of
  Public folder, which can be shared over Bluetooth). But either way,
  the label and the behavior should match.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-user-share 3.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Fri Mar 16 11:24:16 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
  SourcePackage: gnome-user-share
  UpgradeStatus: Upgraded to precise on 2012-01-22 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/956834/+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 1406538] Re: Screenshot contains selected area highlight

Can you reproduce this bug with newer version of Ubuntu MATE?

** Tags added: mint-mate

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

Title:
  Screenshot contains selected area highlight

Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in mate-utils package in Ubuntu:
  Fix Committed

Bug description:
  mate-utils_1.8.1-0+rebecca_amd64
  If i choose "select area to grab" i almost constantly get an annoying green 
overlay which is what i just used to highlight the area that i wanted to grab.
  See attached example.
  I'm using Mint MATE x64 17.1, software compositing window manager enabled, 
compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 
7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. 
  I remember this happening since mint 13 or so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1406538/+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 1803586] Re: SeaHorse hangs Panel when trying to decrypt file

** Tags added: bionic

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

Title:
  SeaHorse hangs Panel when trying to decrypt file

Status in mate-panel package in Ubuntu:
  New
Status in seahorse package in Ubuntu:
  New

Bug description:
  Hello ,

  Let's say that we have a file that we need to encrypt , so you go
  ahead and click Encrypt and then SeaHorse will ask you to choose which
  PGP to use , if you don't have one then you will be prompted to make
  one , let's say that we have made the PGP key and we encrypted the key
  but we didn't save the passphrase in the password manager so you will
  be prompted to put the password so you can decrypt the file and see
  the content

  But when you get prompted to put the passphrase to decrypt, then you
  decide not to put the passphrase but to cancel the process, you will
  be prompted second time to put the password automatically , I cancel
  it again and then the PC works just fine , but the whole menu is stuck
  , I can't click on Applications/Places/System , but I am able to click
  on the icons in the panel

  But it's frozen , I need to logout and login again to be able to use
  the panel again

  UPDATE : Even if not cancelling , putting the passphrase and unlocking
  the encryption will result in having the unencrypted file but still
  the panel freezes, And a logout/restart is needed to get it back
  working.

  If I'm missing any information please tell me I would update

  Thanks.

  Ubuntu Mate 18.04.1 LTS
  4.15.0-39-generic
  Traditional Panel
  Marco as Window Manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1803586/+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 1578487] Re: Unable to mount disk drives in computer://

Can you reproduce this bug with newer version of Ubuntu MATE?

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

Title:
  Unable to mount disk drives in computer://

Status in caja package in Ubuntu:
  Incomplete
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Mate 16.04

  Places/Computer
  -Disk images (SSD and File Systems) state "unknown"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1578487/+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 1901263] Re: I cant open any Chromium based browser

** Tags added: maybe-hirsute

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

Title:
  I cant open any Chromium based browser

Status in Ubuntu MATE:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've just installed Unbuntu Mate 20.10 from a bootable USB stick. The
  process was very simple (congratulations!) but the only browser I can
  open is the built-in Firefox. All other Chromium based browsers I've
  installed ( Chromium, Opera and Vivaldi) freeze the computer and I
  have do shut it down manually. My PC is a AMD-64 Dell Inspiron with 4
  GB RAM.

  Thanks for any help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1901263/+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 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

** Tags removed: disco disconnect down drop network wifi

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: 
disconnected -> scanning
  Dec 0

[Desktop-packages] [Bug 269441] Re: Trash always full

Can you reproduce this bug with newer version of Ubuntu MATE?

** Tags removed: groovy

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

Title:
  Trash always full

Status in Ubuntu MATE:
  Confirmed
Status in caja package in Ubuntu:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+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 1069964] Re: Two processes attempt to mount blank optical discs

** Tags removed: ubuntu-mate

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  Won't Fix
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1938630] Re: Sorting by Évaluation

2021-08-01 Thread DoMi.....

After restarting system, it works again. Close it

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

Title:
  Sorting by Évaluation

Status in gnome-software package in Ubuntu:
  New

Bug description:
   Hello, 
  When I'm in the explorer of gnome-software and I have select "Sorting by 
Name", it's neither possible to select "Sorting by Évaluation" (french version).
   Tks for you work.
   Dominique

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-software 3.38.1-1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug  1 09:28:23 2021
  InstallationDate: Installed on 2021-07-31 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.38.1-1
   gnome-software-plugin-snapN/A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1938630/+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 1938631] Re: the wifi network is sometimes interrupted

2021-08-01 Thread Shayxnazar Madaminov

** Project changed: snappy-hwe-snaps => network-manager (Ubuntu)

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

Title:
  the wifi network is sometimes interrupted

Status in network-manager package in Ubuntu:
  New

Bug description:
  the wifi network is sometimes interrupted and cannot be connected
  until it is restarted. And after disconnect the list of wifi networks
  stays are empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1938631/+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 1938631] [NEW] the wifi network is sometimes interrupted