[Desktop-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-04 Thread James Henstridge
I hadn't realised that they renamed the IM module with the version bump:
that means snaps built against older platforms won't load the old (but
working) Fcitx 4 module when run on a host system configured with Fcitx
5.

We can certainly look at adding the new IM module to the platform snaps,
but that will also switch to the new IPC protocol.  From a quick look
through the source it will probably be allowed by existing AppArmor
rules in the "desktop" interface, but that will need testing.

It's probably going to be easiest to see if we can get things working
with a core20 based platform snap though, since we have fcitx5 packages
there (albeit for a git prerelease version).

For the core18 based platform snaps, we would need to backport the
fcitx5 packages themselves.  Alternatively, I wonder if we could get
away with symlinking the old module name to the new one?

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1930945] Re: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)

2021-06-04 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu desktop - changing display configuration lost wallpaper (trap
  messages filled dmesg)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Impish daily test on
  - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  Changing display positions in settings.  I have two monitors, one
  above the other (so not the default).

  I made change and it looked okay so I said keep. I noticed I was wrong
  having TOP/BOTTOM displays the wrong way (detected via mouse movements
  between displays) so I made another change of the TOP/BOTTOM displays
  in "DISPLAYS" of GNOME settings clicked apply again & keep...

  ** Expected Results

  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen

  ** Actual Results

  I now have BLUE background on both displays.

  (this was soon changing.. but that didn't occur until I tried to
  change wallpapers...)

  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930945/+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 1930946] [NEW] Upgrade from 20.10 to 21.04 changes anthy settings

2021-06-04 Thread DarkTrick
Public bug reported:

On 20.10 Anthy was set to choose the keyboard layout according to the current 
input language. 
After the upgrade to 21.04, this setting got lost; Apparently the settings of 
anthy are not upgrade-safe.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: anthy 1:0.4-2
ProcVersionSignature: Ubuntu 5.11.0-19.20-generic 5.11.21
Uname: Linux 5.11.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Jun  5 12:46:04 2021
SourcePackage: anthy
UpgradeStatus: Upgraded to hirsute on 2021-06-05 (0 days ago)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Upgrade from 20.10 to 21.04 changes anthy settings

Status in anthy package in Ubuntu:
  New

Bug description:
  On 20.10 Anthy was set to choose the keyboard layout according to the current 
input language. 
  After the upgrade to 21.04, this setting got lost; Apparently the settings of 
anthy are not upgrade-safe.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: anthy 1:0.4-2
  ProcVersionSignature: Ubuntu 5.11.0-19.20-generic 5.11.21
  Uname: Linux 5.11.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sat Jun  5 12:46:04 2021
  SourcePackage: anthy
  UpgradeStatus: Upgraded to hirsute on 2021-06-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anthy/+bug/1930946/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2021-06-04 Thread Chris Guiver
Booted today's impish daily (live QA-test) on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

On initial boot there were glitches on the top of the display (panel &
top of wallpaper below panel).  It booted with wallpaper (not no
wallpaper today so not identical).

On changing wallpaper I get either
- correct wallpaper
- glitchy version (blocky bad-digital-reception type) of wallpaper some of 
which looks, parts do not
- no background
- magnified version of wallpaper so only part visible  (current image is like 
it's 1/8th of chosen 'hippo' wallpaper instead of all of it... part of image 
though is warped

choosing the same wallpaper does NOT mean you get the same result the
next time though

** Tags added: impish

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1930945] Re: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)

2021-06-04 Thread Chris Guiver
Possibly related (duplicate of)?

- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893493


** Description changed:

- Ubuntu Desktop Impish daily test.
+ Ubuntu Desktop Impish daily test on
+ - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  
  Changing display positions in settings.  I have two monitors, one above
  the other (so not the default).
  
- I made change and it look okay so I said keep. I noticed I was wrong
- having TOP/BOTTOM displays the wrong way, detected via mouse movements
- between displays so I made another change of the TOP/BOTTOM displays in
- "DISPLAYS" of GNOME settings...
+ I made change and it looked okay so I said keep. I noticed I was wrong
+ having TOP/BOTTOM displays the wrong way (detected via mouse movements
+ between displays) so I made another change of the TOP/BOTTOM displays in
+ "DISPLAYS" of GNOME settings clicked apply again & keep...
  
  ** Expected Results
  
  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen
  
  ** Actual Results
  
  I now have BLUE background on both displays.
+ 
+ (this was soon changing.. but that didn't occur until I tried to change
+ wallpapers...)
  
  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu desktop - changing display configuration lost wallpaper (trap
  messages filled dmesg)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Impish daily test on
  - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  Changing display positions in settings.  I have two monitors, one
  above the other (so not the default).

  I made change and it looked okay so I said keep. I noticed I was wrong
  having TOP/BOTTOM displays the wrong way (detected via mouse movements
  between displays) so I made another change of the TOP/BOTTOM displays
  in "DISPLAYS" of GNOME settings clicked apply again & keep...

  ** Expected Results

  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen

  ** Actual Results

  I now have BLUE background on both displays.

  (this was soon changing.. but that didn't occur until I tried to
  change wallpapers...)

  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930945/+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 1930945] Re: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)

2021-06-04 Thread Chris Guiver
I'm unable to change wallpaper now.

On selecting some they appear to flash on screen, then get replaced by a
image... currently this firefox window appears on my other display with
this "add comment" box frozen at the word "currently" last line when the
image was changed...

Wallpaper on other image just re-freshed, now contains all of last
paragraph... setting is on the 'clock' or change image..

No squashfs errors appear in `dmesg`.

As stated earlier.. operation of box appears unimpacted, however the
'firefox' image replacing the originally-blue background is a
concentration-problem for me..

The other screen now appears to be updating regularly as I type, rather
than time interval.. behavior appears somewhat inconsistent with
background (no longer static).

Likely nouveau/nvidia issue; sorry I was unsure thus the incorrect
`ubuntu-desktop`.

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

Title:
  ubuntu desktop - changing display configuration lost wallpaper (trap
  messages filled dmesg)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Impish daily test.

  Changing display positions in settings.  I have two monitors, one
  above the other (so not the default).

  I made change and it look okay so I said keep. I noticed I was wrong
  having TOP/BOTTOM displays the wrong way, detected via mouse movements
  between displays so I made another change of the TOP/BOTTOM displays
  in "DISPLAYS" of GNOME settings...

  ** Expected Results

  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen

  ** Actual Results

  I now have BLUE background on both displays.

  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930945/+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 1930945] [NEW] ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)

2021-06-04 Thread Chris Guiver
Public bug reported:

Ubuntu Desktop Impish daily test.

Changing display positions in settings.  I have two monitors, one above
the other (so not the default).

I made change and it look okay so I said keep. I noticed I was wrong
having TOP/BOTTOM displays the wrong way, detected via mouse movements
between displays so I made another change of the TOP/BOTTOM displays in
"DISPLAYS" of GNOME settings...

** Expected Results

On changing display orientation I expect wallpaper to be redrawn, or
remain on screen

** Actual Results

I now have BLUE background on both displays.

/var/crash is empty... operation appears normal; I lost background.
lots of TRAP messages though fill `dmesg`

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-desktop 1.469
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  5 03:01:52 2021
LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

** Attachment added: "sudo dmesg >dmesg.txt"
   https://bugs.launchpad.net/bugs/1930945/+attachment/5502569/+files/dmesg.txt

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

Title:
  ubuntu desktop - changing display configuration lost wallpaper (trap
  messages filled dmesg)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Impish daily test.

  Changing display positions in settings.  I have two monitors, one
  above the other (so not the default).

  I made change and it look okay so I said keep. I noticed I was wrong
  having TOP/BOTTOM displays the wrong way, detected via mouse movements
  between displays so I made another change of the TOP/BOTTOM displays
  in "DISPLAYS" of GNOME settings...

  ** Expected Results

  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen

  ** Actual Results

  I now have BLUE background on both displays.

  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930945/+subscriptions

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


Re: [Desktop-packages] [apparmor] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-04 Thread Seth Arnold
On Sat, Jun 05, 2021 at 01:27:19AM -, Gunnar Hjalmarsson wrote:
> It means that it explicitly looks for the fcitx 5 gtk im module, while
> Chromium only has access to the fcitx 4 one.

Oh! Excellent debugging to find the root cause.

Thanks

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-04 Thread Gunnar Hjalmarsson
I presented the snap problem for James Henstridge, and he gave me a very
useful hint: The Chromium snap makes use of the bionic library stack
(the gnome-3-28-1804 snap) including the im module installed by fcitx-
frontend-gtk3, i.e. the fcitx 4 gtk im module.

That made me think of . That bug is
still open, and as a result im-config currently sets these variables for
fcitx 5:

GTK_IM_MODULE=fcitx5
XMODIFIERS=@im=fcitx
QT_IM_MODULE=fcitx5

It means that it explicitly looks for the fcitx 5 gtk im module, while
Chromium only has access to the fcitx 4 one.

So as a test I tweaked im-config to set:

GTK_IM_MODULE=fcitx
XMODIFIERS=@im=fcitx
QT_IM_MODULE=fcitx

and that made a difference. With that environment I could successfully
input beautiful Chinese characters in Chromium using fcitx 5. :)

Consequently there seems to be no need to add any extra stuff to
apparmor to handle fcitx 5. Instead I see two options:

1. Change im-config's variable assignment, or

2. somehow add the fcitx 5 im modules for gtk and qt to the snap library
stack.

I'm going to consult with Debian's input method team about which route
is preferable.

@James: Do you see a problem from your POV with adding the fcitx 5 im
modules to the snaps?

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

** Also affects: snappy
   Importance: Undecided
   Status: New

** Package changed: apparmor (Ubuntu) => im-config (Ubuntu)

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1215882] Re: Emails are silently discarded on 554 reply to STARTTLS

2021-06-04 Thread Bug Watch Updater
** Changed in: thunderbird
   Status: Confirmed => Invalid

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
/usr/lib/mozilla/extensions/{3550f703

[Desktop-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")

2021-06-04 Thread Mathew Hodson
Patch sent upstream:

https://patchwork.ozlabs.org/project/hostap/patch/20210525031333.7665-1-mathew.hod...@gmail.com/

** Tags added: patch-forwarded-upstream

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

Title:
  Typo in man page ("introduce a much improvement mechanism")

Status in One Hundred Papercuts:
  Triaged
Status in wpa package in Ubuntu:
  Triaged
Status in wpa package in Debian:
  New

Bug description:
  "introduce a much improvement mechanism" should be "introduce a much
  improved mechanism".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 24 16:19:30 2014
  InstallationDate: Installed on 2014-12-19 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2021-06-04 Thread rns
We have a [Smtpd.jsm](https://searchfox.org/comm-
central/source/mailnews/test/fakeserver/Smtpd.jsm) fakeserver for
testing, we don't have a test case for this bug though.

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847

[Desktop-packages] [Bug 1215882]

2021-06-04 Thread Jonathan Kamens
The other reason this is a critical bug is because if the user does not
have Thunderbird configured to save messages in Sent Mail -- which the
user *shouldn't*, e.g., if the user is using Gmail, since Gmail saves
outbound messages automatically, then this bug causes DATA LOSS by
closing the window without saving the message ANYWHERE.

Can believe this bug is still not fixed after nearly a decade. Glad to
see it's about to be fixed, but as someone else pointed out in a recent
comment, if this is just a matter of changing the status codes that
cause Thunderbird to leave the compose window open, then maybe we should
make that fix in TB78 rather than waiting until the next major release
for it to be fixed?

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMM

[Desktop-packages] [Bug 1215882]

2021-06-04 Thread Mkmelin+mozilla
Thunderbird 91 is just around the corner, and any change to 78 could no
longer get beta testing, so even with a fix to the old code we would not
take it at this point.

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a0

[Desktop-packages] [Bug 1215882]

2021-06-04 Thread Vseerror
I just realized Ben has a test script comment 160.  Does smtp-js have a
test library, and does it cover this?

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigma

[Desktop-packages] [Bug 1215882]

2021-06-04 Thread Vseerror
Do we expect this to be gone with smtp-js?

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d

[Desktop-packages] [Bug 1215882]

2021-06-04 Thread rns
(In reply to Wayne Mery (:wsmwk) from comment #180)
> Do we expect this to be gone with smtp-js?

Yes, I think so. Compose window is still open in my local test.

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1

[Desktop-packages] [Bug 440051] Re: Firefox should not offer a manual install of Flash on First Run

2021-06-04 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Expired

** Changed in: firefox
   Importance: Wishlist => Medium

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

Title:
  Firefox should not offer a manual install of Flash on First Run

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox-3.0

  After installing today's updates in Jaunty, when first opening Firefox
  I get a greeting with this message:

  You should update Adobe Flash Player right now.

  Firefox is up to date, but your current version of Flash Player can
  cause security and stability issues. Please install the free update as
  soon as possible.

  This links to http://get.adobe.com/flashplayer/ which proposes a
  manual download and installation of Flash.

  AFAIK my version is current (alpha 64-bit version of Flash), Firfox
  shouldn't be attempting to detect nor correct such updates. This
  should be handled by the packaging system in Ubuntu.

  Not sure if this affects non-64-bit versions.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia wl
  Package: firefox 3.0.14+build2+nobinonly-0ubuntu0.9.04.1
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.28-15-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/440051/+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 1335388] Re: Firefox does not play local flash files

2021-06-04 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Expired

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

Title:
  Firefox does not play local flash files

Status in Mozilla Firefox:
  Expired
Status in Linux Mint:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xubuntu 14.04 I cannot play local swf files int
  Firefox any more. Was OK in 13.10.

  I get the window "You have chosen to open: xxx.swf which is: Shockwave Flash 
file (yyyMB) from: /home/...
  What should Firefox do with this file?
  - Open with (Parole/Other...)
  - Save File
  Do this automatically...

  Reinstalling 14.04 completely (and installing flashplugin-installer) and 
creating a new user does not help.
  Of course this works well with flash embedded in html pages.

  In Firefox, there are 2 entries in the applications menu, one for"shockwave 
flash files" and the other for "SWF", as described in 
https://support.mozilla.org/en-US/questions/995797.
  I cannot link the action "Use shockwave flash (in Firefox)" to the type 
"shockwave flash files" as it is for "SWF file".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 30.0+build1-0ubuntu0.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  malaise2839 F pulseaudio
  BuildID: 20140608211132
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Jun 28 09:16:51 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-06-15 (12 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.0.254 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.5  metric 9
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}/defaults/preferences/prefs-dwhelper.js
  Profiles: Profile0 (Default) - LastVersion=30.0/20140608211132 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3259CGG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:svnLENOVO:pn3259CGG:pvrThinkPadEdgeE530:rvnLENOVO:rn3259CGG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3259CGG
  dmi.product.version: ThinkPad Edge E530
  dmi.sys.vendor: LENOVO

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

2021-06-04 Thread Niklasbetz20
Adobe Flash is no longer supported.

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

Title:
  Firefox should not offer a manual install of Flash on First Run

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox-3.0

  After installing today's updates in Jaunty, when first opening Firefox
  I get a greeting with this message:

  You should update Adobe Flash Player right now.

  Firefox is up to date, but your current version of Flash Player can
  cause security and stability issues. Please install the free update as
  soon as possible.

  This links to http://get.adobe.com/flashplayer/ which proposes a
  manual download and installation of Flash.

  AFAIK my version is current (alpha 64-bit version of Flash), Firfox
  shouldn't be attempting to detect nor correct such updates. This
  should be handled by the packaging system in Ubuntu.

  Not sure if this affects non-64-bit versions.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia wl
  Package: firefox 3.0.14+build2+nobinonly-0ubuntu0.9.04.1
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.28-15-generic x86_64

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

2021-06-04 Thread Marja Erwin
Depending on browser settings, Adobe's website can strobe, trigger
migraines, and for some people, trigger seizures, with several refreshes
per second. I think it may be a cookie-handling bug. Firefox shouldn't
point any users to the website.

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

Title:
  Firefox should not offer a manual install of Flash on First Run

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox-3.0

  After installing today's updates in Jaunty, when first opening Firefox
  I get a greeting with this message:

  You should update Adobe Flash Player right now.

  Firefox is up to date, but your current version of Flash Player can
  cause security and stability issues. Please install the free update as
  soon as possible.

  This links to http://get.adobe.com/flashplayer/ which proposes a
  manual download and installation of Flash.

  AFAIK my version is current (alpha 64-bit version of Flash), Firfox
  shouldn't be attempting to detect nor correct such updates. This
  should be handled by the packaging system in Ubuntu.

  Not sure if this affects non-64-bit versions.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia wl
  Package: firefox 3.0.14+build2+nobinonly-0ubuntu0.9.04.1
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.28-15-generic x86_64

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

2021-06-04 Thread Niklasbetz20
Adobe Flash is no longer supported.

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

Title:
  Firefox does not play local flash files

Status in Mozilla Firefox:
  Expired
Status in Linux Mint:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xubuntu 14.04 I cannot play local swf files int
  Firefox any more. Was OK in 13.10.

  I get the window "You have chosen to open: xxx.swf which is: Shockwave Flash 
file (yyyMB) from: /home/...
  What should Firefox do with this file?
  - Open with (Parole/Other...)
  - Save File
  Do this automatically...

  Reinstalling 14.04 completely (and installing flashplugin-installer) and 
creating a new user does not help.
  Of course this works well with flash embedded in html pages.

  In Firefox, there are 2 entries in the applications menu, one for"shockwave 
flash files" and the other for "SWF", as described in 
https://support.mozilla.org/en-US/questions/995797.
  I cannot link the action "Use shockwave flash (in Firefox)" to the type 
"shockwave flash files" as it is for "SWF file".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 30.0+build1-0ubuntu0.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  malaise2839 F pulseaudio
  BuildID: 20140608211132
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Jun 28 09:16:51 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-06-15 (12 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.0.254 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.5  metric 9
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}/defaults/preferences/prefs-dwhelper.js
  Profiles: Profile0 (Default) - LastVersion=30.0/20140608211132 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3259CGG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:svnLENOVO:pn3259CGG:pvrThinkPadEdgeE530:rvnLENOVO:rn3259CGG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3259CGG
  dmi.product.version: ThinkPad Edge E530
  dmi.sys.vendor: LENOVO

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

2021-06-04 Thread Rguenth
GCC 9.4 is being released, retargeting bugs to GCC 9.5.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1862053/+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 915059] Re: [Upstream] Compare Document highlighting unchanged words as changed

2021-06-04 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/915059

Title:
  [Upstream] Compare Document highlighting unchanged words as changed

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

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

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip
  && file-roller -h versions.zip && cd versions && lowriter -nologo
  version1.odt

  Edit -> Compare Document -> version2.odt -> Insert button

  is under Actions regarding the first Deletion top to bottom, one tan
  hyphen is shown to the left of "LibreOffice Writer" and "LibreOffice
  Writer" is not marked tan with a tan underline. An example of how it
  should look may be found via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files
  /versions-space.zip && file-roller -h versions-space.zip && cd
  versions-space && lowriter -nologo version1-space.odt

  Edit -> Compare Document -> version2-space.odt -> Insert button

  4) What happens instead is the hyphen to the left of "LibreOffice
  Writer" is not shown and "LibreOffice Writer" is marked tan with a tan
  underline.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/915059/+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 1388491] Re: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells

2021-06-04 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: In Progress => Fix Released

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

Title:
  [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects
  other cells

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  Step to reproduce:
  1. Open the attached ods file.
  2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur 
with copy)
  3. Select I5 and open Paste Special dialog (Shift+Ctrl+V).
  4. Enable "Transpose" option and Click "OK"

  Then, values of some cells in C9 to E10, which are not related to
  blank cells are changed:

  C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6)
  D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6)
  E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6)
  C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6)
  D10:  =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6)
  E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6)

  My environment is Ubuntu 14.04 LibreOffice 4.2.6.3

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

2021-06-04 Thread Qa-admin-q
Dear Leo H,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/915059

Title:
  [Upstream] Compare Document highlighting unchanged words as changed

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

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

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip
  && file-roller -h versions.zip && cd versions && lowriter -nologo
  version1.odt

  Edit -> Compare Document -> version2.odt -> Insert button

  is under Actions regarding the first Deletion top to bottom, one tan
  hyphen is shown to the left of "LibreOffice Writer" and "LibreOffice
  Writer" is not marked tan with a tan underline. An example of how it
  should look may be found via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files
  /versions-space.zip && file-roller -h versions-space.zip && cd
  versions-space && lowriter -nologo version1-space.odt

  Edit -> Compare Document -> version2-space.odt -> Insert button

  4) What happens instead is the hyphen to the left of "LibreOffice
  Writer" is not shown and "LibreOffice Writer" is marked tan with a tan
  underline.

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

2021-06-04 Thread timur
Created attachment 172605
version compared screen

This bug seems to have been resolved in 3.6 which makes it opposite to bug 
71155 which started then. 
Comparison attached.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/915059

Title:
  [Upstream] Compare Document highlighting unchanged words as changed

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

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

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip
  && file-roller -h versions.zip && cd versions && lowriter -nologo
  version1.odt

  Edit -> Compare Document -> version2.odt -> Insert button

  is under Actions regarding the first Deletion top to bottom, one tan
  hyphen is shown to the left of "LibreOffice Writer" and "LibreOffice
  Writer" is not marked tan with a tan underline. An example of how it
  should look may be found via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files
  /versions-space.zip && file-roller -h versions-space.zip && cd
  versions-space && lowriter -nologo version1-space.odt

  Edit -> Compare Document -> version2-space.odt -> Insert button

  4) What happens instead is the hyphen to the left of "LibreOffice
  Writer" is not shown and "LibreOffice Writer" is marked tan with a tan
  underline.

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

2021-06-04 Thread Libreoffice-commits
scito committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/c82d96da1c9a03e1742f2f5a7a93b9993c96a0a0

tdf#68976 fix paste transposed regression for notes/patterns

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects
  other cells

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  Step to reproduce:
  1. Open the attached ods file.
  2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur 
with copy)
  3. Select I5 and open Paste Special dialog (Shift+Ctrl+V).
  4. Enable "Transpose" option and Click "OK"

  Then, values of some cells in C9 to E10, which are not related to
  blank cells are changed:

  C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6)
  D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6)
  E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6)
  C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6)
  D10:  =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6)
  E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6)

  My environment is Ubuntu 14.04 LibreOffice 4.2.6.3

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

2021-06-04 Thread Buzea-bogdan
it's ok in
Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 3b57ebb445df8a2bc3d916ea79f8af45e20e4e62
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ro-RO (ro_RO); UI: en-US
Calc: threaded

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

Title:
  Values cleared when scrolling in standard filter dialog

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I was actually developing a change for LibreOffice when I found this
  bug. It exists both on my installed version of LibreOffice (6.0.7.3)
  and the latest master branch (git commit
  058caeef45f9abf12e4e243aafbbb1c2ebcbc057).

  1. Create a spreadsheet with a column of data.
  2. Apply autofiltering to the column.
  3. Select "standard filter..." from the filter menu.
  4. Add a condition (e.g. "Number = 1").
  5. Click OK. Data will be filtered as expected.
  6. Close the spreadsheet.
  7. Open the spreadsheet again.
  8. Select "standard filter..." from the filter menu.
  9. Scroll down and up again in the filter dialog.

  Actual:
  The value "1" will be cleared for some reason.

  Expected:
  The value is not cleared by scrolling.

  This also exists in the master, except you don't even have to scroll
  down and back up. Simply moving the scrollbar at all will trigger this
  bug.


  Ubuntu Release:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  Package version:
  libreoffice:
Installed: (none)
Candidate: 1:6.0.7-0ubuntu0.18.04.10
Version table:
   1:6.0.7-0ubuntu0.18.04.10 500
  500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
   1:6.0.3-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  (But also in master branch of code.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 09:03:51 2020
  InstallationDate: Installed on 2019-09-14 (262 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1881811/+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 1930937] [NEW] Default dependency resolution in Focal pulls in full GNOME Desktop

2021-06-04 Thread Daniel Dadap
Public bug reported:

In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome
| polkit-1-auth-agent. Focal replaces this with a dependency on gnome-
shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when
install screen-resolution-extra (e.g. as a dependency of nvidia-
settings) on a system that doesn't already have GNOME or another polkit
auth agent installed, the default dependency resolution pulls in a full
GNOME desktop in Focal, while it does not do so under the same
circumstances in Bionic. This can be worked around by explicitly
installing policykit-1-gnome (or another package which provides the
polkit-1-auth-agent virtual package), but it would be nice to not pull
in GNOME by default on a system that doesn't already have it.

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

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

Title:
  Default dependency resolution in Focal pulls in full GNOME Desktop

Status in screen-resolution-extra package in Ubuntu:
  New

Bug description:
  In Bionic, screen-resolution-extra has a dependency on
  policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a
  dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent.
  As a result, when install screen-resolution-extra (e.g. as a
  dependency of nvidia-settings) on a system that doesn't already have
  GNOME or another polkit auth agent installed, the default dependency
  resolution pulls in a full GNOME desktop in Focal, while it does not
  do so under the same circumstances in Bionic. This can be worked
  around by explicitly installing policykit-1-gnome (or another package
  which provides the polkit-1-auth-agent virtual package), but it would
  be nice to not pull in GNOME by default on a system that doesn't
  already have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object

2021-06-04 Thread Jon Yoon
I've tried using boto3+s3:// as well before and it was unsuccessful.
Swapping it out with this newer version of duplicity produced an error
regarding the HeadBucket operation.

See new failure below. I turned up the verbosity to 9 for this one.

Note: My company is using Duplicity 0.8.11 and Duply in other servers
(Servers are running Ubuntu 20.04 w/Python 3.5.8) without issue.
However, this particular machine is the only one where we needed to
implement multipart chunks due to the size of the backup being so huge
compared to our other servers that don't need it.

I know that on a different server (Ubuntu 16.04) running Duplicity
0.7.19 on Python 2.7, the multipart chunking worked without issue, but
since we can't run that version of Python or Duplicity on this newer
version of Ubuntu, I'm not sure what else we need to do to get 0.8.19 to
work here.



Start duply v2.2, time is 2021-06-04 21:26:37.
Using profile '/root/.duply/artifactory_backup'.
Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 
2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU 
MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-rele
ase (x86_64-pc-linux-gnu)'.
Checking TEMP_DIR '/tmp' is a folder and writable (OK)
Test - En/Decryption skipped. (GPG disabled)

--- Start running command PRE at 21:26:37.615 ---
Skipping n/a script '/root/.duply/artifactory_backup/pre'.
--- Finished state OK at 21:26:37.628 - Runtime 00:00:00.012 ---

--- Start running command BKP at 21:26:37.659 ---
Using archive dir: /root/.cache/duplicity/duply_artifactory_backup
Using backup name: duply_artifactory_backup
GPG binary is gpg, version (2, 2, 19)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.boxbackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.gdrivebackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.idrivedbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.megav2backend Succeeded
Import of duplicity.backends.megav3backend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rclonebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.s3_boto3_backend Succeeded
Multiprocessing is not supported on linux, will use threads instead.
Import of duplicity.backends.s3_boto_backend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Reading globbing filelist /root/.duply/artifactory_backup/exclude
Main action: inc
Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile'

duplicity 0.8.19
Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption 
--verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing 
--s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist 
/root/.duply/artifactory_backup/exclude /labkey 
boto3+s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup
Linux ip-172-30-115-92 5.4.0-1049-aws #51-Ubuntu SMP Wed May 12 21:13:52 UTC 
2021 x86_64 x86_64
/usr/bin/python3 3.8.5 (default, May 27 2021, 13:30:53) 
[GCC 9.3.0]

Using temporary directory /tmp/duplicity-_k91zmc2-tempdir
Registering (mkstemp) temporary file 
/tmp/duplicity-_k91zmc2-tempdir/mkstemp-t1cl2e0h-1
Temp has 138928574464 available, backup will use approx 1395864371.
Backtrace of previous error: Traceback (innermost last):
  File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 384, in 
inner_retry
return fn(self, *args)
  File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 604, in list
return [toby

[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-06-04 Thread Brian Murray
It looks like version 30.4.1 didn't make into Hirsute, so I've opened a
task for that release of Ubuntu and escalated it to the desktop team.

** Also affects: evolution-data-server (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu Hirsute)
   Status: New => Triaged

** Tags added: rls-hh-incoming

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released
Status in evolution-data-server source package in Hirsute:
  Triaged

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1930145] Re: IBus Panel Show Icon on system tray doesn't persist

2021-06-04 Thread Gunnar Hjalmarsson
I noticed that the issue is present also on Kubuntu 20.04, so it has
been there for a while. It's not present on Ubuntu MATE, though, which
indicates that it's a KDE issue rather than an ibus one.

But @Cory, it would be good if you could clarify why it is a problem. In
short: Why do you want to have ibus-daemon running without seeing which
input source is currently in use? Understanding that would be useful to
determine the importance of the issue.

** Also affects: plasma-desktop (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: plasma-desktop (Ubuntu)
   Status: New => Confirmed

** Tags added: focal hirsute impish

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

Title:
  IBus Panel Show Icon on system tray doesn't persist

Status in ibus package in Ubuntu:
  Incomplete
Status in plasma-desktop package in Ubuntu:
  Confirmed

Bug description:
  After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon
  appears in the system tray despite "Show icon on system tray" NOT
  being checked.  Right clicking on the IBus Panel icon, checking "Show
  icon on system tray" and then unchecking again it causes the icon to
  be correctly hidden.  But the problem reappears after the next reboot.

  Another user reporting what is almost certainly the same behavior:
  https://www.reddit.com/r/kde/comments/j91t8f/ibus_panel_icon_in_system_tray/

  And this is an _identical_ bug report from 2012, so maybe it's a regression 
of some sort?
  https://bugzilla.redhat.com/show_bug.cgi?id=877135

  Based om the trouble shooting requested at that time I get:

  $ gconftool-2 --get /desktop/ibus/panel/show_icon_on_systray
  No value set for `/desktop/ibus/panel/show_icon_on_systray'

  Note that I am running KDE, in case that's the important detail.

  The primary problem is that if you click on it accidentally and close
  the panel, you lose all keyboard input.

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04
  $ apt-cache policy ibus
  ibus:
Installed: 1.5.24-1
Candidate: 1.5.24-1
Version table:
   *** 1.5.24-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1930145/+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 1930925] Re: Ubuntu 20.04 doesn't work with moidern KVMs

2021-06-04 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Ubuntu 20.04 doesn't work with moidern KVMs

Status in xorg package in Ubuntu:
  New

Bug description:
  I have recently acquired a acquired a desktop running ubuntu 20.04. I
  have several computers and switch between them using this KVM
  
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
  The other machines are either running windows or ubuntu 18.04 or
  earlier. They are all fine, but the with 20.04 machine neither the
  keyboard nor the mouse works. On the 18.04 machine I can see

  lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  and it is the Logitech, Inc. Unifying Receiver which appears when the
  USB from the KVM is connected. On the 20.04 machine only this appears

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
  Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I have tested installation discs from 19.04 onwards. The failure first
  appears in 19.10 and is still present in 21.04

  I can observe a similar problem with a dual boot laptop running
  windows 10 and 20.04. With windows 10 I can use it with the KVM for
  screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and
  mouse do not work. This issue has also been observed here
  https://unix.stackexchange.com/questions/646515/using-logitech-mouse-
  keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed
  it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model).

  I had to report this originally against xorg as this bug reporting
  system seems not to allow reporting of bugs against unknown packages.
  I also had to report it through the ubuntu-bug executable as I've been
  unable to find a way in launchpad of reporting a bug (as opposed to
  getting a guided tour about reporting bugs).

  I am happy to supply more info and test fixes if I am asked but as
  with this type of bug where something fails to happen rather than
  something wrong happens I don't know what to look at.

  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
  Date: Fri Jun  4 20:21:15 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-05-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
   |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 
12M
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2021
  dmi.bios.release: 8.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H570M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0820:bd04/27/2021:br8.20:svnASUS:pnSystemProductN

[Desktop-packages] [Bug 1930925] [NEW] Ubuntu 20.04 doesn't work with moidern KVMs

2021-06-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have recently acquired a acquired a desktop running ubuntu 20.04. I
have several computers and switch between them using this KVM
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
The other machines are either running windows or ubuntu 18.04 or
earlier. They are all fine, but the with 20.04 machine neither the
keyboard nor the mouse works. On the 18.04 machine I can see

lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and it is the Logitech, Inc. Unifying Receiver which appears when the
USB from the KVM is connected. On the 20.04 machine only this appears

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have tested installation discs from 19.04 onwards. The failure first
appears in 19.10 and is still present in 21.04

I can observe a similar problem with a dual boot laptop running windows
10 and 20.04. With windows 10 I can use it with the KVM for screen and
keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not
work. This issue has also been observed here
https://unix.stackexchange.com/questions/646515/using-logitech-mouse-
keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it
using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model).

I had to report this originally against xorg as this bug reporting
system seems not to allow reporting of bugs against unknown packages. I
also had to report it through the ubuntu-bug executable as I've been
unable to find a way in launchpad of reporting a bug (as opposed to
getting a guided tour about reporting bugs).

I am happy to supply more info and test fixes if I am asked but as with
this type of bug where something fails to happen rather than something
wrong happens I don't know what to look at.

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
Date: Fri Jun  4 20:21:15 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2021-05-14 (21 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
 |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2021
dmi.bios.release: 8.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0820
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H570M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0820:bd04/27/2021:br8.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH570M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl

[Desktop-packages] [Bug 1930914] [NEW] ubuntu-minimal depends on ubuntu-advantage-tools

2021-06-04 Thread Bartłomiej Żogała
Public bug reported:

This is counter to #1566183 There is no reason to enforce desktop users
who manage machine on their own to install ubuntu-advantage-tools,
especially when this is 'minimal' version.  This should include only
essential packages to make the OS functional

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-minimal 1.450.2
ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
Uname: Linux 5.4.0-73-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jun  4 18:54:56 2021
InstallationDate: Installed on 2020-01-29 (491 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

- This is counter to #1566183 There is no reason desktop users who manage
- machine on their own need to be enforced to install ubuntu-advantage-
- tools, especially when this is 'minimal' version which should include
- only essential packages to make the OS functional
+ This is counter to #1566183 There is no reason to enforce desktop users
+ who manage machine on their own to install ubuntu-advantage-tools,
+ especially when this is 'minimal' version.  This should include only
+ essential packages to make the OS functional
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-04 Thread Robert
How do I install Ubuntu 21.04.1 to test the fix?

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions

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


Re: [Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-04 Thread Gipsz Jakab
Thank you for the work,
ii gnome-shell 3.38.4-1ubuntu3~21.04.1
ii gnome-shell-common 3.38.4-1ubuntu3~21.04.1
ii gnome-shell-extension-prefs 3.38.4-1ubuntu3~21.04.1

I updated the above packages from proposed updates,
logged out and in to wayland,
enabled the dash-to-panel extension through firefox,
happily pressed the Super key just to check if I get back my desktop ( i did)
and started a few applications via the run field or whatever.

Seems to work.

Regards,

tg


On Fri, 4 Jun 2021 at 11:31, Timo Aaltonen <1922...@bugs.launchpad.net> wrote:
>
> Hello Gipsz, or anyone else affected,
>
> Accepted gnome-shell into hirsute-proposed. The package will build now
> and be available at https://launchpad.net/ubuntu/+source/gnome-
> shell/3.38.4-1ubuntu3~21.04.1 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> hirsute to verification-done-hirsute. If it does not fix the bug for
> you, please add a comment stating that, and change the tag to
> verification-failed-hirsute. In either case, without details of your
> testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Tags added: verification-needed verification-needed-hirsute
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1922353
>
> Title:
>   Overview sometimes fails to appear or disappear in gnome-shell 3.38
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Hirsute:
>   Fix Committed
> Status in gnome-shell source package in Impish:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   Shell overview gets stuck where it's permanently toggled but not
>   visible. Only app windows appear in their overview state. Can't
>   interact with applications anymore.
>
>   [Test Plan]
>
>   1. Log into GNOME.
>   2. Press Super+A
>   3. Click on 'Files' and wait till it has launched.
>   4. Press the Super key.
>   Expect: Can interact with the application window.
>
>   [Where problems could occur]
>
>   Since the patch affects some of the core gnome-shell layout logic,
>   anything is possible. Risk has been mitigated by the patch being
>   small.
>
>   [Original description]
>
>   When I press the "windows" or "options" or "super" key a list of
>   running applications (like alt-tab) and a text window appears. I can
>   choose from the running applications or write a command into the text
>   window. After I chose an application or press ESC all this disappear
>   and I can do my thing.
>
>   Since trying 21.04 sometimes this
>   1. does not appear properly - there is no visible text window
>   2. does not disappear - despite what I click on or what keys do I press 
> this never disappear so I can not use my running applications or start 
> anything new even from the menu.
>
>   I have to log out and in to break this.
>
>   Disabling my gnome-shell extensions or using xorg instead of wayland
>   does not helps.
>
>   Since upgrading this morning this happens every time I press Super,
>   not just occasionally, thus making my desktop unusable.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: gnome-shell 3.38.4-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
>   Uname: Linux 5.11.0-13-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu61
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr  2 14:07:39 2021
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-03-19 (378 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions


--
we do what we must because we can

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

Title

[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-04 Thread Noctis Bennington
I have the same bug here. You can activate or turn it off but the
bluetooth is always "off", for me happens sometimes when I reboot.

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  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
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:744804 acl:76 sco:0 events:105989 errors:0
TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-04 Thread Luca Bellinzaghi
Hello

tested package: gnome-shell
version: 3.38.4-1ubuntu3~21.04.1

Machine: Lenovo ThinkPad T430

root@TP-T430:~# uname -r
5.11.0-18-generic

root@TP-T430:~# apt-cache policy gnome-shell| grep Install
  Installato: 3.38.4-1ubuntu3~21.04.1


steps undertaken to test:

1. Log into GNOME.
2. Press Super+A
3. Click on 'Files' and wait till it has launched.
4. Press the Super key.

Expected: Can interact with the application window.

Result: I can interact with the system as expected.

This release fixed the bug for me.

Thanks!

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set

2021-06-04 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Frequent kernel oops related to nvidia / nv_drm_master_set

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading yesterday from ubuntu 20 to 21.04 my machine now
  exhibits frequent involuntary restarts, related to a kernel oops of
  the form

  Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
  [...]
  Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
  Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
  Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
  Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
  Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
  Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
  Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
  Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
  Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
  Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
  Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  4 17:00:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
   nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-09 (391 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: NA ZBOX-ER51070
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: ZBOX-ER51070
  dmi.board.vendor: NA
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZBOX-ER51070
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: NA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  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

[Desktop-packages] [Bug 1930903] [NEW] Frequent kernel oops related to nvidia / nv_drm_master_set

2021-06-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading yesterday from ubuntu 20 to 21.04 my machine now
exhibits frequent involuntary restarts, related to a kernel oops of the
form

Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[...]
Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jun  4 17:00:45 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
 nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
InstallationDate: Installed on 2020-05-09 (391 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: NA ZBOX-ER51070
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ZBOX-ER51070
dmi.board.vendor: NA
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ZBOX-ER51070
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: NA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubuntu
-- 
Frequent kernel oops related to nvidia / nv_drm_master_set
https://bugs.launchpad.net/bugs/1930903
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
Mailing list: ht

[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)

2021-06-04 Thread fprietog
Proposed fix tested in hirsute on a Raspberry Pi4 arm64 and on an PC
amd64.

Packages installed from hirsute-proposed:

libgjs0g (1.68.1-1~ubuntu0.21.04.1)
gjs (1.68.1-1~ubuntu0.21.04.1)

And, after reboot, do those tests:

1./ Test case:
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 
'delete_async', 'delete_finish');
   print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo 
GJS works
[object Promise]
GJS works

2./ The error shown in every boot is gone.

3./ The indicator-multiload app is working as expected

So the bug seem to be fixed. Thanks and best regards.

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

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

Title:
  Gjs promises on Gio.File operations don't work anymore after upgrading
  libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)

Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Won't Fix
Status in gjs source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  As per glib commit
  https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
  Gio.File.new_for_path("") returns a GDummyFile implementation, while
  Gio._promisify relies on it being a LocalFile, so we don't promisify
  the right methods.

  [ Test case ]

  gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 
'delete_async', 'delete_finish');
 print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && 
echo GJS works

  Should write on terminal:

  [object Promise]
  GJS works

  In the bugged version would instead just:

  (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method 
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
  @:2:48

  (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script 
  threw an exception

  
  [ Regression potential ]

  Gjs apps are slower in starting up, or not act properly when / is not
  a local location.

  ---

  
  Problem tested in two different environments:
  - Ubuntu 21.04 Beta amd64
  - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

  After upgrading these packages:

  libglib2.0-02.67.5-2 to 2.68.0-1
  libglib2.0-bin  2.67.5-2 to 2.68.0-1
  libglib2.0-data 2.67.5-2 to 2.68.0-1

  The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
  three dots (...) instead of the graphic expected. It's throwing error
  messages to the system journal every second or so (depends of the
  refresh interval selected in the app settings):

  abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
  multiload, Impossible to read image from path '/run/user/1026
  /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
  TypeError: method Gio.File.read_async: At least 3 arguments required,
  but only 2 passed

  Don't know if this is a documented change of that method and the bug
  should be open for the indicator-multiload app. Please, if that's the
  case just let me know to do it.

  Thanks and best reagrds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-04 Thread Sebastien Bacher
** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

** Changed in: thunderbird (Ubuntu)
   Status: New => In Progress

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in

2021-06-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: plasma-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  No virtual terminals (CTRL+ALT+F?) when no user logged in

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed

Bug description:
  As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to 
reproduce:
  - boot Ubuntu
  - Press Ctrl+Alt+F2 (or F3 or...)

  Expected behaviour: virtual console should appear with login prompt.
  Actual behaviour: nothing happens.

  When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3...
  However, hitting first Ctrl+Alt+F1 and, subsequently, hitting
  Ctrl+Alt+F3 does not show tty3, and remains at the graphical login
  screen but keyboard and mouse are unresponsive until either
  Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal
  the ubuntu session is running at.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 10:11:26 2018
  InstallationDate: Installed on 2014-05-05 (1418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-04 Thread Francois Thirioux
Firefox snap gets this one, TB snap does not:

pulseaudiofirefox:pulseaudio  :pulseaudio
-

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  New

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-04 Thread Francois Thirioux
I can select a custom sound from /usr/share/sounds, I don't get a deny
of access.

Enter snap name: thunderbird

Available connections:
Interface Connecteur   Prise
Notes
audio-playbackthunderbird:audio-playback   :audio-playback  
-
avahi-observe thunderbird:avahi-observe-
-
browser-support   thunderbird:browser-sandbox  :browser-support 
-
camerathunderbird:camera   -
-
content[gnome-3-34-1804]  thunderbird:gnome-3-34-1804  
gnome-3-34-1804:gnome-3-34-1804  -
content[gtk-3-themes] thunderbird:gtk-3-themes 
gtk-common-themes:gtk-3-themes   -
content[icon-themes]  thunderbird:icon-themes  
gtk-common-themes:icon-themes-
content[sound-themes] thunderbird:sound-themes 
gtk-common-themes:sound-themes   -
cups-control  thunderbird:cups-control :cups-control
manual
desktop   thunderbird:desktop  :desktop 
-
desktop-legacythunderbird:desktop-legacy   :desktop-legacy  
-
gpg-keys  thunderbird:gpg-keys -
-
gsettings thunderbird:gsettings:gsettings   
-
home  thunderbird:home :home
-
network   thunderbird:network  :network 
-
network-control   thunderbird:network-control  -
-
openglthunderbird:opengl   :opengl  
-
removable-media   thunderbird:removable-media  -
-
wayland   thunderbird:wayland  :wayland 
-
x11   thunderbird:x11  :x11 
-

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  New

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-04 Thread Olivier Tilloy
Thanks for the report François. This was previously reported at
https://forum.snapcraft.io/t/snap-thunderbird-plays-no-sounds/23953. I'm
quoting my comment from that thread here:

  Can you share the output of the following command?

snap connections thunderbird

  Also, if you’re trying to use a custom sound file, it might be that
the snap sandboxing doesn’t allow the application to read that file.
Where is that file located on disk?

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  New

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-06-04 Thread Marian Rainer-Harbach
Hi, when will this bug be fixed in 21.04/Hirsute?

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1930887] [NEW] [snap] Thunderbird 78.11 does not play new email sound

2021-06-04 Thread Francois Thirioux
Public bug reported:

(Was the same before v. 78.11.)

TB does not play a sound when a new mail incomes, even if the correct option is 
selected.
Changing from default to custom sound does not change the issue.

New emails notifications do work as intended, except sound.

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

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  New

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)

2021-06-04 Thread fprietog
Proposed fix tested in hirsute on a Raspberry Pi4 arm64, kernel
5.11.0-1009-raspi

Packages installed from hirsute-proposed:

gnome-shell (3.38.4-1ubuntu3~21.04.1)
gnome-shell-common (3.38.4-1ubuntu3~21.04.1)
gnome-shell-extension-prefs (3.38.4-1ubuntu3~21.04.1)

After reboot I've activated calendar sync with my google account and the
reported problem is gone. I also check that the calendar sync worked as
expected.

So the bug seem to be fixed. Thanks and best regards.

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

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

Title:
  gnome-shell-calendar-server assert failure on arm64: double free or
  corruption (fasttop)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell-calendar-server crashes (and it seems to happen more in
  aarch64).

  https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
  https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1

  [ Test case ]

  There's not a clear test case, but this is relevant:
   - Configure a supported calendar in your online accounts 
   - GNOME shell should show your events in the calendar (under notifications 
panel)

  [ Regression potential ]

  gnome-shell-calendar-server may leak memory.

  
  ---

  M1 Mac mini
  Parallels Ubuntu VM

  ProblemType: CrashDistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic aarch64
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: arm64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 04:34:36 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
   b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
  InstallationDate: Installed on 2021-02-17 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
  ProcCmdline: /usr/libexec/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x81240c08 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=, p=0xe9eee300, have_lock=0) at 
malloc.c:4298
   g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell-calendar-server assert failure: double free or corruption 
(fasttop)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+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 1930863] Re: Browser hangs activating HTML select element

2021-06-04 Thread AlexB
** Summary changed:

- Failed to load module "xapp-gtk3-module"
+ Browser hangs activating HTML select element

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

Title:
  Browser hangs activating HTML select element

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium snap, whilst browsing a website, I sometimes experience
  a browser hang activating a HTML select element. I'm running Ubuntu
  21.04 with the Ubuntu Unity package installed.

  I have the following output when I start the browser via the command
  line.

  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  Gtk-Message: 11:06:53.360: Failed to load module "xapp-gtk3-module"

  (chrome:34804): dbind-WARNING **: 11:06:53.486: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-BrZcGTnIin: No such 
file or directory
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [34912:34912:0604/110653.545090:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [34804:34897:0604/110738.564042:ERROR:gpu_process_host.cc(1002)] GPU process 
exited unexpectedly: exit_code=512
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [35415:35415:0604/110738.670097:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930863/+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 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object

2021-06-04 Thread Kenneth Loafman
Yes, it should be urllib3.  We keep the older boto+s3:// around because
it is still needed.

Try using the boto3+s3:// backend instead.

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

Title:
  Error when using S3 multipart upload - TypeError: cannot use a string
  pattern on a bytes-like object

Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  I followed the solution in
  https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I
  was running duplicity 0.8.11.1612-1 as well), but after upgrading to
  0.8.19, the problem still persists for me when trying to use S3
  multipart uploads.

  Note: This problem doesn't appear to exist in duplicity 0.7.17 running
  on python2.7, which is making me wonder if this is a python3.8 related
  issue.


  user@host:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  user@host:~$ apt-cache policy duplicity
  duplicity:
Installed: 0.8.19-ppa202104291804~ubuntu20.04.1
Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1
Version table:
   *** 0.8.19-ppa202104291804~ubuntu20.04.1 500
  500 
http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.8.11.1612-1 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 
Packages

  Start duply v2.2, time is 2021-06-02 22:58:11.
  Using profile '/root/.duply/artifactory_backup'.
  Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), 
gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, 
GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release 
(x86_64-pc-linux-gnu)'.
  Checking TEMP_DIR '/tmp' is a folder and writable (OK)
  Test - En/Decryption skipped. (GPG disabled)

  --- Start running command PRE at 22:58:11.550 ---
  Skipping n/a script '/root/.duply/artifactory_backup/pre'.
  --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 ---

  --- Start running command BKP at 22:58:11.595 ---
  Using archive dir: /root/.cache/duplicity/duply_artifactory_backup
  Using backup name: duply_artifactory_backup
  GPG binary is gpg, version (2, 2, 19)
  Import of duplicity.backends.adbackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk'
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Succeeded
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.gdrivebackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.idrivedbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.jottacloudbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.megav2backend Succeeded
  Import of duplicity.backends.megav3backend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pcabackend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rclonebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.s3_boto3_backend Succeeded
  Multiprocessing is not supported on linux, will use threads instead.
  Import of duplicity.backends.s3_boto_backend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  Setting multipart boto backend process pool to 4 processes
  Reading globbing filelist /root/.duply/artifactory_backup/exclude
  Main action: inc
  Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile'
  

  duplicity 0.8.19
  Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption 
--verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing 
--s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist 
/root/.duply/artifactory_backup/exclude /MyDirectory 
s3:/

[Desktop-packages] [Bug 1929304] Re: file-roller / gnome archive manager fails to extract

2021-06-04 Thread Marc Deslauriers
** Also affects: gnome-autoar (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-autoar (Ubuntu Impish)
   Importance: Low
 Assignee: Sebastien Bacher (seb128)
   Status: Fix Committed

** Also affects: gnome-autoar (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-autoar (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: gnome-autoar (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: gnome-autoar (Ubuntu Bionic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gnome-autoar (Ubuntu Focal)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gnome-autoar (Ubuntu Groovy)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gnome-autoar (Ubuntu Hirsute)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gnome-autoar (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gnome-autoar (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gnome-autoar (Ubuntu Groovy)
   Status: New => In Progress

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

** Changed in: gnome-autoar (Ubuntu Hirsute)
   Status: Incomplete => In Progress

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

Title:
  file-roller / gnome archive manager fails to extract

Status in gnome-autoar package in Ubuntu:
  Fix Committed
Status in gnome-autoar source package in Bionic:
  In Progress
Status in gnome-autoar source package in Focal:
  In Progress
Status in gnome-autoar source package in Groovy:
  In Progress
Status in gnome-autoar source package in Hirsute:
  In Progress
Status in gnome-autoar source package in Impish:
  Fix Committed

Bug description:
  problem occurs with :

  a) ubuntu 20.04.2 | gnome version 3.36.8 | X11

  b) fedora 34 | gnome 40.0.1 | wayland

  the latest version of gnome archive manager which is 3.36.3 fails to
  extract a .gz file which it used to do earlier.

  here are 2 links to 2 separate versions of hard disk sentinel linux
  version :

  1. https://www.hdsentinel.com/hdslin/hdsentinel-018c.gz

  2. https://www.hdsentinel.com/hdslin/hdsentinel-019c-x64.gz

  when i try to extract both the above mentioned files by right clicking
  & then extract here all i get is an empty folder with nothing
  extracted in it.

  if i open the gnome archive manager 3.36.3 from the applications menu
  & then try to extract the 1st file hard disk sentinel version 018c the
  extraction is successful.

  but if i open the gnome archive manager 3.36.3 from the applications
  menu & then try to extract the 2nd file hard disk sentinel version
  019c it only makes a copy of the .gz file.

  the earlier version of gnome archive manager which is default / built-in the 
ubuntu 20.04.2 iso
  did not have this problem it is only after the update that the gnome archive 
manager fails to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1929304/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-04 Thread Adalberto
Hello
I can confirm that release "3.38.4-1ubuntu3~21.04.1" of "gnome-shell" and 
"gnome-shell-common" packages has solved the issue for me, tested on kernel 
5.11.0-19-generic on my Lenovo Yoga 7 laptop.
The fix solved the issue in "Ubuntu on X.org" but also, and more importantly, 
on standard Wayland user interface!
Now selecting a window in "Activities" effectively switches to that window as 
expected.

Thank you all for this quick resolution!

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

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-04 Thread Jani Uusitalo
I can reproduce the crash at will with the steps I listed above, so I
don't have to wait for it to happen. It also doesn't forcibly log me
out, so I can enter those commands by just having a terminal window
present when I trigger the issue. But I logged out here (after
triggering) anyway since you instructed me to log in, in case it
matters.

Also, there's lots of noise in these from Boinc, thanks to #1876313.


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502425/+files/journal.txt

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

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

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-04 Thread Jani Uusitalo
** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502426/+files/prevboot.txt

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

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

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930863] [NEW] Failed to load module "xapp-gtk3-module"

2021-06-04 Thread AlexB
Public bug reported:

Using chromium snap, whilst browsing a website, I sometimes experience a
browser hang activating a HTML select element. I'm running Ubuntu 21.04
with the Ubuntu Unity package installed.

I have the following output when I start the browser via the command
line.

ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
Gtk-Message: 11:06:53.360: Failed to load module "xapp-gtk3-module"

(chrome:34804): dbind-WARNING **: 11:06:53.486: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-BrZcGTnIin: No such 
file or directory
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
[34912:34912:0604/110653.545090:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[34804:34897:0604/110738.564042:ERROR:gpu_process_host.cc(1002)] GPU process 
exited unexpectedly: exit_code=512
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
[35415:35415:0604/110738.670097:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Using chromium snap, whilst browsing a website, I sometimes experience a
  browser hang activating a HTML select element. I'm running Ubuntu 21.04
  with the Ubuntu Unity package installed.
+ 
+ I have the following output when I start the browser via the command
+ line.
  
  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  Gtk-Message: 11:06:53.360: Failed to load module "xapp-gtk3-module"
  
  (chrome:34804): dbind-WARNING **: 11:06:53.486: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-BrZcGTnIin: No such 
file or directory
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [34912:34912:0604/110653.545090:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [34804:34897:0604/110738.564042:ERROR:gpu_process_host.cc(1002)] GPU process 
exited unexpectedly: exit_code=512
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [35415:35415:0604/110738.670097:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

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

Title:
  Failed to load module "xapp-gtk3-module"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium snap, whilst browsing a website, I sometimes experience
  a browser hang activating a HTML select element. I'm running Ubuntu
  21.04 with the Ubuntu Unity package installed.

  I have the following output when I start the browser via the command
  line.

  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  Gtk-Message: 11:06:53.360: Failed to load module "xapp-gtk3-module"

  (chrome:34804): dbind-WARNING **: 11:06:53.486: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-BrZcGTnIin: No such 
file or directory
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [34912:34912:0604/110653.545090:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [34804:34897:0604/110738.564042:ERROR:gpu_process_host.cc(1002)] GPU process 
exited unexpectedly: exit_code=512
  si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
  [35415:35415:0604/110738.670097:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930863/+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 1918578] Re: Chromium Crashes When Triggering File Dialog

2021-06-04 Thread AlexB
Actually, I believe this is a different bug, so will open a separate
issue.

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

Title:
  Chromium Crashes When Triggering File Dialog

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've installed Chromium via Snap. Chromium seems to crash any time it
  triggers a native file dialog. This can be replicated by doing "Save
  file as", "Save image as" or simply doing CTRL+O to open a local web
  page.

  I've launched it from the terminal to see if it has any prints. Here's
  what I've got *before* the crash:

  ```plain
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so
  Gtk-Message: 08:07:49.139: Failed to load module "appmenu-gtk-module"

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: /snap/chromium/1514
  /gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-
  ibus.so: cannot open shared object file: No such file or directory

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: Loading IM context type
  'ibus' failed

  (chrome:6811): Gtk-WARNING **: 08:07:57.896: Could not load a pixbuf from 
icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  ```

  Here's what I've got *when* it crashed:

  ```plain
  Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/snap/chromium/1506/data-dir/icons/Adwaita/16x16/status/image-missing.png: 
Unable to load image-loading module: 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 cannot open shared object file: No such file or directory 
(gdk-pixbuf-error-quark, 5)
  Aborted (core dumped)
  ```

  What is the issue here? How can I resolve this?

  ***

  # Environment

   - Kubuntu 20.04.2
   - Chromium 89.0.4389.72 (Official Build) snap (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918578/+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 1918578] Re: Chromium Crashes When Triggering File Dialog

2021-06-04 Thread AlexB
I have uninstalled and reinstalled Chromium snap.

Running Chromium via the terminal gives 
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
Gtk-Message: 10:49:24.464: Failed to load module "xapp-gtk3-module"

(chrome:30543): dbind-WARNING **: 10:49:24.578: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-BrZcGTnIin: No such 
file or directory
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance 
counters)
[30654:30654:0604/104924.648476:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

I'm using Ubuntu 21.04 with the Unity desktop package.


** Changed in: chromium-browser (Ubuntu)
   Status: Expired => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Chromium Crashes When Triggering File Dialog

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've installed Chromium via Snap. Chromium seems to crash any time it
  triggers a native file dialog. This can be replicated by doing "Save
  file as", "Save image as" or simply doing CTRL+O to open a local web
  page.

  I've launched it from the terminal to see if it has any prints. Here's
  what I've got *before* the crash:

  ```plain
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so
  Gtk-Message: 08:07:49.139: Failed to load module "appmenu-gtk-module"

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: /snap/chromium/1514
  /gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-
  ibus.so: cannot open shared object file: No such file or directory

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: Loading IM context type
  'ibus' failed

  (chrome:6811): Gtk-WARNING **: 08:07:57.896: Could not load a pixbuf from 
icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  ```

  Here's what I've got *when* it crashed:

  ```plain
  Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/snap/chromium/1506/data-dir/icons/Adwaita/16x16/status/image-missing.png: 
Unable to load image-loading module: 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 cannot open shared object file: No such file or directory 
(gdk-pixbuf-error-quark, 5)
  Aborted (core dumped)
  ```

  What is the issue here? How can I resolve this?

  ***

  # Environment

   - Kubuntu 20.04.2
   - Chromium 89.0.4389.72 (Official Build) snap (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918578/+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 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5

2021-06-04 Thread Timo Aaltonen
Hello themusicgod1, or anyone else affected,

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

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

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

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

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

** Changed in: gjs (Ubuntu Hirsute)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  toggling down object GInotifyFileMonitor that's already queued to
  toggle up ... GNOME Shell crashed with signal 5

Status in gjs:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  Gnome shell crashes when unexpected references happens on other
  threads

  [ Test case ]

  Createa file called modify.py:

  #!/usr/bin/env python3

  import time
  import random

  while True:
  time.sleep(0.001)
  with open('/tmp/testfile', 'w') as f:
  f.write(str(random.random()))

  
  Create a file called crash-me.js:

  #!/usr/bin/gjs

  const {GLib, Gio} = imports.gi;
  const watchFile = Gio.file_new_for_path('/tmp/testfile');
  const fileMonitor = watchFile.monitor(Gio.FileMonitorFlags.NONE, null);
  fileMonitor.connect('changed', () => {});

  GLib.MainLoop.new(null, false).run();

  
  Open two terminals and run (in each):
  $ python3 modify.py
  $ gjs crash-me.js

  gjs should run for some minutes without crashing.

  [ Regression potential ]

  gjs may use memory or not free correctly created objects

  
  ---

  https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215

  ---

  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "

[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)

2021-06-04 Thread Timo Aaltonen
Hello fprietog, or anyone else affected,

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

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

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

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

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

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

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

Title:
  Gjs promises on Gio.File operations don't work anymore after upgrading
  libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)

Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Won't Fix
Status in gjs source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  As per glib commit
  https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
  Gio.File.new_for_path("") returns a GDummyFile implementation, while
  Gio._promisify relies on it being a LocalFile, so we don't promisify
  the right methods.

  [ Test case ]

  gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 
'delete_async', 'delete_finish');
 print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && 
echo GJS works

  Should write on terminal:

  [object Promise]
  GJS works

  In the bugged version would instead just:

  (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method 
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
  @:2:48

  (gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script 
  threw an exception

  
  [ Regression potential ]

  Gjs apps are slower in starting up, or not act properly when / is not
  a local location.

  ---

  
  Problem tested in two different environments:
  - Ubuntu 21.04 Beta amd64
  - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

  After upgrading these packages:

  libglib2.0-02.67.5-2 to 2.68.0-1
  libglib2.0-bin  2.67.5-2 to 2.68.0-1
  libglib2.0-data 2.67.5-2 to 2.68.0-1

  The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
  three dots (...) instead of the graphic expected. It's throwing error
  messages to the system journal every second or so (depends of the
  refresh interval selected in the app settings):

  abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
  multiload, Impossible to read image from path '/run/user/1026
  /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
  TypeError: method Gio.File.read_async: At least 3 arguments required,
  but only 2 passed

  Don't know if this is a documented change of that method and the bug
  should be open for the indicator-multiload app. Please, if that's the
  case just let me know to do it.

  Thanks and best reagrds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1927840] Re: [SRU] Update to 1.68.1

2021-06-04 Thread Timo Aaltonen
Hello Marco, or anyone else affected,

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

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

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

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

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

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

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  [SRU] Update to 1.68.1

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including many memory fixes
  https://gitlab.gnome.org/GNOME/gjs/commits/1.68.1

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working, as well other
  gjs based apps like polari or gnome-weather and maps

  [ Regression potential ]

  The way the objects are handled when (un)reffed from other threads or after 
(and during) disposition changed a lot, so it could both cause:
   1. Leaks (memory waste in fact) if objects are kept referenced by gjs and 
not released when nothing else
  need them
   2. New crashes or dead-locks when objects are (un)reffed from other threads

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1927840/+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 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)

2021-06-04 Thread Timo Aaltonen
Hello shine, or anyone else affected,

Accepted gnome-shell into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.4-1ubuntu3~21.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  gnome-shell-calendar-server assert failure on arm64: double free or
  corruption (fasttop)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell source package in Hirsute:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell-calendar-server crashes (and it seems to happen more in
  aarch64).

  https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
  https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1

  [ Test case ]

  There's not a clear test case, but this is relevant:
   - Configure a supported calendar in your online accounts 
   - GNOME shell should show your events in the calendar (under notifications 
panel)

  [ Regression potential ]

  gnome-shell-calendar-server may leak memory.

  
  ---

  M1 Mac mini
  Parallels Ubuntu VM

  ProblemType: CrashDistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic aarch64
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: arm64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 04:34:36 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
   b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
  InstallationDate: Installed on 2021-02-17 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
  ProcCmdline: /usr/libexec/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x81240c08 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=, p=0xe9eee300, have_lock=0) at 
malloc.c:4298
   g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell-calendar-server assert failure: double free or corruption 
(fasttop)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-04 Thread Timo Aaltonen
Hello Gipsz, or anyone else affected,

Accepted gnome-shell into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.4-1ubuntu3~21.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions

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


Re: [Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

2021-06-04 Thread Iain Lane
Yeah, I read the man page too, but it wasn't understandable to me. If 
you understand it more, could you prepare a change for upstream? I can't 
just paste those two entries there to them, that's not enough 
information.

Any hints on the second question about when wayland does start working, 
what prime support is supposed to do then?

On Fri, Jun 04, 2021 at 05:42:53AM -, Alberto Milone wrote:
> Here is the difference:
> 
> DRIVER
> Match the driver name of the event device. Only set this key for devices 
> which are bound to a driver at the time the event is generated.
> 
> DRIVERS
> Search the devpath upwards for a matching device driver name.
> 
> https://www.freedesktop.org/software/systemd/man/udev.html
> 
> 
> I assume the device is not always bound to the driver when the event is 
> generated.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1925238
> 
> Title:
>   [nvidia-prime] switches between xorg and wayland session
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [nvidia-prime] switches between xorg and wayland session

Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Impish:
  New

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too.

  Performance mode is selected in nvidia-settings, which is supposed to
  mean nvidia & therefore xorg but it's not working. Selecting it
  explicitly doesn't help either.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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 1929304] Re: file-roller / gnome archive manager fails to extract

2021-06-04 Thread Sebastien Bacher
Thanks, sounds like https://gitlab.gnome.org/GNOME/gnome-
autoar/-/commit/135053d5 which was just fixed in the new 0.3.3 version

** Package changed: file-roller (Ubuntu) => gnome-autoar (Ubuntu)

** Changed in: gnome-autoar (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: gnome-autoar (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  file-roller / gnome archive manager fails to extract

Status in gnome-autoar package in Ubuntu:
  Fix Committed

Bug description:
  problem occurs with :

  a) ubuntu 20.04.2 | gnome version 3.36.8 | X11

  b) fedora 34 | gnome 40.0.1 | wayland

  the latest version of gnome archive manager which is 3.36.3 fails to
  extract a .gz file which it used to do earlier.

  here are 2 links to 2 separate versions of hard disk sentinel linux
  version :

  1. https://www.hdsentinel.com/hdslin/hdsentinel-018c.gz

  2. https://www.hdsentinel.com/hdslin/hdsentinel-019c-x64.gz

  when i try to extract both the above mentioned files by right clicking
  & then extract here all i get is an empty folder with nothing
  extracted in it.

  if i open the gnome archive manager 3.36.3 from the applications menu
  & then try to extract the 1st file hard disk sentinel version 018c the
  extraction is successful.

  but if i open the gnome archive manager 3.36.3 from the applications
  menu & then try to extract the 2nd file hard disk sentinel version
  019c it only makes a copy of the .gz file.

  the earlier version of gnome archive manager which is default / built-in the 
ubuntu 20.04.2 iso
  did not have this problem it is only after the update that the gnome archive 
manager fails to perform.

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

2021-06-04 Thread Stransky
export DISPLAY=wayland-0 is not correct, it should be export DISPLAY=:0
or so (set to your active X11 display).

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

Title:
  Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I am running Weston/Wayland on Ubuntu 18.0.4.

  I am able to successfully start the display server:
  ```
  export XDG_RUNTIME_DIR=/run/weston
  weston --tty 1 &
  ```

  Next, I try to run firefox on it:

  ```
  export XDG_RUNTIME_DIR=/run/weston
  export GDK_BACKEND=wayland
  export MOZ_ENABLE_WAYLAND=1
  export DISPLAY=wayland-0
  export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
  export WAYLAND_DEBUG=1
  export WAYLAND_DISPLAY=wayland-0

  firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
  ```

  This outputs:

  ```
  [1446891.592]  -> wl_display@1.get_registry(new id wl_registry@2)
  [1446891.702]  -> wl_disp...@1.sync(new id wl_callback@3)
  [1446893.656] wl_display@1.delete_id(3)
  [1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
  [1446893.781]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id 
[unknown]@4)
  [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
  [1446893.889]  -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id 
[unknown]@5)
  [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
  [1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
  [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
  [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
  [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
  [1446894.109]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@6)
  [1446894.156] wl_registry@2.global(8, "wl_shm", 1)
  [1446894.190]  -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
  [1446894.429]  -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
  [1446894.974]  -> wl_shm_pool@8.resize(5568)
  [1446895.214]  -> wl_shm_pool@8.resize(12096)
  [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
  [1446895.315] wl_registry@2.global(10, "wl_seat", 5)
  [1446895.353]  -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
  [1446925.977]  -> wl_compositor@4.create_surface(new id wl_surface@10)
  [1446926.203]  -> wl_data_device_manager@6.get_data_device(new id 
wl_data_device@11, wl_seat@9)
  [1446926.370]  -> wl_compositor@4.create_surface(new id wl_surface@12)
  [1446926.636]  -> wl_disp...@1.sync(new id wl_callback@13)
  [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
  [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
  [1446926.906] wl_registry@2.global(13, "wl_output", 3)
  [1446926.965]  -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
  [1446927.172]  -> wl_disp...@1.sync(new id wl_callback@15)
  [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
  [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
  [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
  [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
  [1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
  [1446927.585] wl_registry@2.global(19, "wl_shell", 1)
  [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
  [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
  [1446927.777] wl_callb...@3.done(1)
  [1446929.537] wl_display@1.delete_id(13)
  [1446929.624] wl_display@1.delete_id(15)
  [1446929.656] wl_shm@7.format(0)
  [1446929.684] wl_shm@7.format(1)
  [1446929.709] wl_shm@7.format(909199186)
  [1446929.733] wl_shm@7.format(842093913)
  [1446929.758] wl_shm@7.format(842094158)
  [1446929.783] wl_shm@7.format(1448695129)
  [1446929.807] wl_seat@9.capabilities(2)
  [1446929.834]  -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
  [1446929.903] wl_s...@9.name("default")
  [1446929.931] wl_callb...@13.done(1)
  [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
  [1446930.094] wl_output@14.scale(1)
  [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
  [1446930.193] wl_out...@14.done()
  [1446930.245] wl_callb...@15.done(1)
  [1446930.278]  -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id 
[unknown]@15)
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) [GFX1-]: glxtest: EGL test failed
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) |[2][GFX1-]: No GP

[Desktop-packages] [Bug 1930485]

2021-06-04 Thread Jameson Williams
> export DISPLAY=wayland-0 is not correct, it should be export
DISPLAY=:0 or so (set to your active X11 display).

Hi Martin - thanks for the suggestion. I am trying to Firefox on
Weston/Wayland, so I don't have any X11 display.

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

Title:
  Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I am running Weston/Wayland on Ubuntu 18.0.4.

  I am able to successfully start the display server:
  ```
  export XDG_RUNTIME_DIR=/run/weston
  weston --tty 1 &
  ```

  Next, I try to run firefox on it:

  ```
  export XDG_RUNTIME_DIR=/run/weston
  export GDK_BACKEND=wayland
  export MOZ_ENABLE_WAYLAND=1
  export DISPLAY=wayland-0
  export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
  export WAYLAND_DEBUG=1
  export WAYLAND_DISPLAY=wayland-0

  firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
  ```

  This outputs:

  ```
  [1446891.592]  -> wl_display@1.get_registry(new id wl_registry@2)
  [1446891.702]  -> wl_disp...@1.sync(new id wl_callback@3)
  [1446893.656] wl_display@1.delete_id(3)
  [1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
  [1446893.781]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id 
[unknown]@4)
  [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
  [1446893.889]  -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id 
[unknown]@5)
  [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
  [1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
  [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
  [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
  [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
  [1446894.109]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@6)
  [1446894.156] wl_registry@2.global(8, "wl_shm", 1)
  [1446894.190]  -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
  [1446894.429]  -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
  [1446894.974]  -> wl_shm_pool@8.resize(5568)
  [1446895.214]  -> wl_shm_pool@8.resize(12096)
  [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
  [1446895.315] wl_registry@2.global(10, "wl_seat", 5)
  [1446895.353]  -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
  [1446925.977]  -> wl_compositor@4.create_surface(new id wl_surface@10)
  [1446926.203]  -> wl_data_device_manager@6.get_data_device(new id 
wl_data_device@11, wl_seat@9)
  [1446926.370]  -> wl_compositor@4.create_surface(new id wl_surface@12)
  [1446926.636]  -> wl_disp...@1.sync(new id wl_callback@13)
  [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
  [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
  [1446926.906] wl_registry@2.global(13, "wl_output", 3)
  [1446926.965]  -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
  [1446927.172]  -> wl_disp...@1.sync(new id wl_callback@15)
  [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
  [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
  [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
  [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
  [1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
  [1446927.585] wl_registry@2.global(19, "wl_shell", 1)
  [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
  [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
  [1446927.777] wl_callb...@3.done(1)
  [1446929.537] wl_display@1.delete_id(13)
  [1446929.624] wl_display@1.delete_id(15)
  [1446929.656] wl_shm@7.format(0)
  [1446929.684] wl_shm@7.format(1)
  [1446929.709] wl_shm@7.format(909199186)
  [1446929.733] wl_shm@7.format(842093913)
  [1446929.758] wl_shm@7.format(842094158)
  [1446929.783] wl_shm@7.format(1448695129)
  [1446929.807] wl_seat@9.capabilities(2)
  [1446929.834]  -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
  [1446929.903] wl_s...@9.name("default")
  [1446929.931] wl_callb...@13.done(1)
  [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
  [1446930.094] wl_output@14.scale(1)
  [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
  [1446930.193] wl_out...@14.done()
  [1446930.245] wl_callb...@15.done(1)
  [1446930.278]  -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id 
[unknown]@15)
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI 
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed 
(t=0.548476) [GFX1-]: glxtest: EGL test failed
  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxte