date:20191024

Here's the relevant bug on our tracker:
https://bugzilla.mozilla.org/show_bug.cgi?id=1590984

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

Title:
  WebRTC-related crashes

Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+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 1849615] [NEW] WebRTC-related crashes

Public bug reported:

In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
version of Firefox 69.0.x. All the crashes are happening in the WebRTC
code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-checking
safety is causing an abort. Is it possible that Firefox is being built
with a FD_SETSIZE value that's different from what's used in libc?

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

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

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

Title:
  WebRTC-related crashes

Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+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 1839620] Re: New upstream stable version 3.32.3

1:3.32.3-0ubuntu1 is working just fine in my testing

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

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

Title:
  New upstream stable version 3.32.3

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  That's a stable update in the GNOME 3.32 serie, the details of the changes 
are in 
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.2.news
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.3.news

  [ Test case ]

  That's a standard GNOME bugfix update and covered by
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the filemanager still work correctly, browse some
  locations, copy some files and directories, open the documents

  
  [ Regresison potential ]

  The update include several fixes, several of those are around the
  marking of favorites files/folders so check that feature works as
  expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839620/+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 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2019-10-24 Thread Daniel van Vugt

Yes disabling multi-stream transport makes it a single stream, hence it
can only then drive a single monitor.

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+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 1833431] Re: Update gnome-settings-daemon to 3.32.1

3.32.1-0ubuntu1 seems to be working without issue, marking as verified

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

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

Title:
  Update gnome-settings-daemon to 3.32.1

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Committed

Bug description:
  * Impact

  There is a new bugfix GNOME update available with some bugs fixed, details on 
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS

  * Test case

  Log into a Ubuntu/GNOME session and make sure that the session has the
  correct theme, that the screen resolution is correct, that the
  keybinding work as they should.

  * Regression potential

  The main changes are in the plugins to handle the monitor, night mode
  and multimedia keys, make sure those keep working

  The update is covered by the GNOME standing exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+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 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

2019-10-24 Thread Daniel van Vugt

** Summary changed:

- gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr() from 
meta_window_get_workspaces()
+ gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr() from 
meta_window_get_workspaces() [assertion failure "code should not be reached"]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #885
   https://gitlab.gnome.org/GNOME/mutter/issues/885

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/885
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

1:12.2-2ubuntu3.1 is working fine and not creating regressions, even if
the bug seems to not happen on every install which makes the fix harder
to verify the change is right on principle, marking as verified

** Tags removed: removal-candidate verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1823448] Re: cogl ftbfs in disco (i386 only)

The new version built on i386 and seems to have no functional
regression, marking as verified

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

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

Title:
  cogl ftbfs in disco (i386 only)

Status in cogl package in Ubuntu:
  Fix Released
Status in cogl source package in Disco:
  Fix Committed

Bug description:
  * Impact
  It fails to build on i386 (hanging in tests)

  * Test case
  The i386 build should work

  * Regression potential
  There is no change to the code, just test that GNOME and the video player 
(cogl users) still work correctly

  

  
  
https://launchpadlibrarian.net/417939758/buildlog_ubuntu-disco-i386.cogl_1.22.2-6_BUILDING.txt.gz

  make  check-local
  make[5]: Entering directory '/<>/tests'
  ( cd ./conform && make  test ) || exit $?
  make[6]: Entering directory '/<>/tests/conform'
  Key:
  ok = Test passed
  n/a = Driver is missing a feature required for the test
  FAIL = Unexpected failure
  FIXME = Test failed, but it was an expected failure
  PASS! = Unexpected pass

     Test  GL+FF GL+ARBFP GL+GLSL GL-NPT
  GL3ES2 ES2-NPT

   test_pipeline_user_matrix: ok   ok  ok ok ok 
ok  ok
  test_blend_strings: ok   ok  ok ok ok 
ok  ok
  test_blend: ok   ok  ok ok ok 
ok  ok
    test_premult:  FIXMEFIXME   FIXME  FIXME  FIXME  
FIXME   FIXME
   test_path: ok   ok  ok ok ok 
ok  ok
  test_path_clip: ok   ok  ok ok ok 
ok  ok
     test_depth_test: ok   ok  ok ok ok 
ok  ok
     test_color_mask: ok   ok  ok ok ok 
ok  ok
  make[6]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** Waiting for unfinished jobs
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** wait: No child processes.  Stop.
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs
  make[5]: *** [Makefile:875: test] Terminated
  make[2]: *** wait: No child processes.  Stop.
  E: Caught signal ‘Terminated’: terminating immediately
  make[4]: *** [Makefile:750: check-am] Terminated
  make: *** [debian/rules:7: build-arch] Terminated
  make[1]: [debian/rules:60: override_dh_auto_test] Terminated (ignored)
  Build killed with signal TERM after 150 minutes of inactivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1823448/+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 1849615] Re: WebRTC-related crashes

I did some further digging and this isn't a WebRTC-specific issue though
it tends to crash WebRTC code more often than other code.

See this for another similar crash in code we don't control (and which
might also be using select() and thus triggering the safety check):

https://crash-stats.mozilla.com/report/index/d347998e-6c60-4761-aece-
e7e8c0191023

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

Title:
  WebRTC-related crashes

Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+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 1849573] Re: No way to specify tls-version-min or tls-version-max, please include the config options in the GUI config panel.

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues #36
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/36

** Also affects: network-manager-openvpn via
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/36
   Importance: Unknown
   Status: Unknown

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

Title:
  No way to specify tls-version-min or tls-version-max, please include
  the config options in the GUI config panel.

Status in NetworkManager-OpenVPN:
  Unknown
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  The OpenVPN plugin for Network Manager does not have any mechanisms to
  interpret tls-version-{min,max} directives for OpenVPN.

  In Debian upstream, especially in Buster and Unstable, they disable
  TLS 1.0, 1.1, and 1.2 by default and use only TLS 1.3 by default.
  Therefore, with OpenVPN servers that only use TLS 1.2 or older, it is
  impossible to establish a tunnel to those locations *unless* you
  specify tls-version-{min,max} in the configurations.

  This can be done in OVPN files for OpenVPN directly, but there is
  currently no mechanism to do this in the GUI.

  This is tracked in Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=933177 as the original cause for TLS 1.3
  support, but if Ubuntu ever defaults OpenSSL to not have TLS 1.0-1.2
  support enabled by default, we will be out of luck.

  Upstream, GNOME has not yet merged a merge request which would add
  this option to the GUI: https://gitlab.gnome.org/GNOME/NetworkManager-
  openvpn/merge_requests/15

  Testing in Debian, the patch works against NetworkManager OpenVPN
  there.  I am currently testing these in Focal, Eoan, and Bionic to see
  if this is something we can possibly include at a future date to fix
  this issue long-term.

  In the interim, this tracks the request to get these features in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1849573/+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 1849615] Re: WebRTC-related crashes

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1590984
   Importance: Unknown
   Status: Unknown

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

Title:
  WebRTC-related crashes

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

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

Nevermind, this isn't WebRTC-specific and not even Ubuntu-specific since
I could find Debian instances of it. It's caused by select() being used
instead of more modern methods that don't have limits on the file
descriptor values you pass to them. Sorry for the noise.

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

Title:
  WebRTC-related crashes

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

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849615/+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 1849542] Re: Thunderbird empty after update to 19.10

2019-10-24 Thread Loïc Alejandro

I got it. See it attached.

** Attachment added: "faulty file"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+attachment/5299645/+files/global-messages-db.sqlite

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+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 1849615] Re: WebRTC-related crashes

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

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

Title:
  WebRTC-related crashes

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

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849615/+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 1849542] Re: Thunderbird empty after update to 19.10

2019-10-24 Thread Olivier Tilloy

Thanks Loïc. It's likely that this file contained private information,
so I downloaded a copy and deleted the attachment, to prevent ill-
intentioned people to use your data.

I'll try and reproduce the problem with this file.

** Attachment removed: "faulty file"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+attachment/5299645/+files/global-messages-db.sqlite

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => 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/1849542

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  New

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+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 1849573] Re: No way to specify tls-version-min or tls-version-max, please include the config options in the GUI config panel.

** Changed in: network-manager-openvpn
   Status: Unknown => New

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

Title:
  No way to specify tls-version-min or tls-version-max, please include
  the config options in the GUI config panel.

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  The OpenVPN plugin for Network Manager does not have any mechanisms to
  interpret tls-version-{min,max} directives for OpenVPN.

  In Debian upstream, especially in Buster and Unstable, they disable
  TLS 1.0, 1.1, and 1.2 by default and use only TLS 1.3 by default.
  Therefore, with OpenVPN servers that only use TLS 1.2 or older, it is
  impossible to establish a tunnel to those locations *unless* you
  specify tls-version-{min,max} in the configurations.

  This can be done in OVPN files for OpenVPN directly, but there is
  currently no mechanism to do this in the GUI.

  This is tracked in Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=933177 as the original cause for TLS 1.3
  support, but if Ubuntu ever defaults OpenSSL to not have TLS 1.0-1.2
  support enabled by default, we will be out of luck.

  Upstream, GNOME has not yet merged a merge request which would add
  this option to the GUI: https://gitlab.gnome.org/GNOME/NetworkManager-
  openvpn/merge_requests/15

  Testing in Debian, the patch works against NetworkManager OpenVPN
  there.  I am currently testing these in Focal, Eoan, and Bionic to see
  if this is something we can possibly include at a future date to fix
  this issue long-term.

  In the interim, this tracks the request to get these features in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1849573/+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 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

** Changed in: mutter
   Status: Unknown => New

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+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 1849559] Re: /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

That's coming from upstream/Debian, would be worth reporting to them
since that's probably not something we want to carry as an Ubuntu delta
right?

** Changed in: wpa (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

Status in wpa package in Ubuntu:
  New

Bug description:
  The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
  location. It is a system-wide default config for dbus, and as such
  probably should be in /usr/share/dbus-1/system.d instead; like most
  other DBus definitions installed on a typical system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1849559/+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 1848958] Re: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10

2019-10-24 Thread DRracer

Tried kernel 5.4-rc4
A very similar behavior, suspend takes 3 minutes to complete
After resume, the screen shows the KDE lock screen, but the mouse cursor is 
just a white box (I assume its bitmap was lost). 
The display is unresponsive, however the machine lives, I was able to ssh into 
it from another machine.
There are nouveau driver crashes in dmesg, see attachment.

I'll try kernel 5.0 if I can make it compile from within Kubuntu 19.10
to see if the suspend/resume problem changes.

** Attachment added: "2019-10-24_kernel_5.4-rc4.suspend-resume.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1848958/+attachment/5299662/+files/2019-10-24_kernel_5.4-rc4.suspend-resume.txt

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

Title:
  Suspend takes 3 minutes and screen is garbled after resume with
  nouveau driver after upgrade to 19.10

Status in Nouveau Xorg driver:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.

  After upgrading to 19.10 the machine now behaves weird:
  1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.

  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).

  3. Restarting the X-server resolves the issue, i.e. the screen
  contains reasonable content

  4. Text console is working correctly even without restarting the
  X-server

  5. Tried running KDE with and without compositor, got the same
  results.

  I'd like to help fixing this or at least provide technical info that
  will lead to fixing this issue, please tell me what shall I try/test.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Oct 20 23:18:53 2019
  DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M 
GS] [1462:7220]
  InstallationDate: Installed on 2019-04-21 (182 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Micro-Star International GT627
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago)
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1651IMS.10V
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1651
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: GT627
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver 1.000
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2019-10-24 Thread Solomon Nadar

I have the problem despite I tried to forget the network and tried
connecting again.

snadar@ThinkPad-T480:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

snadar@ThinkPad-T480:~$ cat /var/log/syslog
Oct 24 11:18:04 ThinkPad-T480 wpa_supplicant[1205]: wlp3s0: 
CTRL-EVENT-SCAN-STARTED
Oct 24 11:18:07 ThinkPad-T480 NetworkManager[1173]:   [1571908687.5057] 
audit: op="connection-delete" uuid="36692638-6bb6-4bc7-8425-849f3cb9ff70" 
name="apname" pid=5766 uid=1000 result="success"
Oct 24 11:18:16 ThinkPad-T480 wpa_supplicant[1205]: wlp3s0: 
CTRL-EVENT-SCAN-STARTED
Oct 24 11:19:04 ThinkPad-T480 wpa_supplicant[1205]: message repeated 3 times: [ 
wlp3s0: CTRL-EVENT-SCAN-STARTED]
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.3918] 
keyfile: add connection in-memory 
(660e7552-b847-4063-803c-6de6da411f0b,"apname")
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.3936] 
device (wlp3s0): disconnecting for new activation request.
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.3936] 
device (wlp3s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4074] 
settings-connection[0x55affb554360,660e7552-b847-4063-803c-6de6da411f0b]: 
write: successfully commited (keyfile: update 
/etc/NetworkManager/system-connections/apname 
(660e7552-b847-4063-803c-6de6da411f0b,"apname") and persist connection)
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4075] 
audit: op="connection-add-activate" uuid="660e7552-b847-4063-803c-6de6da411f0b" 
name="apname" pid=5766 uid=1000 result="success"
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4169] 
device (wlp3s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Withdrawing address record 
for fe80::5eb2:7428:835c:e20e on wlp3s0.
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Leaving mDNS multicast group 
on interface wlp3s0.IPv6 with address fe80::5eb2:7428:835c:e20e.
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Interface wlp3s0.IPv6 no 
longer relevant for mDNS.
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4505] 
dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 8389
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4505] 
dhcp4 (wlp3s0): state changed bound -> done
Oct 24 11:19:09 ThinkPad-T480 kernel: [ 3539.473650] wlp3s0: deauthenticating 
from a0:04:60:7c:6f:31 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 24 11:19:09 ThinkPad-T480 wpa_supplicant[1205]: wlp3s0: 
CTRL-EVENT-DISCONNECTED bssid=a0:04:60:7c:6f:31 reason=3 locally_generated=1
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Withdrawing address record 
for 192.168.44.148 on wlp3s0.
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Leaving mDNS multicast group 
on interface wlp3s0.IPv4 with address 192.168.44.148.
Oct 24 11:19:09 ThinkPad-T480 avahi-daemon[1120]: Interface wlp3s0.IPv4 no 
longer relevant for mDNS.
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4654] 
device (wlp3s0): Activation: starting connection 'apname' 
(660e7552-b847-4063-803c-6de6da411f0b)
Oct 24 11:19:09 ThinkPad-T480 dbus-daemon[1139]: [system] Activating via 
systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 
pid=1173 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 24 11:19:09 ThinkPad-T480 systemd[1]: Starting Network Manager Script 
Dispatcher Service...
Oct 24 11:19:09 ThinkPad-T480 wpa_supplicant[1205]: wlp3s0: 
CTRL-EVENT-SCAN-STARTED
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4701] 
sup-iface[0x55affb6bc0d0,wlp3s0]: connection disconnected (reason -3)
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4702] 
device (wlp3s0): supplicant interface state: completed -> disconnected
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4705] 
sup-iface[0x55affb6bc0d0,wlp3s0]: connection disconnected (reason -3)
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4720] 
device (wlp3s0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4728] 
device (wlp3s0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4730] 
device (wlp3s0): Activation: (wifi) access point 'apname' has security, but 
secrets are required.
Oct 24 11:19:09 ThinkPad-T480 NetworkManager[1173]:   [1571908749.4730] 
device (wlp3s0): state change: config -> need-auth (reason 'none', 
sys-iface-state: 'managed')
Oct 24 11:19:09 ThinkPad-T480 NetworkManager

[Desktop-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-10-24 Thread Hui Wang

Verification done on the Bionic, it fixed the problem.

On the lenovo P520, I installed OEM image (18.04), edit the 
/etc/apt/sources.list to add bionic-proposed repository, then run apt-get 
update abd sudo apt install pulseaudio, now the pulseaudio is:
ii pulseaudio 1:11.1-1ubuntu7.4 amd64 PulseAudio sound server
ii pulseaudio-utils 1:11.1-1ubuntu7.4 amd64 Command line tools for the 
PulseAudio sound server

recording: plug a mic into the front audio jack, and select it from
sound-setting, use arecord to record sound, after recording, unplug the
front mic and plug it to rear mic, use arecord to record sound again, it
still can record sound.

playback: plug a headphone to rear lineout and select lineout as output
device, then play sound via totem, after a while, close the totem and
unplug the rear lineout and plug the headphone to front headphone jack,
use totem to play sound, I can hear the sound from front headphone.


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

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1849615] Re: WebRTC-related crashes

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1590984.

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


On 2019-10-24T07:07:08+00:00 Gabriele Svelto wrote:

This bug is for crash report bp-abe63a7e-7862-4e4d-b2f7-313140191023.

```
Top 10 frames of crashing thread:

0 libc-2.27.so raise 
/build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51
1 libc-2.27.so abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:79
2 libc-2.27.so __libc_message 
/build/glibc-OTsEL5/glibc-2.27/libio/../sysdeps/posix/libc_fatal.c:181
3 libc-2.27.so __fortify_fail_abort 
/build/glibc-OTsEL5/glibc-2.27/debug/fortify_fail.c:33
4 libc-2.27.so __fortify_fail 
/build/glibc-OTsEL5/glibc-2.27/debug/fortify_fail.c:44
5 libc-2.27.so __chk_fail /build/glibc-OTsEL5/glibc-2.27/debug/chk_fail.c:28
6 libc-2.27.so __fdelt_chk /build/glibc-OTsEL5/glibc-2.27/debug/fdelt_chk.c:25
7 libxul.so webrtc::videocapturemodule::DeviceInfoLinux::EventCheck 
/build/firefox-WlAST4/firefox-69.0.2+build1/media/webrtc/trunk/webrtc/modules/video_capture/linux/device_info_linux.cc:92
8 libxul.so webrtc::videocapturemodule::DeviceInfoLinux::ProcessInotifyEvents 
/build/firefox-WlAST4/firefox-69.0.2+build1/media/webrtc/trunk/webrtc/modules/video_capture/linux/device_info_linux.cc:133
9 libxul.so webrtc::videocapturemodule::DeviceInfoLinux::InotifyProcess 
/build/firefox-WlAST4/firefox-69.0.2+build1/media/webrtc/trunk/webrtc/modules/video_capture/linux/device_info_linux.cc:166

```

This crash is happening in the Ubuntu-packaged version of Firefox. It
seems to affect 64-bit users only. I'll file a bug on Ubuntu's tracker
and link it here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/comments/0


On 2019-10-24T07:30:51+00:00 Gabriele Svelto wrote:

I filed a bug on Ubuntu's tracker. I've also dug a little bit further in
the crashes and this is not related to WebRTC per-se. The most visible
signatures are in WebRTC code but they're not the only ones. This is
caused by checks in libc that check if the file descriptor values passed
to the `FD_SET`, `FD_CLR` and `FD_ISSET` macros are less than the
`FD_SETSIZE` value. All code calling `select()` both directly and
indirectly seems to be affected. In WebRTC we're receiving file
descriptors from `inotify_init()`, is it possible that this will return
values larger than `FD_SETSIZE`?

Switching to `poll()` would probably fix the issue here but there's a
few things that are odd about this bug: for starters, why is it only
happening on Ubuntu/Debian and not on our builds? Also, this is
happening in code that calls `select()` outside of Firefox and those
crashes are also happening only on Ubuntu/Debian builds, not ours.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/comments/3


On 2019-10-24T08:13:44+00:00 Gabriele Svelto wrote:

I did some further digging and this is happening all over the place but
mostly in code we don't control. It's always `select()`'s fault though.
Daniel, this code is different from upstream WebRTC (which is also using
`select()` but in other places), is there a reason for this? I can cook
up a patch to switch this code to `poll()` instead but I wonder if it's
the right thing to do or if this should be fixed upstream first.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/comments/5


** Changed in: firefox
   Status: Unknown => Confirmed

** Changed in: firefox
   Importance: Unknown => Critical

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

Title:
  WebRTC-related crashes

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

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849615/+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 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

2019-10-24 Thread Taras Romaniv

+1
It is impossible to use WebStrom, as Gnome-Shell on Ubuntu 19.10 constantly 
crashes

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+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 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

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

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

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+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 1849105] Re: [snap] cannot pause video with bluetooth headset buttons any more (MPRIS denied by apparmor)

2019-10-24 Thread Marius Gedminas

I can confirm that the fix works with chromium snap 78.0.3904.70 (rev
909).

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

Title:
  [snap] cannot pause video with bluetooth headset buttons any more
  (MPRIS  denied by apparmor)

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 19.04 I could press the button on my Bluetooth headset and
  the YouTube video playing in my Chromium would pause/resume.  This no
  longer works in 19.10.  What happens instead is I get an OSD popup
  with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
  shell.

  I suspect the additional sandboxing of the snap package is the
  culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  Date: Mon Oct 21 15:04:13 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
   tmpfs  tmpfs  7,7G  122M  7,6G   2% /dev/shm
   /dev/nvme0n1p5 ext4   284G  208G   62G  78% /
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (130 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20Q0CTO1WW
  dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849105/+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 1849656] [NEW] Screen displays weird broken animation behavior when I unlock

2019-10-24 Thread Jonathan Kamens

Public bug reported:

I sat down at my computer this morning and unlocked the screen and saw
the behavior shown in the attached video. I waited a while and it never
stopped. I hit Alt-L to lock the screen again which worked, and then
unlocked it again, which worked.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 24 07:35:14 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (294 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-22 (1 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-04-12T15:17:59.097705

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


** Tags: amd64 apport-bug eoan

** Attachment added: "video of weird unlock behavior"
   
https://bugs.launchpad.net/bugs/1849656/+attachment/5299677/+files/screen-unlock.mpg

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

Title:
  Screen displays weird broken animation behavior when I unlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I sat down at my computer this morning and unlocked the screen and saw
  the behavior shown in the attached video. I waited a while and it
  never stopped. I hit Alt-L to lock the screen again which worked, and
  then unlocked it again, which worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 07:35:14 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-02 (294 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (1 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-04-12T15:17:59.097705

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849656/+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 1663679] Re: tracker-miner-fs assert failure: * Error in `/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 0x000055c09c7eab30 *

is that still an issue and if so could you describe how to trigger it?

** Changed in: tracker (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  tracker-miner-fs assert failure: *** Error in `/usr/lib/tracker
  /tracker-miner-fs': double free or corruption (out):
  0x55c09c7eab30 ***

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  When I boot the computer

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-miner-fs 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/tracker/tracker-miner-fs': double 
free or corruption (out): 0x55c09c7eab30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 10 18:36:26 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2014-12-30 (772 days ago)
  InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f561dd8c3a8 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f561dd8c4b8 "double free or corruption (out)", action=3) at malloc.c:5046
   _int_free (av=, p=, have_lock=) 
at malloc.c:3902
   __GI___libc_free (mem=) at malloc.c:2982
   g_pattern_match () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-miner-fs assert failure: *** Error in 
`/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 
0x55c09c7eab30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip epoptes fuse lpadmin mysql mythtv 
plugdev sambashare sudo vboxsf vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1663679/+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 1848958] Re: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10

2019-10-24 Thread DRracer

kernel 4.19.80
suspend perfect (takes no more than 10s), resume perfect, no graphical glitches.
I belive the nouveau problems are caused by the recent GPU shared memory 
changes (just skimmed through the latest changes)

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

Title:
  Suspend takes 3 minutes and screen is garbled after resume with
  nouveau driver after upgrade to 19.10

Status in Nouveau Xorg driver:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.

  After upgrading to 19.10 the machine now behaves weird:
  1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.

  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).

  3. Restarting the X-server resolves the issue, i.e. the screen
  contains reasonable content

  4. Text console is working correctly even without restarting the
  X-server

  5. Tried running KDE with and without compositor, got the same
  results.

  I'd like to help fixing this or at least provide technical info that
  will lead to fixing this issue, please tell me what shall I try/test.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Oct 20 23:18:53 2019
  DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M 
GS] [1462:7220]
  InstallationDate: Installed on 2019-04-21 (182 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Micro-Star International GT627
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago)
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1651IMS.10V
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1651
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: GT627
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver 1.000
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1848958/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

** Changed in: ibus
   Status: New => Fix Released

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1844853/+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 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

2019-10-24 Thread sonald

I don't know where to submit either, it's a pity. hope someone may merge
the fix.

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/";
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/";
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help";
  BUG_REPORT_URL="https://bugzilla.redhat.com/";
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy";
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1809737/+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 1769206] Re: In admin panel "Sharing - Screen Sharing". Dialog box, (bottom "Network" part of it) says there is "No networks selected for sharing". (Nothing to select) Server d

2019-10-24 Thread Swinder Pal Singh

Need help on same problem

My company admistrator manages the network and hence the wired connection shows 
up as unmanaged in NM ui.
Screen Sharing doesnot allow to enable as no network available in the list to 
select.

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

Title:
  In admin panel "Sharing - Screen Sharing". Dialog box, (bottom
  "Network" part of it) says there is "No networks selected for
  sharing".  (Nothing to select) Server don't detect actual working
  wired connections.

Status in gnome-control-center package in Ubuntu:
  Expired

Bug description:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.

  The Screen Sharing dialog box, (bottom "Network" part of it) says
  there is "No networks selected for sharing".  It should at least show
  "Wired Connection 1", as in fact the wired connection is working
  perfectly (the box has internet connection in and out, and I am able
  to connect to it using ssh).

  As the sharing dialog does not show any available networks to pick
  from, it is not possible to activate the sharing.

  Another problem indicator is that the desktop systray network icon
  does not show up, even if the box is connected to fully working wired
  ethernet connection, and internet is working in and out of the
  machine.

  Also, in admin panel "Network" configuration dialog, there is no
  visible config area for "Wired Connections".  It appear as the
  computer has no network cards at all, only the VPN and Proxy settings
  are visible.

  *

  Possible related problem with drivers: I tried 'ubuntu-drivers devices' in 
order to find correct drivers for my graphic card.  The output from the command 
was simply nothing at all, it just reverted to the empty clean command prompt.
  root@mybox:~# ubuntu-drivers devices
  root@mybox:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May  4 18:18:02 2018
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-04-29 (4 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.199 metric 100 
   192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.199 
   192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.199 metric 100
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   enp4s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   enp5s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1769206/+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 1849666] [NEW] can not see hdmi

2019-10-24 Thread emre

Public bug reported:

i can not see hdmi, and i don't know why?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 24 15:27:11 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:39fe]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39fe]
InstallationDate: Installed on 2019-10-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 145f:01e7 Trust 
 Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81FV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=6747b4a8-5274-45de-a7f5-f774e2c086d9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8JCN48WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R33126 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Legion Y530-15ICH
dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN48WW:bd11/02/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R33126WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
dmi.product.family: Legion Y530-15ICH
dmi.product.name: 81FV
dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
dmi.product.version: Lenovo Legion Y530-15ICH
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100+git1910210630.c69c9c~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910240730.196165~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910240730.196165~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.1.0+git1910151930.b9bd80~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1910071930.bff5ec~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 
third-party-packages 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/1849666

Title:
  can not see hdmi

Status in xorg package in Ubuntu:
  New

Bug description:
  i can not see hdmi, and i don't know why?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 15:27:11 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39fe]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39fe]
  InstallationDate: Installed on 2019-10-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 145f:01e7 Trust 
   Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=6747b4a8-5274-45de-a7f5-f774e2c086d9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2018
  dmi.bios.vendor: LENOVO
  d

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

2019-10-24 Thread Neil Hanlon

Happy to try and make this happen.. I believe I can make it happen
pretty reliably on my system. Perhaps I can do something while profiling
gnome?

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  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.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+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 996012] Re: [Upstream] Cannot resize inserted formula in Impress via mouse

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

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

Title:
  [Upstream] Cannot resize inserted formula in Impress via mouse

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2)  apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in a blank Impress file is if one adds a
  formula via Insert -> Object -> Formula, one may resize the formula
  window.

  4) What happens instead is the formula is not resizable via clicking
  and dragging the edges of the formula.

  WORKAROUND: Secondary click the formula -> Position and Size... ->
  under Protect uncheck checkbox Size -> under Size choose the desired
  Width and Height.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-impress 1:3.5.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Mon May  7 17:44:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120417)
  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/996012/+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 1412448] Re: [upstream] Calc wrap text setting in Cell Formatting not persisted

** Summary changed:

- Calc wrap text setting in Cell Formatting not persisted
+ [upstream] Calc wrap text setting in Cell Formatting not persisted

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

Title:
  [upstream] Calc wrap text setting in Cell Formatting not persisted

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

Bug description:
  * Reporting this bug in this tracker tagged with PPA following this
  note: https://lists.launchpad.net/libreoffice/msg00072.html *

  When editing an XLS in Libreoffice Calc, the wrap text automatically
  setting in the cell formatting is not persisted across saves. Attached
  is a test spreadsheet with a long string of text in cell A1.

  Steps to reproduce:
  1) Right click cell and go to Format Cells
  2) Select Alignment tab
  3) Unselect Wrap Text Automatically
  4) Press OK
  5) Save spreadsheet selecting to keep the XLS format if asked
  6) Close spreadsheet
  7) Reopen spreadsheet

  Expected Result:
  When the spreadsheet is reopened cell A1 has remembered that the text is NOT 
to be wrapped.

  Actual Result:
  Cell A1 is once again wrapped

  lsb_release -rd:
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04

  apt-cache policy libreoffice-calc:
  libreoffice-calc:
Installed: 1:4.3.5~rc2-0ubuntu1~precise1
Candidate: 1:4.3.5~rc2-0ubuntu1~precise1
Version table:
   *** 1:4.3.5~rc2-0ubuntu1~precise1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ precise/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.5.7-0ubuntu7 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
   1:3.5.2-2ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1412448/+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 424044] Re: [Upstream] Math Object formula changed causing resize saving .odt to .doc

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

** Changed in: df-libreoffice
   Importance: Low => Unknown

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

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #40187 => Document Foundation 
Bugzilla #45284

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

Title:
  [Upstream] Math Object formula changed causing resize saving .odt to
  .doc

Status in LibreOffice:
  Unknown
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Incomplete
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org-writer

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/+attachment/2287815/+files/example.odt
  && lowriter -nologo example.odt

  save to .doc and open the .doc it looks the same as the .odt.

  4) What happens instead is the embedded Math equation is resized. The
  Math equation changes from:

  size 21{ Prod cSub { size 14{ ital "k="1} } cSup { size 14{N} } {p rSub {size 
14 {k}
  }^{size 14 n_{size 10 k} } } }

  in the .odt to:

  size 12{ Prod cSub { size 8{ ital "k="1} } cSup { size 8{N} } {p rSub
  { size 8{k} } rSup { size 8{n rSub {k} } } } } {}

  in .doc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/424044/+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 384553] Re: [Upstream] Text color changed to black importing Office 2007 PPTX

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

** Changed in: df-libreoffice
   Importance: Low => Unknown

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

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #37310 => Document Foundation 
Bugzilla #72567

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

Title:
  [Upstream] Text color changed to black importing Office 2007 PPTX

Status in LibreOffice:
  Unknown
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Incomplete
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org-impress

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/+attachment/602148/+files/MDOP.pptx
  && lowriter -nologo MDOP.pptx

  is that slide 54 text color looks as it does in the MS Office 2007
  screenshot:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/+attachment/2303006/+files
  /libre-office%20bug%20384553.tar.bz2 -O ex.tar.bz2 && file-roller -h
  ex.tar.bz && cd vista && eog page54.jpg

  4) What happened instead is the text is changed to black.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:3.0.1-9ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR@euro
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/384553/+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 575143] Re: [Upstream] Sheet bar self-resizes erroneously upon window resize

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

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

Title:
  [Upstream] Sheet bar self-resizes erroneously upon window resize

Status in LibreOffice:
  Invalid
Status in gnumeric package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Invalid
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description:Ubuntu Natty (development branch)
  Release:11.04

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

  3) What is expected to happen at the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/575143/+attachment/1373092/+files
  /empty-sheet.xls && localc -nologo empty-sheet.xls

  Notice how one can see Sheet 1 and part of the rest of the Sheets bar.
  Resize the window so it is as small as possible horizontally. Then re-
  size the window to almost full screen. The Sheets bar should display
  Sheet 1 and part of the rest of the Sheets bar as before.

  4) What happened instead is Sheet 1 and the rest of the bar
  disappeared, requiring one to slide the Sheets bar over.

  WORKAROUND: This problem does not occur in Gnumeric.

  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  apt-cache policy gnumeric
  gnumeric:
Installed: 1.10.13-1ubuntu1
Candidate: 1.10.13-1ubuntu1
Version table:
   *** 1.10.13-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org-calc 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue May  4 16:54:21 2010
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en
   PATH=(custom, user)
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/575143/+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 462564] Re: [Upstream] Deleting a column in Writer deletes whole table

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

** Changed in: df-libreoffice
   Importance: Wishlist => Unknown

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

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #48704 => Document Foundation 
Bugzilla #46733

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

Title:
  [Upstream] Deleting a column in Writer deletes whole table

Status in LibreOffice:
  Unknown
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Incomplete
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1)  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

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

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

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt
  && lowriter -nologo test.odt

  is when one highlights the second column of the table -> secondary
  clicks -> Column -> Delete is only that column is deleted. Please see
  movie for more details:
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv

  4) What happens instead is the whole table is deleted.

  Reproducible in:
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Split the table then delete the column.

  WORKAROUND: Use Word via WINE.

  Microsoft Office Word 2003 (11.5604.6505)

  apt-cache policy wine1.3
  wine1.3:
    Installed: 1.3.28-0ubuntu1~ppa1~natty1
    Candidate: 1.3.28-0ubuntu1~ppa1~natty1
    Version table:
   *** 1.3.28-0ubuntu1~ppa1~natty1 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.3.15-0ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Oct 28 09:43:20 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/462564/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

2019-10-24 Thread Gunnar Hjalmarsson

** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1831
   https://gitlab.gnome.org/GNOME/glib/issues/1831

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/issues/1831
   Importance: Unknown
   Status: Unknown

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Unknown
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 902344] Re: [Upstream] Headless soffice failure condition

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

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

Title:
  [Upstream] Headless soffice failure condition

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

Bug description:
  Command line executed:
  "/usr/lib/libreoffice/program/soffice.bin" 
"-accept=socket,host=127.0.0.1,port=2003,tcpNoDelay=1;urp;" 
"-env:UserInstallation=file:///tmp/.jodconverter_socket_host-127.0.0.1_port-2003"
 "-headless" "-nocrashreport" "-nodefault" "-nofirststartwizard" "-nolockcheck" 
"-nologo" "-norestore"

  This will return on the first run. The soffice process doesn't stick around.
  This will work on subsequent runs (process doesn't return).
  If the "env:UserInstallation" 
(/tmp/.jodconverter_socket_host-127.0.0.1_port-2003) directory is removed, it 
will fail again at the next execution.

  A LibreOffice 3.4 package on Windows doesn't show the same behaviour
  (works every time), though it may not be the same build of LibreOffice
  3.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Dec  9 22:01:41 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100323)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-05-16 (207 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/902344/+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 1769206] Re: In admin panel "Sharing - Screen Sharing". Dialog box, (bottom "Network" part of it) says there is "No networks selected for sharing". (Nothing to select) Server d

2019-10-24 Thread Swinder Pal Singh

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  In admin panel "Sharing - Screen Sharing". Dialog box, (bottom
  "Network" part of it) says there is "No networks selected for
  sharing".  (Nothing to select) Server don't detect actual working
  wired connections.

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

Bug description:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.

  The Screen Sharing dialog box, (bottom "Network" part of it) says
  there is "No networks selected for sharing".  It should at least show
  "Wired Connection 1", as in fact the wired connection is working
  perfectly (the box has internet connection in and out, and I am able
  to connect to it using ssh).

  As the sharing dialog does not show any available networks to pick
  from, it is not possible to activate the sharing.

  Another problem indicator is that the desktop systray network icon
  does not show up, even if the box is connected to fully working wired
  ethernet connection, and internet is working in and out of the
  machine.

  Also, in admin panel "Network" configuration dialog, there is no
  visible config area for "Wired Connections".  It appear as the
  computer has no network cards at all, only the VPN and Proxy settings
  are visible.

  *

  Possible related problem with drivers: I tried 'ubuntu-drivers devices' in 
order to find correct drivers for my graphic card.  The output from the command 
was simply nothing at all, it just reverted to the empty clean command prompt.
  root@mybox:~# ubuntu-drivers devices
  root@mybox:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May  4 18:18:02 2018
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-04-29 (4 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.199 metric 100 
   192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.199 
   192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.199 metric 100
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   enp4s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   enp5s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1769206/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init

2019-10-24 Thread Olivier Tilloy

Fix committed again (https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=e4093977f925511becd71b44e992e2d936ea59ba) now that the
request for auto-connection has been granted.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [snap] wrapper script doesn't source ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported here: https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/82)

  The /usr/bin/chromium-browser script in the old deb packages had the
  following line:

  test -f ~/.chromium-browser.init && . ~/.chromium-browser.init

  which allowed users to customize CHROMIUM_FLAGS. This was lost when
  transitioning to the snap. For compatibility, it should be added back,
  so that users who rely on this don't observe regressions when
  transitioning to the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1839620] Re: New upstream stable version 3.32.3

This bug was fixed in the package nautilus - 1:3.32.3-0ubuntu1

---
nautilus (1:3.32.3-0ubuntu1) disco; urgency=medium

  * New upstream version (lp: #1839620)

 -- Sebastien Bacher   Fri, 09 Aug 2019 15:37:02
+0200

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

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

Title:
  New upstream stable version 3.32.3

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  That's a stable update in the GNOME 3.32 serie, the details of the changes 
are in 
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.2.news
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.3.news

  [ Test case ]

  That's a standard GNOME bugfix update and covered by
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the filemanager still work correctly, browse some
  locations, copy some files and directories, open the documents

  
  [ Regresison potential ]

  The update include several fixes, several of those are around the
  marking of favorites files/folders so check that feature works as
  expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839620/+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 1839620] Update Released

The verification of the Stable Release Update for nautilus has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New upstream stable version 3.32.3

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  That's a stable update in the GNOME 3.32 serie, the details of the changes 
are in 
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.2.news
  https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.3.news

  [ Test case ]

  That's a standard GNOME bugfix update and covered by
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the filemanager still work correctly, browse some
  locations, copy some files and directories, open the documents

  
  [ Regresison potential ]

  The update include several fixes, several of those are around the
  marking of favorites files/folders so check that feature works as
  expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839620/+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 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

2019-10-24 Thread Gunnar Hjalmarsson

On 2019-10-24 07:50, Steve Langasek wrote:
> On Thu, Oct 24, 2019 at 12:06:38AM -, Gunnar Hjalmarsson wrote:
>> wondering if that line shouldn't rather read something like this:
>> 
>> : "☭"   # HAMMER AND SICKLE
>> 
>> (which works with IBus provided that there is a defined compose key)
> 
> Sure, this is a valid alternative, and just replacing the <\> with
>  is enough to unbreak my Delete key.  (I don't care about
> whether it causes the compose sequence to work,

Please.. Whether it works in some case is reasonably relevant.

If I open gedit from terminal, I get these complaints:

(org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.241: Could not get code
point of keysym \

(org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.242: Could not get code
point of keysym )

(org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.242: compose file
/home/gunnar/.XCompose does not include any keys besides keys in en-us
compose file

So Gtk does not understand it, and - needless to say - it doesn't work.

If I replace <\> with  and <)> with , Gtk stops
complaining and it works, kind of. I.e. pressing \ followed by ) gives
me ☭. But then I can't use my \ key for anything else, so this kind of
composing is pretty useless without including  too.

My observations are true both with and without IBus. IBus provides the
extra 'feature' with involving the Delete key, though.

> IBus does not define the syntax of .XCompose,

Right. Probably Gtk or libx11 does.

> It is not for ibus to retroactively declare the file to be
> "syntactically incorrect";

I suppose you don't know if it worked in 19.04. I guess it did not, and
then the file has been incorrect for a long time.

> and regardless, if it has decided that the file is syntactically
> incorrect, this should not result in changes to the behavior of an
> unrelated key.

Ok.. Do you plan to submit an upstream issue?

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu3.1

---
pulseaudio (1:12.2-2ubuntu3.1) disco; urgency=medium

  * debian/patches/0006-load-module-x11-bell.patch:
- remove that old distro patch, it's undocumented, not needed since
  GNOME handles the login sound by itself and create issues in some
  cases (duplicate sound, not respecting the UI choice)
  (lp: #1827842)

  [ Hui Wang ]
  * d/p/0800-stream-restore-Don-t-restore-if-the-active_port-is-P.patch:
- Don't restore the streams to sinks/sources with only unavailable ports
  (LP: #1834138)

 -- Sebastien Bacher   Fri, 28 Jun 2019 11:45:10
+0200

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

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1833431] Re: Update gnome-settings-daemon to 3.32.1

This bug was fixed in the package gnome-settings-daemon -
3.32.1-0ubuntu1

---
gnome-settings-daemon (3.32.1-0ubuntu1) disco; urgency=medium

  * New upstream version (lp: #1833431)
Media-keys:
- Fix MPRIS issues with disconnecting clients (lp: #1832374)

 -- Sebastien Bacher   Thu, 20 Jun 2019 10:29:50
+0200

** Changed in: gnome-settings-daemon (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-settings-daemon to 3.32.1

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Released

Bug description:
  * Impact

  There is a new bugfix GNOME update available with some bugs fixed, details on 
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS

  * Test case

  Log into a Ubuntu/GNOME session and make sure that the session has the
  correct theme, that the screen resolution is correct, that the
  keybinding work as they should.

  * Regression potential

  The main changes are in the plugins to handle the monitor, night mode
  and multimedia keys, make sure those keep working

  The update is covered by the GNOME standing exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+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 1834138] Update Released

The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1833431] Update Released

The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-settings-daemon to 3.32.1

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Released

Bug description:
  * Impact

  There is a new bugfix GNOME update available with some bugs fixed, details on 
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS

  * Test case

  Log into a Ubuntu/GNOME session and make sure that the session has the
  correct theme, that the screen resolution is correct, that the
  keybinding work as they should.

  * Regression potential

  The main changes are in the plugins to handle the monitor, night mode
  and multimedia keys, make sure those keep working

  The update is covered by the GNOME standing exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu3.1

---
pulseaudio (1:12.2-2ubuntu3.1) disco; urgency=medium

  * debian/patches/0006-load-module-x11-bell.patch:
- remove that old distro patch, it's undocumented, not needed since
  GNOME handles the login sound by itself and create issues in some
  cases (duplicate sound, not respecting the UI choice)
  (lp: #1827842)

  [ Hui Wang ]
  * d/p/0800-stream-restore-Don-t-restore-if-the-active_port-is-P.patch:
- Don't restore the streams to sinks/sources with only unavailable ports
  (LP: #1834138)

 -- Sebastien Bacher   Fri, 28 Jun 2019 11:45:10
+0200

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

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1827842] Update Released

The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1832374] Update Released

The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Media keys stop working due to missing service file

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Released

Bug description:
  * Impact 
  Sometime multimedia keys stop working

  * Test case
  - start playing an audio file in VLC/totem/smplayer
  - pause
  - open a video in another player
  - exit the other player
  - try to resume the music play from the first one using the play key

  -> it should work

  * Regression potential
  Make sure that multimedia play/pause keys keep working

  --

  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages
  still get logged. Closing SMPlayer again does not restore media keys
  so that Clementine can handle them. I had SMPlayer running ~17 hours
  ago.

  Doing a shell reload doesn't seem to fix this either.

  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.

  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320

  If you need any other information let me know.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-settings-daemon 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 11 17:36:07 2019
  InstallationDate: Installed on 2019-02-01 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20181202)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

Yeah, I guess this will have to do it for the verification. Please be
sure to re-open the bug in case someone reports the issue as not being
fixed in the end.

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1832374] Re: Media keys stop working due to missing service file

This bug was fixed in the package gnome-settings-daemon -
3.32.1-0ubuntu1

---
gnome-settings-daemon (3.32.1-0ubuntu1) disco; urgency=medium

  * New upstream version (lp: #1833431)
Media-keys:
- Fix MPRIS issues with disconnecting clients (lp: #1832374)

 -- Sebastien Bacher   Thu, 20 Jun 2019 10:29:50
+0200

** Changed in: gnome-settings-daemon (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Media keys stop working due to missing service file

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Released

Bug description:
  * Impact 
  Sometime multimedia keys stop working

  * Test case
  - start playing an audio file in VLC/totem/smplayer
  - pause
  - open a video in another player
  - exit the other player
  - try to resume the music play from the first one using the play key

  -> it should work

  * Regression potential
  Make sure that multimedia play/pause keys keep working

  --

  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages
  still get logged. Closing SMPlayer again does not restore media keys
  so that Clementine can handle them. I had SMPlayer running ~17 hours
  ago.

  Doing a shell reload doesn't seem to fix this either.

  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.

  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320

  If you need any other information let me know.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-settings-daemon 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 11 17:36:07 2019
  InstallationDate: Installed on 2019-02-01 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20181202)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

2019-10-24 Thread Meghdad

Is this the issue because of which chromium apps' shortcuts launch
chromium and show its icon as indicator instead of the pinned app's
icon?

If so, this issue still is not fixed in Ubuntu 19.10.

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1849484] Re: ultra-wide monitor recognized properly when plugged in only intermittently

2019-10-24 Thread Jonathan Kamens

The problem does not appear to happen under Wayland.

I am attaching a zip file containing four sets of the output of the
commands you requested spanning the time from before I plugged in the
HDMI cable to afterward, waiting long enough to confirm that I was
getting black screens rather than the correct behavior after plugging in
the cable.

To minimize the content of the zip, I've edited the journal.txt files in
all of the sets after the first to remove the logs that were in the
previous journal.txt, so if you append all four journal.txt files you
will get a complete, consecutive journal.


** Attachment added: "zip file containing logs"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849484/+attachment/5299735/+files/logs.zip

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

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

Title:
  ultra-wide monitor recognized properly when plugged in only
  intermittently

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849484/+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 462564] Re: [Upstream] Deleting a column in Writer deletes whole table

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

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


On 2012-02-28T10:13:25+00:00 Uls6502 wrote:

Created attachment 57775
A demonstration of the intended, and actual, behavior.

Steps to reproduce:

1) Create a table.

2) Merge some of the cells together so that the merged area is more than
one column wide.

3) Select a different row in one of such columns.

4) Try to delete this column.

Intended behavior:

The only column deleted is the one actually chosen, like in LibreOffice Calc. 
The merged cell is intact, only combining one column less.
The only way to delete the merged cell is to have the merged cell itself 
selected(alternately: or the column the merged cell is originally from).

Actual behavior:

All the columns the merged cell combines are deleted, even if the
selected cell is in a different row.

Tested on two different installations of LibreOffice 3.5.0 on Debian
Squeeze amd64 and Ubuntu 10.04 LTS amd64.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/9


On 2012-04-20T12:30:20+00:00 Jmrecarey wrote:

[Reproducible] with "LibreOffice 3.3.4 - Ubuntu 11.04 (32bit) Spanish
UI"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/14


On 2012-05-24T05:35:15+00:00 Sasha-libreoffice wrote:

reproduced also in 3.5.2 on Windows 7 32 bit
Changing version to 3.3.4 as most early reproducible, due to comment 2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/15


On 2012-09-24T06:25:20+00:00 sphericalhorse wrote:

Created attachment 67608
Table example

Now I've reproduced this bug in LibreOffice 3.5.4.2 on Ubuntu 12.04 x64
and LibreOffice 3.6.1.2 on Archlinux x64.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/16


On 2012-09-24T07:26:01+00:00 sphericalhorse wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/18


On 2012-09-24T15:10:42+00:00 Christopher M. Penalver wrote:

Changing Version: 3.3.3 due to downstream report
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564 .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/462564/comments/19


On 2015-04-01T14:39:57+00:00 Qa-admin-q wrote:

** Please read this message in its entirety before responding **

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 on a currently supported version of 
LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes the version of 
LibreOffice and your operating system, and any changes you see in the bug 
behavior
 
   *If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a short comment that includes your version of 
LibreOffice and Operating System

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)

http://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

[Desktop-packages] [Bug 384553] Re: [Upstream] Text color changed to black importing Office 2007 PPTX

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

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

On 2013-12-10T14:33:07+00:00 Marcos Paulo de Souza wrote:

Created attachment 90582
pptx test file

Problem description:

Steps to reproduce:
1.  Open the attached file
2. 
3. 

Current behavior: First title don't have the yellow gradient, just a
white text

Expected behavior: First title with yellow gradient

Operating System: Linux (Other)
Version: 4.3.0.0.alpha0+ Master

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/26

On 2013-12-10T14:36:32+00:00 Marcos Paulo de Souza wrote:

Created attachment 90583
Image from PowerPoint 2013 importing the file

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/27

On 2013-12-10T14:45:30+00:00 Marcos Paulo de Souza wrote:

Created attachment 90585
Image of LibreOffice 4.3 importing this file

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/28

On 2013-12-21T02:25:28+00:00 Jmadero-dev wrote:

Thank you for reporting this issue! I have been able to confirm the issue on:
Version: 4.3.0.0.alpha0+Build ID: daa57a101a20e0b37db7090796ad002b8d192b9b
 Date:   Sun Dec 15 23:07:57 2013 +0100
Platform: Ubuntu Linux 13.04

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
As I've been able to confirm this problem I am marking as:

New (confirmed)
Major - data loss or at least import problem that looks like data loss for our 
end users
High - quite a common feature, slideshows generated in any newer release of MSO 
with a gradient for text is going to see this issue.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LibreOffice is powered by a team of volunteers, every bug is confirmed 
(triaged) by human beings who mostly give their time for free. We invite you to 
join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage and join us on freenode at 
#libreoffice-qa

There are also other ways to get involved including with marketing, UX,
documentation, and of course developing -  http://www.libreoffice.org
/get-help/mailing-lists/.

Lastly, good bug reports help tremendously in making the process go
smoother, please always provide reproducible steps (even if it seems
easy) and attach any and all relevant material

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/31

On 2013-12-21T02:26:27+00:00 Jmadero-dev wrote:

Updating version - at least presentsince 4.1.3.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/32

On 2014-01-13T14:25:03+00:00 Marcos Paulo de Souza wrote:

Hi guys,

I'm interested in working in this bug.

I know we need to understand how OOXML handles this, but there is some
documents and code pointers where we can touch this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/33

On 2014-01-13T15:23:56+00:00 Geoffrey De Belie wrote:

(In reply to comment #5)
> Hi guys,
> 
> I'm interested in working in this bug.
> 
> I know we need to understand how OOXML handles this, but there is some
> documents and code pointers where we can touch this?

Hi, you might find this useful: http://www.osb-
alliance.de/fileadmin/Working_Groups/OfficeInteroperability/Project1
/suse-ooxml-tender-use-case-5.1-report.pdf

Or this:
http://www.officeopenxml.com/prSlide-background.php
http://officeopenxml.com/drwSp-PattFill.php
http://www.officeopenxml.com/prSlideMaster.php

I also uploaded another pptx test file with transparent background,
which is still not detected by LibreOffice.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/34

On 2014-01-13T15:27:10+00:00 Geoffrey De Belie wrote:

Created attachment 91955
PPTX test file 2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/comments/35

On 2014-06-19T10:49:24+00:00 Barta-c wrote:

(In reply to comment #4)
> Updating version - at l

[Desktop-packages] [Bug 424044] Re: [Upstream] Math Object formula changed causing resize saving .odt to .doc

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

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


On 2012-01-26T12:41:06+00:00 Yury wrote:

Created attachment 56202
remove appending of the hard-coded font sizes (made against git checkout)

This is about formulas in writer file which is being exported (saved as)
microsoft word .doc file.

The current conversion routines in starmath/ subdir append hard-coded
font sizes ("size 12" to normal content, "size 8" to super- and
subscripts etc.), regardless of what is set in LibreOffice formula
editor's settings. That is, of course, completely wrong approach. This
way formulas are, in fact, corrupted. There are many tickets for this
issue filed in OOO bugzilla, by the way.

One way of correcting this is proposed in a patch attached, pending the
implementation of "completely correct" way of exporting font sizes in
formulas to .doc (in ole streams attributes). This patch just removes
the code which adds "size %d {" and corresponding "}".

"Works for me", as now I'm able to export many-formulas document to
word's .doc and not have to *edit* each and every of those, if something
other than "size 12" is required (I still have to double-click each and
every of those to correct the previews, but that's another problem,
albeit related).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/19


On 2012-02-17T07:55:23+00:00 Sasha-libreoffice wrote:

@ Michael
Please, take look at this bug. Appears that it contains ready patch for fixing 
this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/20


On 2012-02-29T01:23:25+00:00 Sasha-libreoffice wrote:

@ Ivan
Please, take look at this bug. Appears that it contains ready patch for fixing
this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/21


On 2012-02-29T02:13:01+00:00 Michael-stahl wrote:

sounds plausible, but i know ~nothing about WW8;
Caolan, Cedric, Lubos: please take a look at the patch here

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/22


On 2012-02-29T04:06:51+00:00 Caolanm wrote:

seeing as this is a patch to the import, I guess the problem is a round
trip from .doc back to .doc again ?

Can you attach a demo document which shows the problem that this fixes.
Its been a very long time since I played with the MathType format.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/23


On 2012-02-29T07:16:37+00:00 Timofeev-i-s wrote:

Heh, since I am in the CC list... :)
The patch looks a bit weird to me: it removes the support of the SIZE record of 
the MTEF. However, MTEF is the format I am not familiar with, I have just 
downloaded the specification and looking into it right now. :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/24


On 2012-02-29T10:38:29+00:00 Yury wrote:

I'll attach a prepared and re-tested example tomorrow.

And, like I said before, this patch is not a real solution, but a
kludge, really.

As I don't understand the starmath module too well myself, I've just
removed ("hacked off") a provision for inserting the "size" tag, which
is abused by export to Word Eq. editor AND import from Word Eq. editor
routines. Personally, I can live without "size" tag (I'd rather have a
global font size(s) changing control/dialog), but the effective
corruption of formulas by insertion of "size 12", "size 8" is quite a
PITA.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/25


On 2012-03-03T03:08:47+00:00 Yury wrote:

Created attachment 57967
10pt equivalent of ooo's "{a123} wideslash {b456}" made in word

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/26


On 2012-03-03T03:10:58+00:00 Yury wrote:

Created attachment 57968
14pt equivalent of "{a123} wideslash {b456}" made in word

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/comments/27

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

** Changed in: glib
   Status: Unknown => New

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  New
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1849686] Re: gnome-shell crashed with signal 5

2019-10-24 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1755779
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from 
g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap 
(invalid Pixmap parameter)"] from ... meta_pre_paint_func()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Unknown crash on ubuntu 19.10

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 24 19:46:17 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-06-23 (122 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcCmdline: gnome-shell -r
  ProcCwd: /home/pvl
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libX11.so.6
   () at /lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /lib/x86_64-linux-gnu/libX11.so.6
   XCompositeGetOverlayWindow () at /lib/x86_64-linux-gnu/libXcomposite.so.1
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-06-29T23:49:14.971566
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849686/+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 1847196] Re: BackendException: PyDrive backend requires PyDrive installation

2019-10-24 Thread Danesh

On 19.10 myself. My workaround was to install pydrive with pip.

>_ sudo pip3 install PyDrive

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

Title:
  BackendException: PyDrive backend requires PyDrive installation

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have deja-dup configured to do a back up to Google Drive. This
  worked until like a month or two ago, at which point it started to
  print

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'pydrive'

  There does not seem to be a pydrive module in the archive; and I
  thought it is using GOA anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  8 09:02:38 2019
  InstallationDate: Installed on 2018-03-14 (572 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2018-11-20 (321 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847196/+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 1755779] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display

2019-10-24 Thread Apport retracing service

** Tags added: bugpattern-needed

** Tags added: eoan

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured_standard() from _gdk_x11_display_error_event()
  ["BadPixmap (invalid Pixmap parameter)"] from ...
  meta_pre_paint_func()

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

Bug description:
  https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee
  https://gitlab.gnome.org/GNOME/mutter/issues/253

  ---

  don't know why, maybe related to printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 10:02:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-02-12 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755779/+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 1843796] Re: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available

2019-10-24 Thread Pat Viafore

I have tested this package in bionic-proposed, and all of my test cases
passed.

Tests cases:

Testing NVIDIA drivers install on non-GPU instance does nothing
Testing NVIDIA drivers install on GPU instance
Specifying different versions for NVIDIA drivers install

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

Title:
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no
  linux-modules-nvidia package is available

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

   * Calling "ubuntu-drivers install" does not install the kernel
  modules when passed the "--gpgpu" argument.

  While matching linux-modules-nvidia packages for the running kernel
  should be the default choice, we should fall back to the DKMS package
  when they are not available.

  The cha

  
  [Test Case]

   * Remove any currently installed nvidia drivers:
 sudo apt-get --purge remove '*nvidia*'

   * Call the ubuntu drivers tool:
 sudo ubuntu-drivers install --gpgpu

   * Restart your computer, and run the nvidia-smi package:
 sudo nvidia-smi

   * Check that the output shows the NVIDIA GPU (this is a sign that the
  kernel module was loaded, and is running properly).

  [Regression Potential]

   * Low. Currently, users relying on the --gpgpu parameter have no NVIDIA 
kernel modules, which prevents them from actually using the NVIDIA GPU.
  
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no 
linux-modules-nvidia package is available.

  Currently, we do not deal with this kind of failure i.e. when no
  linux-modules-nvidia package is available for the kernel in use. If no
  such package can be found, we need to at least attempt installing the
  relevant DKMS package, so that users get the required kernel modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1843796/+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 1849693] [NEW] Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings

2019-10-24 Thread Gert Brinkmann

Public bug reported:

I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser
for the first time, it should have imported all former settings. But it
did not. E.g. all bookmarks and saved passwords are gone.

Is there a way to start the config import afterwards?

The workaround mentioned under the following link did not help in my case:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160

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

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

Title:
  Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
  from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the
  browser for the first time, it should have imported all former
  settings. But it did not. E.g. all bookmarks and saved passwords are
  gone.

  Is there a way to start the config import afterwards?

  The workaround mentioned under the following link did not help in my case:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+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 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

2019-10-24 Thread Kai-Heng Feng

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/

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

Title:
  [amdgpu] Screen Glitching & Kernel Panic

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848108/+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 1848958] Re: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10

2019-10-24 Thread DRracer

kernel 5.2.21 behaves still ok like 4.19.80 and 5.0.x, which has been in
Kubuntu 19.04

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

Title:
  Suspend takes 3 minutes and screen is garbled after resume with
  nouveau driver after upgrade to 19.10

Status in Nouveau Xorg driver:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.

  After upgrading to 19.10 the machine now behaves weird:
  1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.

  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).

  3. Restarting the X-server resolves the issue, i.e. the screen
  contains reasonable content

  4. Text console is working correctly even without restarting the
  X-server

  5. Tried running KDE with and without compositor, got the same
  results.

  I'd like to help fixing this or at least provide technical info that
  will lead to fixing this issue, please tell me what shall I try/test.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Oct 20 23:18:53 2019
  DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M 
GS] [1462:7220]
  InstallationDate: Installed on 2019-04-21 (182 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Micro-Star International GT627
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago)
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1651IMS.10V
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1651
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: GT627
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver 1.000
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1848958/+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 1849711] [NEW] Only GRUB2 have MAX BRIGHTNESS in 19.04 and 19.10

2019-10-24 Thread raza

Public bug reported:

whenever I boot into Ubuntu the grub 2 boot loader have maximum brightness but 
after selecting Ubuntu OS, system return to its normal brightness value , 
previously my Ubuntu version is 19.04 and this problem exists but after 
upgrading to 19.10 this issue still there and nothing works by upgrading 
system, grub remains at high brightness value (even function keys not working 
at that time). Every time i reboot the system the grub 2 have max brightness 
and it returns to normal brightness after reaching to log on screen and then 
everything works fine even functions keys also working.
laptop specs:
AMD reyzen 3 2200u
AMD Radeon Vega 3
HP g7 245

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 24 21:52:44 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [103c:8562]
MachineType: Hewlett-Packard HP 245 G7 Notebook PC
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro quiet splash 
acpi_backlight=vendor quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/03/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8562
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 84.24
dmi.chassis.asset.tag: 5CG9212QLP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 245 G7 Notebook PC
dmi.product.sku: 6JM93PA#ACJ
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan 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/1849711

Title:
  Only GRUB2 have MAX BRIGHTNESS  in 19.04 and 19.10

Status in xorg package in Ubuntu:
  New

Bug description:
  whenever I boot into Ubuntu the grub 2 boot loader have maximum brightness 
but after selecting Ubuntu OS, system return to its normal brightness value , 
previously my Ubuntu version is 19.04 and this problem exists but after 
upgrading to 19.10 this issue still there and nothing works by upgrading 
system, grub remains at high brightness value (even function keys not working 
at that time). Every time i reboot the system the grub 2 have max brightness 
and it returns to normal brightness after reaching to log on screen and then 
everything works fine even functions keys also working.
  laptop specs:
  AMD reyzen 3 2200u
  AMD Radeon Vega 3
  HP g7 245

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 21:52:44 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:8562]
  MachineType: Hewlett-Packard HP 245 G7 Notebook PC
  ProcEnviron:
   LANGUAGE=en_

[Desktop-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-24 Thread M

Dear Ubuntu devs,

issue was reported on 17.10 and still - Ubuntu 19.04 starts fast, Ubuntu
19.10 upgraded from 19.04 / installed from scratch starts very slow.

ANY IDEAS?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848534/+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 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window

2019-10-24 Thread ScHRiLL

If someone needs a workaround for the path part, use the following liner
inotifywait -m ~/Pictures/ -e create | while read path action file; do if [[ 
$file == *"Screenshot"* ]]; then mv $path/"$file" ~/newpath; fi; done

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window

Status in gnome-screenshot package in Ubuntu:
  Opinion

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+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 1849346] Re: kerberos GSSAPI no longer works after deb->snap transition

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

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

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

Title:
  kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://cloud.google.com/docs/chrome-
  enterprise/policies/?policy=AuthServerWhitelist

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPEGNO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-24 Thread Dexuan Cui

Can Ubuntu devs please try to repro the issue? I can not repro it. :-(

Hi M, I assume you can also repro the issue with a VM created from
scratch from the server .iso (see comment #28) with a minimal
installation? If yes, can you please share the vhdx file? If you
configure the disk size to 15GB an use xfs (rather than ext4) in the
installation process, the generated vhdx file should be 1.5GB or so
(IIRC), so I guess there might be a way for you to share the file
somewhere for me to download? Please also use less CPUs (e.g. 2) and
memory for the VM (e.g. 2GB), if this doesn't prevent you from
reproducing the issue.

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-n

[Desktop-packages] [Bug 1849484] Re: ultra-wide monitor recognized properly when plugged in only intermittently

2019-10-24 Thread Jonathan Kamens

OK, this is really weird, but it appears that this problem only happens
(or, at the very least, happens much more frequently) when Synology
Drive Client is running, or more accurately, when the Synology Drive
Client applet is in my top bar.

Furthermore, sometimes (but not always) when I plug in my monitor and
this problem occurs, Synology Drive Client applet process segfaults and
exits, and then if I unplug the monitor and plug it back in again
everything is fine.

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

Title:
  ultra-wide monitor recognized properly when plugged in only
  intermittently

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849484/+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 1848753] Re: [snap] chromium times out connecting document portal with NFS home

2019-10-24 Thread Juho L

With journalctl -f | grep DEN these messages appear to the console after 
waiting the 12ms timeout:
loka 24 20:56:42 koira audit[12568]: AVC apparmor="DENIED" 
operation="file_mmap" profile="/snap/snapd/4992/usr/lib/snapd/snap-confine" 
name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=12568 
comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0
loka 24 20:56:42 koira kernel: audit: type=1400 audit(1571939802.361:56): 
apparmor="DENIED" operation="file_mmap" 
profile="/snap/snapd/4992/usr/lib/snapd/snap-confine" 
name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=12568 
comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0
loka 24 20:56:42 koira audit[1068]: USER_AVC pid=1068 uid=105 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=12568 
label="snap.chromium.chromium"
loka 24 20:56:42 koira kernel: audit: type=1107 audit(1571939802.915:57): 
pid=1068 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=12568 label="snap.chromium.chromium"

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  New

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1848753/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-24 Thread M

Hi Dexuan,

Sorry for delay in answer - I have installed fresh Server 19.10
(installation is of course different - EFI partition setup by installer,
etc. etc.) and after kernel boot messages I've got immediately login
prompt.

After that I've done "sudo apt-get install ubuntu-desktop" and issue is
visible.

size of VM disk with xfs 2,5 GB, with xfs + ubuntu-desktop 5,5GB , size
of "normal" installation 8,5 GB

What can you propose in this situation?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848534/+subscriptions

[Desktop-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

2019-10-24 Thread Roque

Thanks, hope it will be added to mainline soon.

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

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Confirmed

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  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-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  x

[Desktop-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

** No longer affects: network-manager (Ubuntu)

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

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-24 Thread Dexuan Cui

So let me summarize your findings on the same host of yours (I suppose
your VMs use the same config for the number of vCPUs and the memory
size. I also suppose you only tested Hyper-V Generation 2 VMs or you
confirmed Gen-1 vs. Gen-2 makes no difference):

("fast" means you can see the GUI desktop or the text terminal prompt in
about 1~2 seconds, and "slow" means you need a much longer time, e.g. 1
minute (?))

fresh Server 19.10 ==> fast
fresh Server 19.10 + the ubuntu-desktop package ==> slow
fresh Desktop 19.10 ==> slow
fresh Desktop 19.04 ==> fast
fresh Desktop 19.04 upgraded to 19.10 ==> slow

So it looks a change in 19.10 with the xorg causes the slowness.

However, I can not reproduce the issue, because both my fresh 19.10 and
19.04 VMs boot up in 20+ seconds and I never have a boot-up time of 1~2
seconds.

Hi M, can you please check this case:

fresh Desktop 19.04 upgraded to 19.10 ==> slow

What if you boot the VM with the 19.04 kernel + 19.10's userspace (including 
Xorg)?
If it's also slow, then we have more confidence that the 19.04 Xorg has an 
issue.
If it's fast, then the issue may be more likely that the interaction between 
the 19.10 Xorg and the 19.10 kernel is causing the issue.

Can you also please try booting the VM with a "good" 19.04 VM but (ONLY)
upgrading the kernel to 19.10?

In the slow cases, can you check the logs files (/var/log/Xorg*,
/var/log/syslog*) and see if there is any obvious error/warning?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIRele

[Desktop-packages] [Bug 1849693] Re: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings

2019-10-24 Thread Olivier Tilloy

Could it be that the chromium snap was already installed when the
upgrade happened? Can you attach /var/log/apt/history.log.

Also, can you please run "apport-collect 1849693" in a terminal? This
will attach useful additional information to this bug.

The workaround would be to manually copy the contents of
$HOME/.config/chromium to $HOME/snap/chromium/current/.config/chromium,
and to make sure the password-manager-service interface is connected,
but I'd like to understand why this didn't happen automatically first.

** Changed in: chromium-browser (Ubuntu)
   Status: New => 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/1849693

Title:
  Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
  from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the
  browser for the first time, it should have imported all former
  settings. But it did not. E.g. all bookmarks and saved passwords are
  gone.

  Is there a way to start the config import afterwards?

  The workaround mentioned under the following link did not help in my case:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+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 1735981] Re: Huawei ME936 mobile broadband can't connect

2019-10-24 Thread Michael Weimann

Works with Philipp Hufnagl's workaround.

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+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 1849729] [NEW] chromium-browser fails to start after upgrade to eoan

2019-10-24 Thread ts

Public bug reported:

did a distro upgrade to eoan through upon request of popup app in ubuntu
today

restarted the system

tried starting chromium-browser from the "Run Application" (Alt-F2)

Chromium should have started, nothing happened.

Tried again from a shell:

$ chromium-browser 
2019/10/24 22:07:56.441694 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_gRwtXn//home: 
Permission denied

apt-get --purge remove chromium-browser
apt-get install chromium-browser

exits successfully, after exclaiming some stuff about some snap, but
leaves me with

$ chromium-browser 
2019/10/24 22:14:53.150401 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_rkOYc1//home: 
Permission denied


Either the upgrade to eoan left my system broken, or chromium-browser is broken.


lsb_release -rd
Description:Ubuntu 19.10
Release:19.10


$ apt-cache policy chromium-browser
chromium-browser:
  Installed: 77.0.3865.120-0ubuntu1~snap1
  Candidate: 77.0.3865.120-0ubuntu1~snap1
  Version table:
 *** 77.0.3865.120-0ubuntu1~snap1 500
500 http://de.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Oct 24 22:08:43 2019
InstallationDate: Installed on 2019-04-10 (197 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
Snap.ChromeDriverVersion:
 Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed 
with exit code 1: 2019/10/24 22:08:56.371246 cmd_run.go:529: WARNING: 
XAUTHORITY environment value is not a clean path: 
"/misc/home/thorsten/.Xauthority"
 cannot perform operation: mount --rbind /home /tmp/snap.rootfs_6BAwdi//home: 
Permission denied
Snap.ChromiumVersion:
 Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 
1: 2019/10/24 22:08:56.217828 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home/thorsten/.Xauthority"
 cannot perform operation: mount --rbind /home /tmp/snap.rootfs_tHjxkD//home: 
Permission denied
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  chromium-browser fails to start after upgrade to eoan

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  did a distro upgrade to eoan through upon request of popup app in
  ubuntu today

  restarted the system

  tried starting chromium-browser from the "Run Application" (Alt-F2)

  Chromium should have started, nothing happened.

  Tried again from a shell:

  $ chromium-browser 
  2019/10/24 22:07:56.441694 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
  cannot perform operation: mount --rbind /home /tmp/snap.rootfs_gRwtXn//home: 
Permission denied

  apt-get --purge remove chromium-browser
  apt-get install chromium-browser

  exits successfully, after exclaiming some stuff about some snap, but
  leaves me with

  $ chromium-browser 
  2019/10/24 22:14:53.150401 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
  cannot perform operation: mount --rbind /home /tmp/snap.rootfs_rkOYc1//home: 
Permission denied

  
  Either the upgrade to eoan left my system broken, or chromium-browser is 
broken.


  
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 77.0.3865.120-0ubuntu1~snap1
Candidate: 77.0.3865.120-0ubuntu1~snap1
Version table:
   *** 77.0.3865.120-0ubuntu1~snap1 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Oct 24 22:08:43 2019
  InstallationDate: Installed on 2019-04-10 (197 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  Snap.ChromeDriverVersion:
   Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] fail

[Desktop-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2019-10-24 Thread Matthias Prinz

Workarount badpractice works! Thank you!

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+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 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u

2019-10-24 Thread Arek Plich

what equipment do you have  on my Huawei matebook d 14 from ryzen I
noticed problems waking up from sleep

⁣Pozdrawiam
Arkadiusz Plich

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

2019-10-24 Thread Jorg K

OK, I'm running with 68.2.1 now and something terrible has happened. I have a
Spanish language pack installed, and although it's not active, the folders are
now all in Spanish. Eckard, can you please try this version. You're on Mac,
right?
https://queue.taskcluster.net/v1/task/L17h8vIXSx6peUpjHBp2yg/runs/0/artifacts/public/build/target.dmg

So the fix that works on trunk doesn't work on 68, or worse, it's so
zealous that you get the folder names from a language pack you don't
want :-(

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

Title:
E-mail folder names are not localized in thunderbird 68

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

Bug description:
After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
in the French UI. The rest of the UI is in French.

This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
downloaded directly from Mozilla.

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

2019-10-24 Thread Pulsebot

Pushed by mozi...@jorgk.com:
https://hg.mozilla.org/comm-central/rev/8c7735bd0dc3
Avoid IMAP folder operations until final-ui-startup is done. r=aceman DONTBUILD

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

Title:
  E-mail folder names are not localized in thunderbird 68

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

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

2019-10-24 Thread Jorg K

TB 68.2.1 ESR:
https://hg.mozilla.org/releases/comm-esr68/rev/b25e9210922d1efe596ea5a5b281c9cb2fff3cbb

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

Title:
  E-mail folder names are not localized in thunderbird 68

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

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

2019-10-24 Thread Jorg K

Yes, I'm thinking about when to ship this. I think it's too risky for
68.2.0, so it will likely be in 68.2.1 in more than a week. You can
always run the SQL given in the summary on your permissions.sqlite file.

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

Title:
  E-mail folder names are not localized in thunderbird 68

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

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

2019-10-24 Thread Fkrueger-6

Thanks a lot for your efforts! Does this mean that TB 68.x will get the
fix soon?

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

Title:
  E-mail folder names are not localized in thunderbird 68

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

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

2019-10-24 Thread De-berberich

Many many thanks for your relentless efforts to fix this issue, Jörg. 
Being a regular locale switcher I highly appreciate your insistence!

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

Title:
  E-mail folder names are not localized in thunderbird 68

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

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1847772/+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 1847772] Re: E-mail folder names are not localized in thunderbird 68