[Desktop-packages] [Bug 1812683] Re: rhythmbox crashes when trying to play music

2019-01-21 Thread Götz Waschk
This might be a dupe of bug #1801436 as it only happens with the
alternative-toolbar plugin that was enabled by default.

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

Title:
  rhythmbox crashes when trying to play music

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #37 0x4d57 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 16:14:12 2019
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1812683/+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 1796661] Re: Firefox can't download files to an fscrypt protected, unlocked folder

2019-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Firefox can't download files to an fscrypt protected, unlocked folder

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  My Downloads folder is encrypted by fscrypt. I can save and read files
  in there.  However, for Firefox - all downloads fail and it says only
  "download failed" and offers a button to retry which fails again.
  After a failed attempt, a file is created with a proper file name but
  no content (0 bytes).

  When I changed the download dir to a different non-fscrypted folder,
  everything works properly and files do get properly saved.

  I switched to Chromium and Chromium has no problems downloading files
  into any dirs, regardless encrypted or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 62.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pkolaczk   3692 F pulseaudio
   /dev/snd/pcmC0D0c:   pkolaczk   3692 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pkolaczk   3692 F...m pulseaudio
  BuildID: 20181002091723
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 12:10:57 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-04-12 (543 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.0.1 dev enxd481d7358c11 proto dhcp metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev enxd481d7358c11 proto kernel scope link src 192.168.0.2 
metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=62.0.3/20181002091723
  RelatedPackageVersions: adobe-flashplugin 1:20180911.1-0ubuntu0.18.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796661/+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 1812683] Re: rhythmbox crashes when trying to play music

2019-01-21 Thread Götz Waschk
(gdb) bt
#0  0x77183384 in gtk_tree_view_get_column 
(tree_view=tree_view@entry=0x55e847f0 [GtkTreeView], n=n@entry=16)
at ../../../../gtk/gtktreeview.c:12343
#1  0x76ecf5da in _gtk_tree_view_accessible_add_state 
(treeview=0x55e847f0 [GtkTreeView], tree=tree@entry=0x55f801c0, 
node=node@entry=0x56aca100, state=state@entry=GTK_CELL_RENDERER_SELECTED)
at ../../../../gtk/a11y/gtktreeviewaccessible.c:1993
#2  0x771727f9 in gtk_tree_selection_real_select_node 
(selection=selection@entry=0x55e24610 [GtkTreeSelection], 
tree=tree@entry=0x55f801c0, node=node@entry=0x56aca100, 
select=select@entry=1)
at ../../../../gtk/gtktreeselection.c:1632
#3  0x77173146 in _gtk_tree_selection_internal_select_node 
(selection=0x55e24610 [GtkTreeSelection], node=0x56aca100, 
tree=0x55f801c0, path=0x55c58500, mode=, 
override_browse_mode=0)
at ../../../../gtk/gtktreeselection.c:1585
#4  0x771861c8 in gtk_tree_view_real_set_cursor 
(tree_view=tree_view@entry=0x55e847f0 [GtkTreeView], 
path=path@entry=0x55c58500, flags=flags@entry=(CLEAR_AND_SELECT | 
CLAMP_NODE)) at ../../../../gtk/gtktreeview.c:13306
#5  0x7718d4e9 in gtk_tree_view_multipress_gesture_pressed 
(gesture=0x55e7d430 [GtkGestureMultiPress], n_press=1, x=, 
y=, tree_view=0x55e847f0 [GtkTreeView])
at ../../../../gtk/gtktreeview.c:3379
#6  0x710bedae in ffi_call_unix64 ()
---Type  to continue, or q  to quit---
   .so.6
#7  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#8  0x76be3ced in g_cclosure_marshal_generic_va 
(closure=0x55e939f0, return_value=0x0, instance=, 
args_list=, marshal_data=, n_params=3, 
param_types=0x559f4940) at ../../../../gobject/gclosure.c:1604
#9  0x76be3346 in _g_closure_invoke_va (closure=0x55e939f0, 
return_value=0x0, instance=0x55e7d430, args=0x7fffcd70, n_params=3, 
param_types=0x559f4940)
at ../../../../gobject/gclosure.c:867
#10 0x76bfe9ff in g_signal_emit_valist (instance=0x55e7d430, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffcd70) at ../../../../gobject/gsignal.c:3300
#11 0x76bff12f in g_signal_emit 
(instance=instance@entry=0x55e7d430, signal_id=, 
detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#12 0x7700f7fc in gtk_gesture_multi_press_begin (gesture=0x55e7d430 
[GtkGestureMultiPress], sequence=) at 
../../../../gtk/gtkgesturemultipress.c:241
#13 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv 
(closure=0x55ab92d0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x559aa9c0) at ../../../../gobject/gmarshal.c:1950
#14 0x76be3346 in _g_closure_invoke_va (closure=0x55ab92d0, 
return_value=0x0, instance=0x55e7d430, args=0x7fffd130, n_params=1, 
param_types=0x559aa9c0)
at ../../../../gobject/gclosure.c:867
#15 0x76bfe9ff in g_signal_emit_valist (instance=0x55e7d430, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd130) at ../../../../gobject/gsignal.c:3300
#16 0x76bff12f in g_signal_emit 
(instance=instance@entry=0x55e7d430, signal_id=, 
detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#17 0x7700c78e in _gtk_gesture_set_recognized (sequence=0x0, 
recognized=1, gesture=0x55e7d430 [GtkGestureMultiPress]) at 
../../../../gtk/gtkgesture.c:343
#18 0x7700c78e in _gtk_gesture_check_recognized 
(gesture=gesture@entry=0x55e7d430 [GtkGestureMultiPress], 
sequence=sequence@entry=0x0) at ../../../../gtk/gtkgesture.c:389
#19 0x7700dcdb in gtk_gesture_handle_event (controller=0x55e7d430 
[GtkGestureMultiPress], event=0x5739f660) at 
../../../../gtk/gtkgesture.c:747
#20 0x7701099e in gtk_gesture_single_handle_event 
(controller=0x55e7d430 [GtkGestureMultiPress], event=0x5739f660) at 
../../../../gtk/gtkgesturesingle.c:222
#21 0x76fde1e1 in gtk_event_controller_handle_event 
(controller=0x55e7d430 [GtkGestureMultiPress], 
event=event@entry=0x5739f660) at ../../../../gtk/gtkeventcontroller.c:230
#22 0x7719d85b in _gtk_widget_run_controllers (widget=0x55e847f0 
[GtkTreeView], event=0x5739f660, phase=GTK_PHASE_BUBBLE) at 
../../../../gtk/gtkwidget.c:7379
#23 0x77b46642 in rb_tree_dnd_button_press_event_cb 
(widget=widget@entry=0x55e847f0 [GtkTreeView], event=0x5739f660, 
data=) at rb-tree-dnd.c:924
#28 0x76bff12f in  (instance=instance@entry=0x55e847f0, signal_id=, detail=detail@entry=0)
at ../../../../gobject/gsignal.c:3447
#24 0x7705815b in _gtk_marshal_BOOLEAN__BOXED 
(closure=0x55e952f0, return_value=0x7fffd500, n_param_values=, param_values=0x7fffd560, invocation_hint=, 
marshal_data=) at ../../../../gtk/gtkmarshalers.c:83
#25 0x76be310d in g_closure_invoke (closure=0x55e952f0, 
return_value=0x7fffd500, 

[Desktop-packages] [Bug 1812783] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2019-01-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Security update failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan 22 10:21:29 2019
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-11 (255 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1812783/+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 1812783] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2019-01-21 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Security update failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan 22 10:21:29 2019
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-11 (255 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1812783/+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 1803021] Re: No tutorials

2019-01-21 Thread anatoly techtonik
This issue is about error message. Not a support request.

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

Title:
  No tutorials

Status in inkscape package in Ubuntu:
  Invalid

Bug description:
  When selecting `Help -> Tutorials` the error message is shown and no
  tutorial is loaded.

  Failed to load the requested file /usr/share/inkscape/tutorials
  /tutorial-basic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: inkscape 0.92.3-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Nov 13 05:18:54 2018
  InstallationDate: Installed on 2018-11-01 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1803021/+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 1812791] [NEW] Screen power saving does not work

2019-01-21 Thread Jeremy Roth
Public bug reported:

This is a bug that I seen had off and on across various versions of Ubuntu. 
Currently in 18.10 it's back again. The screen never goes blank no matter what 
I set the time to. I can do 
sleep1; xset dpms force standby
manually from a terminal and that works. But the system will not sleep the 
screen automatically.

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

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

Title:
  Screen power saving does not work

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

Bug description:
  This is a bug that I seen had off and on across various versions of Ubuntu. 
Currently in 18.10 it's back again. The screen never goes blank no matter what 
I set the time to. I can do 
  sleep1; xset dpms force standby
  manually from a terminal and that works. But the system will not sleep the 
screen automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812791/+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 1811808] Re: Tearing and/or flickering when using i3wm

2019-01-21 Thread Daniel van Vugt
Come to think of it, one probably could modify some combination
totem/cogl/clutter to avoid tearing in old-style non-compositing window
managers. But that's unlikely to ever get done considering Ubuntu has
been defaulting to compositing window managers for some years now
(Unity/Compiz, Gnome Shell).

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

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

Title:
  Tearing and/or flickering when using i3wm

Status in i3-wm package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1811808/+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 1812381] Re: Color LaserJet Pro MFP M280nw cannot print colors

2019-01-21 Thread Jarl
> Your only solution is to download and install the package from the
Ubuntu disco distribution with 'dpkg -i'.

So does that mean that the bug is not in HPLIP at all and the bug is in
the packaging of HPLIP? And that the packaging bug has been fixed in
package version hplip/3.18.10+dfsg0-3 ?

Or does it mean that the bug is in HPLIP and it has been fixed in HPLIP
3.18.10?


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

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

** Also affects: hplipsetupdebian via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913578
   Importance: Unknown
   Status: Unknown

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

Title:
  Color LaserJet Pro MFP M280nw cannot print colors

Status in HPLIP:
  New
Status in hplipsetupdebian:
  Unknown
Status in hplip package in Ubuntu:
  New
Status in hplip package in Debian:
  Unknown

Bug description:
  Ubuntu version: 18.10
  HPLIP version 3.18.7

  I just bought a Color LaserJet Pro MFP M280nw because HP supports
  printing from Linux.

  The installation was simple, quick and very easy.

  Printing a test page from the printer itself shows a beautiful image of a 
colorul ballon.
  However printing a test page from HPLIP only prints a grayscale test page 
where it usually prints a color test page.

  Further information: In the graphical HPLIP configuration tool (HP
  Device manager) in the Print Settings tab under the General section I
  can see a Output Mode drop-down box, but the drop-down box only has
  one option; "Grayscale".

  I cannot run hp-doctor due to this bug:
  https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1759278

  This has now also been reported on https://h30434.www3.hp.com/t5
  /Printer-Software-and-Drivers/HP-Color-LaserJet-Pro-MFP-M280nw-cannot-
  print-colors-using/m-p/6983569/highlight/true#M153283

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1812381/+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 1763628] Re: autopkgtests are failing on valgrind

2019-01-21 Thread Jeremy Bicha
autopkgtests pass now in cosmic and in disco (well once my 1.4.3-4
upload autosyncs in a few hours).

Do you think it's worth doing a bionic SRU if we can identify what fixed
the autopkgtests in newer versions?

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

Title:
  autopkgtests are failing on valgrind

Status in colord package in Ubuntu:
  New

Bug description:
  This happens now

  autopkgtest [07:42:07]: test make-check: ---]
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - 
- - - - - -
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - 
- - - - - -
  ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9257==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9257==by 0x18898A: set_default_locale (in /bin/bash)
  ==9257==by 0x137E66: main (in /bin/bash)
  ==9257== 
  ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9505==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9505==by 0x18898A: set_default_locale (in /bin/bash)
  ==9505==by 0x137E66: main (in /bin/bash)
  ==9505== 
  autopkgtest [07:42:08]:  summary
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

  From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
  looks like it's cause by the new glib2.0, but I just tried on my
  machine without that package and it still happened.

  Could you have a look please? Looks like it might not actually be
  colord's fault here, but maybe we want to reconsider running under
  valgrind at least for the autopktests?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1763628/+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 267632] Re: title bar doesn't show in dual monitor

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  title bar doesn't show in dual monitor

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  Other applications are rendered without issue. However, Mozilla Thunderbird 
shows without a title bar or Ubuntu's "footer" bar.  I first noticed this 
problem only after switching to dual monitor.  This occurs on the main screen 
of the dual monitor setup.
  1) Ubuntu 8.04
  2) Thunderbird 2.0.0.16
  3) Expect to see an application title bar and a "footer" bar with the hide 
all windows icon
  4) Instead, Thunderbird has no title bar, cuts off the "footer" bar, and 
there appears to be no way to resize it

  ProblemType: Bug
  Architecture: i386
  Date: Sun Sep  7 20:21:33 2008
  Dependencies:
   
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird None [modified: 
/var/lib/dpkg/info/mozilla-thunderbird.list]
  PackageArchitecture: all
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-19-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/267632/+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 529722] Re: NFO filetype is not correctly handled by Firefox

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  NFO filetype is not correctly handled by Firefox

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

Bug description:
  1) Open the following link in firefox 3.5.8:
 * http://www.ludibria.com/nfo.php?sys=wii=4831
  2) Choose link "download NFO"
  3) On the Open Dialog, make sure "Open With gedit" is selected and click OK 
to open

  4) Watch the following error appear:
  <> could not be opened, because the associated helper application does 
not exist. Change the association in your preferences.

  This error should not happen... On step 3 I had selected "open with
  gedit", yet gedit fails to launch and the file never opens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/529722/+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 651147] Re: Firefox's address bar drops down available web addresses whenever it was focused

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox's address bar drops down available web addresses whenever it
  was focused

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  Hi,

  This is not really a bug, I just find it very annoying when I'm used
  to press "alt+d" and "tab" to go to search bar. Now firefox's address
  bar drops down a list of related addresses whenever it was focused. So
  when I press "tab", it will rotate between those addresses. I had to
  press "esc" to close the drop down, then "tab" to the search box.
  However, this does occur in a newly opened tab, because the address
  bar is empty, and there isn't any available choice.

  I'm not sure this is a new feature or a miss programming. Is there
  anyway to reverse it back to the original stat?

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Wed Sep 29 14:58:34 2010
  FirefoxPackages:
   firefox 3.6.10+build1+nobinonly-0ubuntu3
   firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
   firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
  ProcEnviron:
   LANG=en_IE.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/651147/+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 668910] Re: Two duplicate hotmail entries in inbox list

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Two duplicate hotmail entries in inbox list

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  Using Thunderbird 3.0.10, I added a single Hotmail account.

  The functionality is good but under the "Inbox" smart folder there are
  two separate listings for the single Hotmail account that contains the
  same messages. If I delete in one, it deletes in the other, etc.

  I am using Ubuntu Studio 10.04; the full name of Thunderbird installed
  version is 3.0.10+build1+nobinonly-0ubuntu0.10.04.1, and I have
  experience the problem on another distro, but I'm unsure of which.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.10+build1+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Sat Oct 30 17:41:27 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Studio 10.04 LTS "Lucid Lynx" - Release i386 
(20100427.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/668910/+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 118176] Re: No newlines in signature (*nix)

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  No newlines in signature (*nix)

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: mozilla-thunderbird

  My signature file - that is formated with \n newlines, since i use
  Linux - is copyed to the emails without the newlines. (probably the
  routine that attaches the signature to the message is expecting \r\n
  newlines)

  ProblemType: Bug
  Architecture: i386
  Date: Fri Jun  1 02:40:52 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux rolo 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/118176/+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 612254] Re: thunderbird won't start due to prevous hung thunderbird-bin process.

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbird won't start due to prevous hung thunderbird-bin process.

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  After closing thunderbird, often it stays in memory hung (forever).
  When I try to start thunderbird again, I get an 'already running'
  message. Will attach screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sun Aug  1 14:09:05 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/612254/+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 445273] Re: "Run filters on folder" bug

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  "Run filters on folder" bug

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  Thunderbird ver:  2.0.0.23 (20090817)
  OS ver: 2.6.28-15-generic #52-Ubuntu SMP i686 GNU/Linux

  I have a problem with manual filtering:

  1) Trying to run filters independently does nothing

  2) Trying to run filters through "Run filters on folder" command
  produces  "Sending of message failed"

  None of my filters require SMTP or email forwarding interventions (but
  checked as okay anyway); only the moving of incoming mail to specific
  folders.

  Still seems to work automatically okay when downloading from server.

  Cheers

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird 2.0.0.23+build1+nobinonly-0ubuntu0.9.04.1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.28-15-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/445273/+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 668867] Re: Firefox hangs and has becoming very slow. It also crashes Firefox has become virtually unusable

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox hangs and has becoming very slow. It also crashes Firefox has
  become virtually unusable

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  I dont know what else to say other than that it crashes and is
  unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Oct 30 17:00:06 2010
  FirefoxPackages:
   firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support N/A
   firefox-branding 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/668867/+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 597851] Re: Cursor stays as busy cursor after launching Thunderbird

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Cursor stays as busy cursor after launching Thunderbird

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  When you launch Thunderbird, if you move the cursor off the
  Thunderbird application window it will appear as a busy cursor long
  after Thunderbird has finished loading.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Wed Jun 23 13:57:42 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/597851/+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 680525] Re: first tab in firefox has a constant loading icon and won't close

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  first tab in firefox has a constant loading icon and won't close

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  The first tab in firefox has a loading icon that never disappears, no
  matter which page is the first tab. In addition to that, when it gets
  this loading icon that never goes away I cant close the tab through
  conventional means.

  The steps I use to close the tab are:

  1. I right click the tab and select "Open in a New Window"
  2. I close the new window that opens.
  3. Back to the original window I still have a tab I cant close, however now 
it is all blank. So I close firefox all together. 

  When I reopen firefox the tab is gone, however usually within minutes
  the constant loading thing happens again and I have to rinse and
  repeat if I want to close the tab.

  I doubt you ubuntu guys care, however this exact same problem happens
  in Windows, so I think it may be something with a recent change in
  firefox codebase.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  Date: Tue Nov 23 08:21:37 2010
  FirefoxPackages:
   firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.12+build1+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/680525/+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 619808] Re: The Firefox address tab doesn't work, after locking the computer and open it, while firefox running.

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  The Firefox address tab doesn't work, after locking the computer and
  open it, while firefox running.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  I have an updated ubuntu 10.04- LTS the Lucid Lynx, with 
  firefox:  Installed: 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
Candidate: 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
Version table:
   *** 3.6.8+build1+nobinonly-0ubuntu0.10.04.1 0
  500 http://il.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
  100 /var/lib/dpkg/status
   3.6.3+nobinonly-0ubuntu4 0
  500 http://il.archive.ubuntu.com/ubuntu/ lucid/main Packages
   runing on laptop IBM T-41.

  The Firefox address tab working fine, when I clicking the right tab
  all the history of the sites I visited there, and Its auto complete
  the address from the cache.

  Bug - but when the computer auto lock it self while the firefox
  running/opened, and I'm login the address tab and the auto complete
  doesn't work.

  I'm solving the problem by closing and reopening the firefox- restart
  him.

  Please advice 

  Best Regards,

  Assaf Shlush

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Wed Aug 18 15:22:30 2010
  FirefoxPackages:
   firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/619808/+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 911772] Re: gedit crashed with SIGSEGV

2019-01-21 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  gedit crashed with SIGSEGV

Status in gedit package in Ubuntu:
  Expired

Bug description:
  I have opended a kernel.log  which has so much entries that gedit was
  not able to reach then end of the document.

  On closing this fiel gedit SIGSEV was catched by apport deamon.

  I would like to attach the kernel log for reproducing purposes, but it
  has a size of 1.6GB, so  attaching seems not to be indicated.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Wed Jan  4 14:32:02 2012
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: gedit /var/log/apport.log
  SegvAnalysis:
   Segfault happened at: 0x440a08:  mov0x10(%rax),%rdi
   PC (0x00440a08) ok
   source "0x10(%rax)" (0xaaba) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gedit
  Stacktrace:
   #0  0x00440a08 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fffd1e5b418
  StacktraceTop: ?? ()
  Title: gedit crashed with SIGSEGV
  UpgradeStatus: Upgraded to precise on 2011-12-31 (3 days ago)
  UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/911772/+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 1373889] Re: package thunderbird 1:31.1.1+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/omni.ja' to '/usr/lib/thunder

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package thunderbird 1:31.1.1+build1-0ubuntu0.14.04.1 failed to
  install/upgrade: cannot copy extracted data for
  './usr/lib/thunderbird/omni.ja' to '/usr/lib/thunderbird/omni.ja.dpkg-
  new': unexpected end of file or stream

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Ubuntu can't update Thunderbird

  Распаковывается thunderbird (1:31.1.2+build1-0ubuntu0.14.04.1) на замену 
(1:31.1.1+build1-0ubuntu0.14.04.1) …
  dpkg-deb (подпроцесс): разжимающий элемент архива: ошибка lzma: сжатые данные 
повреждены
  dpkg-deb: ошибка: подпроцесс  возвратил код ошибки 2
  dpkg: ошибка при обработке архива 
/var/cache/apt/archives/thunderbird_1%3a31.1.2+build1-0ubuntu0.14.04.1_i386.deb 
(--unpack):
   не удалось скопировать извлечённые данные «./usr/lib/thunderbird/omni.ja» в 
«/usr/lib/thunderbird/omni.ja.dpkg-new»: неожиданный конец файла или потока
  При обработке следующих пакетов произошли ошибки:
   
/var/cache/apt/archives/thunderbird_1%3a31.1.2+build1-0ubuntu0.14.04.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:31.1.1+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  winterman   1805 F pulseaudio
   /dev/snd/controlC0:  winterman   1805 F pulseaudio
   /dev/snd/controlC1:  winterman   1805 F pulseaudio
  BuildID: 20140909111443
  Channel: Unavailable
  Date: Thu Sep 25 20:36:33 2014
  DuplicateSignature: 
package:thunderbird:1:31.1.1+build1-0ubuntu0.14.04.1:cannot copy extracted data 
for './usr/lib/thunderbird/omni.ja' to '/usr/lib/thunderbird/omni.ja.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for './usr/lib/thunderbird/omni.ja' 
to '/usr/lib/thunderbird/omni.ja.dpkg-new': unexpected end of file or stream
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-11-09 (684 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.34  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:31.1.1+build1-0ubuntu0.14.04.1 failed to 
install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/omni.ja' 
to '/usr/lib/thunderbird/omni.ja.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (158 days ago)
  dmi.bios.date: 11/03/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1373889/+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 1000369] Re: Thunderbird window at the bottom is cut off!

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Thunderbird window at the bottom is cut off!

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  First time when I started at the Thunderbird, was not affected by the
  bottom of the window screen!

  See atached screenshot:

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 13.0~b1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.4.0-1.3-generic 3.4.0-rc5
  Uname: Linux 3.4.0-1-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adri   1455 F pulseaudio
  BuildID: 20120509223019
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'CK8S'/'NVidia CK8S with ALC850 at irq 20'
 Mixer name : 'Realtek ALC850 rev 0'
 Components : 'AC97a:414c4790'
 Controls  : 42
 Simple ctrls  : 27
  Card1.Amixer.info:
   Card hw:1 'UART'/'MPU-401 UART at 0x300, irq 5'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Channel: beta
  Date: Wed May 16 19:22:12 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120516)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.100  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  PciNetwork:
   
  Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Windows Media Player Plug-in 10 (compatible; Totem) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
  Prefs:
   extensions.lastAppVersion - 13.0 (prefs.js)
   network.cookie.prefsMigrated - true (prefs.js)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0/20120509223019 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu5
   totem-mozilla 3.0.1-0ubuntu22
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1011.005
  dmi.board.name: 'K8N'
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1011.005:bd02/16/2006:svnASUSTekComputerInc.:pnK8N:pvrSystemVersion:rvnASUSTeKComputerINC.:rn'K8N':rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: K8N
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTek Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1000369/+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 910609] Re: Modifying snippets doesn't work properly

2019-01-21 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Modifying snippets doesn't work properly

Status in gedit package in Ubuntu:
  Expired

Bug description:
  When modifying snippets (let's say from latex), Gedit modifies   "latex.xml" 
and creates a "latex.xml~".
  But the problem is that Gedit uses every file in the directory 
./config/gedit/snippets (xml, xml~, txt ...)

  Then, every snippet is duplicated and doesn't  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/910609/+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 797283] Re: When closing thunderbird the thunderbird process stays at 100% the whole time

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  When closing thunderbird the thunderbird process stays at 100% the
  whole time

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  When closing thunderbird the thunderbird process stays at 100% the
  whole time

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: thunderbird 3.1.10+build1+nobinonly-0ubuntu0.11.04.2
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 2892cad67f71a4db0df94c8bed57c940
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  Date: Tue Jun 14 18:33:14 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to natty on 2011-04-14 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/797283/+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 802974] Re: Firefox always opens in full-screen mode

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox always opens in full-screen mode

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox opens for me all the time in full-screen mode, no matter what I do to 
it. 
  This is very annoying, because I never want it that way, and have to re-size, 
move etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 5.0+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
  Uname: Linux 3.0-1-generic x86_64
  Architecture: amd64
  Date: Tue Jun 28 08:56:08 2011
  FirefoxPackages:
   firefox 5.0+build1+nobinonly-0ubuntu1
   flashplugin-installer 10.3.181.26ubuntu1
   adobe-flashplugin N/A
   icedtea-plugin N/A
  InstallationMedia: Ubuntu-Studio 11.04 "Natty Narwhal" - Release amd64 
(20110426.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/802974/+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 875232] Re: Thunderbird Global Menu dissapears

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Thunderbird Global Menu dissapears

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Hi, I have installed Ubuntu 11.10 x64 on my desktop.

  When running Thunderbird, the globalmenu work just as expected, but
  after playing aroung with windows sizes, and opening the contacts
  window, the thunderbird windows losses it's global menu, just displays
  "Thunderbird email client" ans no window buttons nor menus at all.

  That is all the info I can provide now, please ghuide me if you need
  more information.

  Be advised

  Thanks a lot!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/875232/+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 706541] Re: firefox causes high hard disk load

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  firefox causes high hard disk load

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  I am using firefox-3.5.

  At least every day, but also once in a while the program causes very high 
disk load that makes it impossible to us ethe computer until it's shut down by 
force.
  I tried also the solutions given in:
  https://bugs.launchpad.net/firefox/+bug/215728

  This may have two resons:
  * many websites with multimedia content and API connectors (the usual stuff 
nowadays)
  * bookmark synchronisation

  but without help. this is quite annoying. Please advice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/706541/+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 948658] Re: thunderbirds unable to save a message as a draft. Error in writing temporary file

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbirds unable to save a message as a draft. Error in writing
  temporary file

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  tmp folder overflow

  ProblemType: Bug
  Architecture: i386
  Date: Wed Mar  7 03:08:05 2012
  Dependencies:
   
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird None [modified: 
/var/lib/dpkg/info/mozilla-thunderbird.list]
  PackageArchitecture: all
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/real/RealPlayer
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-31-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/948658/+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 691199] Re: viewing page causes memory leak followed by system lockup

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  viewing page causes memory leak followed by system lockup

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  Viewing the following page in Firefox always causes the entire system
  to grind to a halt almost immediately (you have been warned!) - this
  makes it very difficult to even kill firefox unless you are prepared
  as it very rapidly becomes virtually impossible to open a terminal
  window etc.

  http://www.imperialracingteam.com/imperialracingteam/results0910.html?

  (Suggest you have a "sleep 300; pkill -KILL firefox" already running
  in a terminal window before following the link).

  Memory leak? Whatever it is, it shouldn't be happening... firefox
  shouldn't be bringing the whole system to its knees like that
  (regardless of how badly that particular webpage may be designed)! The
  page is viewable in Chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-26-generic x86_64
  Architecture: amd64
  Date: Thu Dec 16 17:24:57 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/691199/+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 915573] Re: firefox fullscreen mode(f11) makes unity bar always on top

2019-01-21 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  firefox fullscreen mode(f11) makes unity bar always on top

Status in firefox package in Ubuntu:
  Expired

Bug description:
  just open firefox web browser and press f11, later close this mode,
  you will see what i mean

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 10.0~b3+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
  Uname: Linux 3.2.0-8-generic-pae i686
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shududy1574 F pulseaudio
   /dev/snd/pcmC0D0p:   shududy1574 F...m pulseaudio
  BuildID: 20120105165248
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 45'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,1043841c,00100100'
 Controls  : 14
 Simple ctrls  : 9
  Channel: beta
  Date: Thu Jan 12 21:27:32 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120104)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.3  metric 1
  Profiles: Profile0 (Default) - LastVersion=10.0/20120105165248 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd08/23/2010:svnASUSTeKComputerINC.:pn1015PEM:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PEM
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/915573/+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 860828] Re: thunderbird is crashed

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbird is crashed

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  I restarted the system then also not possible to open thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alwyn  1503 F pulseaudio
  BuildID: 20110925021328
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44'
 Mixer name : 'SigmaTel STAC9221 A1'
 Components : 'HDA:83847680,102801d7,00103601 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 21
 Simple ctrls  : 12
  Channel: release
  Date: Wed Sep 28 00:27:06 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 42.108.162.229 
   169.254.0.0/16 dev ppp0  scope link  metric 1000
  Prefs:
   places.database.lastMaintenance - 1316792497
   extensions.lastAppVersion - 7.0
   network.cookie.prefsMigrated - true
   places.history.expiration.transient_current_max_pages - 31120
   javascript.allow.mailnews - false
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0/20110925021328 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to oneiric on 2011-09-27 (0 days ago)
  dmi.bios.date: 07/10/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0RT486
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/10/2007:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn0RT486:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXC062
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/860828/+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 1117191] Re: automatic return receipt

2019-01-21 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  automatic return receipt

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  I had set on my account to ALWAYS SEND return receipt (in all 3
  cases).

  But It has no effect - I'm always ASKED to send or not the receipt.

  
  Notes:
  - restart of FF don$t help
  -  I have three accounts in FF, global setting of receipts is set to ASK for 
all 3 cases
  - on one (target) account I have set the receipt different - all 3 cases = 
always send
  - from another account in FF I send test message to that one with asking for 
receipt
  - the target account after POP asks me to send receipt - manually. 
Automatically is the receipt not send.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 17.0.2+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu15.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hugo   1953 F pulseaudio
   /dev/snd/controlC1:  hugo   1953 F pulseaudio
  BuildID: 20130106044124
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 46'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0887,1462d740,00100302 
HDA:80862805,80862805,0010'
 Controls  : 50
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'Set'/'C-Media USB Headphone Set at usb-:00:1a.0-1.1, full 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:000c'
 Controls  : 7
 Simple ctrls  : 3
  Channel: Unavailable
  Date: Wed Feb  6 11:11:19 2013
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120401)
  IpRoute:
   default via 10.6.6.138 dev eth0  proto static 
   10.6.6.0/24 dev eth0  proto kernel  scope link  src 10.6.6.1  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   217.31.204.130 via 10.6.6.138 dev eth0  proto static 
   217.31.204.131 via 10.6.6.138 dev eth0  proto static
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MarkForUpload: True
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=17.0.2/20130106044124 (In use)
  RelatedPackageVersions:
   icedtea-6-plugin  1.2-2ubuntu1.3
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MA-E35 (MS-7740)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd08/04/2011:svnMSI:pnMS-7740:pvr1.0:rvnMSI:rnH61MA-E35(MS-7740):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7740
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1117191/+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 1758290] Re: package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operat

2019-01-21 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to
  install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery
  /www-graf/gryquest.gif.dpkg-new': Operation not permitted

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  When starting Ubuntu 14.04 I get the Message "System program problem 
detected".
  Kind regards
  Udo

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Wed Mar 21 13:57:39 2018
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu5.2:unable to 
open '/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operation 
not permitted
  InstallationDate: Installed on 2016-03-03 (749 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to 
install/upgrade: unable to open 
'/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1758290/+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 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-01-21 Thread Daniel van Vugt
** Description changed:

+ [Impact]
+ 
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)
  
- Steps to reproduce the issue:
+ [Test Case]
+ 
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.
+ 
+ [Regression Potential]
+ 
+ Low to moderate. The affected code is only used in rendering shell popup
+ menus. But no regressions are expected as the upstream fix has been
+ tested for many months and fixes multiple bugs.
+ 
+ [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'cursor-size' b'96'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Impact]
  
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)
  
  [Test Case]
  
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.
  
  [Regression Potential]
  
- Low to moderate. The affected code is only used in rendering shell popup
- menus. But no regressions are expected as the upstream fix has been
- tested for many months and fixes multiple bugs.
+ Low. The affected code is only used in rendering shell popup menus. But
+ no regressions are expected as the upstream fix has been tested for many
+ months and fixes multiple bugs.
  
  [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. 

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-21 Thread Daniel van Vugt
We're working on getting this fix into all the current Ubuntu
releases...

Can someone please fill in Test Case in the description at the top?

** Description changed:

+ [Impact]
+ 
+ I'm seeing a several gigs (more than 70GB) a day of
+ org.gnome.Shell.desktop log entries.
+ 
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602
  
- ---
+ [Test Case]
+ 
+ [Regression Potential]
+ 
+ [Original Description]
  
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:
  
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  
  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  
  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work for me.
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DisplayManager: gdm3
  

[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom

2019-01-21 Thread Daniel van Vugt
** Description changed:

- Shell text and some icons have sharp edges during zoom. Screenshot
- attached.
+ [Impact]
  
+ Shell text and some icons have sharp edges during zoom. Screenshot attached.
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/387
+ 
+ [Test Case]
+ 
+ 1. Settings > Universal Access > Zoom = ON
+ 2. Click on the time/calendar and look closely at the font edges.
+ Expect: the edges should be smooth when zoomed.
+ 
+ [Regression Potential]
+ 
+ Low to moderate potential effect on other parts of Gnome Shell. The code
+ being changed is only used in shell popup menus at the moment.
+ 
+ [Other Info]
+ 
+ This is not an important bug at all. Its fix is just a happy consequence
+ of fixing the more important bug 1767648, so that's why it is getting
+ SRU'd.

** Description changed:

  [Impact]
  
  Shell text and some icons have sharp edges during zoom. Screenshot attached.
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/387
  
  [Test Case]
  
  1. Settings > Universal Access > Zoom = ON
  2. Click on the time/calendar and look closely at the font edges.
  Expect: the edges should be smooth when zoomed.
  
  [Regression Potential]
  
  Low to moderate potential effect on other parts of Gnome Shell. The code
  being changed is only used in shell popup menus at the moment.
  
  [Other Info]
  
  This is not an important bug at all. Its fix is just a happy consequence
  of fixing the more important bug 1767648, so that's why it is getting
- SRU'd.
+ SRU'd - for bug 1767648.

** Description changed:

  [Impact]
  
  Shell text and some icons have sharp edges during zoom. Screenshot attached.
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/387
  
  [Test Case]
  
  1. Settings > Universal Access > Zoom = ON
  2. Click on the time/calendar and look closely at the font edges.
  Expect: the edges should be smooth when zoomed.
  
  [Regression Potential]
  
- Low to moderate potential effect on other parts of Gnome Shell. The code
- being changed is only used in shell popup menus at the moment.
+ Low potential effect on other parts of Gnome Shell. The code being
+ changed is only used in shell popup menus at the moment.
  
  [Other Info]
  
  This is not an important bug at all. Its fix is just a happy consequence
  of fixing the more important bug 1767648, so that's why it is getting
  SRU'd - for bug 1767648.

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

Title:
  Shell text and some icons have sharp edges during zoom

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Shell text and some icons have sharp edges during zoom. Screenshot attached.
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/387

  [Test Case]

  1. Settings > Universal Access > Zoom = ON
  2. Click on the time/calendar and look closely at the font edges.
  Expect: the edges should be smooth when zoomed.

  [Regression Potential]

  Low potential effect on other parts of Gnome Shell. The code being
  changed is only used in shell popup menus at the moment.

  [Other Info]

  This is not an important bug at all. Its fix is just a happy
  consequence of fixing the more important bug 1767648, so that's why it
  is getting SRU'd - for bug 1767648.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+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 1812780] [NEW] Gnome Shell crashes when Android emulator started

2019-01-21 Thread Kostadin Stoilov
Public bug reported:

I am filing this bug with gjs because the behaviour started after
upgrading to 1.52.5-0ubuntu18.04.1

Steps to reproduce are:

1. Launch an Android emulator from Android Studio: I used all default
settings and Andoid Pie x86 image

2. Change workspace via hotkey

3. Result is gnome-shell crashes and resets

Workaround is to run:
sudo apt install libgjs0g=1.52.1-1ubuntu1
sudo apt install gjs=1.52.1-1ubuntu1

This is from /var/log/syslog at the time of the gnome-shell crash

Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 
'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 
'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 
'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 
'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: Object Gio.Settings 
(0x55703194e880), has been already deallocated - impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs
Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for 
context 0x55702bd7d340 ==
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c135080 
i   resource:///org/gnome/shell/ui/messageTray.js:173 (0x7f5560090ab0 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c1e680 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134fe0 
i   resource:///org/gnome/shell/ui/messageTray.js:812 (0x7f55600a0098 @ 28)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c1f260 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x55702c134f40 
i   resource:///org/gnome/shell/ui/windowAttentionHandler.js:100 
(0x7f5542c43808 @ 42)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c1fe40 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #6 0x55702c134ec8 
i   resource:///org/gnome/shell/ui/windowAttentionHandler.js:44 (0x7f5542c43340 
@ 17)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #7 0x7ffc05c21150 
b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f5542dd2230 @ 386)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #8 0x55702c134e40 
i   resource:///org/gnome/shell/ui/messageTray.js:479 (0x7f556009db38 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #9 0x7ffc05c21da0 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #10 0x55702c134dc0 
i   resource:///org/gnome/shell/ui/calendar.js:801 (0x7f55600a9ef0 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #11 0x7ffc05c22990 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #12 0x7ffc05c22a60 
b   self-hosted:918 (0x7f5542df12b8 @ 394)
Jan 22 06:01:55 kostadin-XPS gnome-shell[16305]: Object Meta.WindowActor 
(0x55702f200b80), has been already deallocated - impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for 
context 0x55702bd7d340 ==
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c134e48 
i   resource:///org/gnome/shell/ui/windowManager.js:1787 (0x7f5542b24670 @ 113)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c21040 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134dc0 
i   resource:///org/gnome/shell/ui/tweener.js:112 (0x7f5542dc8e68 @ 37)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c22ab0 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f5542dd2b38 @ 
54)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x7ffc05c22c00 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f5542dd2bc0 @ 
1626)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c22cb0 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f5542dd2c48 @ 
100)
Jan 22 06:01:55 kostadin-XPS 

[Desktop-packages] [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-21 Thread Daniel van Vugt
Yes please for a new log.

This bug is almost certainly fixable. We just need a complete log, and
then a lot of patience to wait for some upstream developer to get around
to figuring it out.

If you can't wait and want to use the machine now then Lubuntu might be a 
better option:
http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions

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


Re: [Desktop-packages] [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-21 Thread Alexander A Theiler
Hey Daniel,

Yeah, at the beginning of this all, I thought it was taking a long time to
boot as well, but even after letting the system sit at the purple screen
for quite some time, it never went anywhere.  I had a though that my
ancient laptop might simply be too old to properly run Ubuntu, but I was
optimistic.  What's strange is that after it crashes, it boots entirely
normally, and runs very well without any lag or video issues at all.

I'll chalk this up to being a bug related to my system being quite old.

Do you still want that new boot log after 15 minutes of waiting?

Thanks

Alex



On Mon, Jan 21, 2019 at 8:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Alex,
>
> It's unclear how long this bug will take to get resolved, if at all.
> Even if you find the machine does start up after 15 minutes or so, it
> might not perform well enough to be usable.
>
> If you would like to use Ubuntu on it then maybe the lighter weight
> Lubuntu is a better solution right now:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1
> -desktop-amd64.iso
> 
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+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 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-21 Thread Daniel van Vugt
Alex,

It's unclear how long this bug will take to get resolved, if at all.
Even if you find the machine does start up after 15 minutes or so, it
might not perform well enough to be usable.

If you would like to use Ubuntu on it then maybe the lighter weight
Lubuntu is a better solution right now:

http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1
-desktop-amd64.iso

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+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 1201128] Re: missing icons for .directory files

2019-01-21 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-menus - 3.31.4-2ubuntu1

---
gnome-menus (3.31.4-2ubuntu1) disco; urgency=medium

  * Sync with Debian. Remaining changes:
- debian/gnome-menus.postinst, debian/gnome-menus.prerm,
  debian/gnome-menus.dirs:
  + Remove since we don't use the Debian GNOME menu blacklist
- debian/gnome-menus.triggers: Drop "gmenucache".
- Add 09_app_install_entry.patch:
  + Add Ubuntu Software / GNOME Software to the traditional apps menu
- Add 70_ubuntu-directories.patch
  + Add Ubuntu-specific directories back to POTFILES.in
- Add ubuntu_gcc_translations.patch:
  + Make the unity-control-center categories translatable (lp: #1515911)
- Add 80_file_monitor_delayed.patch:
  + Fix app menus not updating correctly after app install or removal

gnome-menus (3.31.4-2) unstable; urgency=medium

  * Follow upstream and stop using intltool for our update-po rule
  * Run debian/rules update-po
  * Add translate-Debian-directories.patch from Ubuntu
  * Run dh_auto_test

gnome-menus (3.31.4-1) unstable; urgency=medium

  * New upstream release
- Drop the Sundry menu
  * Drop obsolete Build-Depends on intltool
  * Refresh patches
  * Drop 12_alacarte.path: obsolete with new release

gnome-menus (3.31.3-1) unstable; urgency=medium

  * New upstream release:
- Includes updates for renamed .desktop files
  * Bump debhelper compat to 11
  * Update Vcs fields for migration to https://salsa.debian.org/
  * Add -Wl,-O1 to our LDFLAGS
  * Bump Standards-Version to 4.3.0
  * debian/desktop-files/:
- Update some of the directory icon names (LP: #1201128)
  * Drop patches applied in new release:
- 03_kde-legacydirs.patch
- 30_xdg_syntax.patch
- 31_nl_translation.patch
  * Refresh patches

 -- Jeremy Bicha   Mon, 21 Jan 2019 20:19:06 -0500

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

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

Title:
  missing icons for .directory files

Status in gnome-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Fix Released

Bug description:
  Directory files have been shipped with incorrect Icon= fields. For
  example, ActionGames.directory contains Icon=weather-storm.

  This should instead read Icon=applications-action (1) which is
  included in many icon sets (2), leaving this kind of substitution to
  the theme author using symlinks. Including references to these
  substitutions directly in the .directory files is an inappropriate and
  unecessary kludge which breaks themes, including the default one.

  I've only  checked the Games .directory files so far, since that is
  what I was doing when I encountered the bug, but they all exhibit this
  problem. I'm using Ubuntu 13.04, but it's the kind of thing that could
  have been sitting undone for a while. It's probably worth checking
  whether this bug exists upstream or whether it's been introduced by
  the Ubuntu team.

  Upon further checking, Bug #421294 is a particular case of this bug,
  where the line reads Icon=system-run rather than Icon=applications-
  puzzles. From this report and Bug #421695 it seems likely that this
  bug was introduced in Karmic.

  (1) or similar - I'm not entirely sure on whether this will shake out
  as applications-action or applications-games-action; Gnome currently
  goes one way and KDE the other but, either way, symlinks are cheap and
  it can be sorted out through freedesktop.

  (2) Ubuntu's own Humanity icon set includes icons of this form, but
  they are not used because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1201128/+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 1812746] Re: .desktop files not displayed or executed correctly in 19.04

2019-01-21 Thread Daniel van Vugt
** Summary changed:

- desktop icon created by VirtualBox no longer working in disco
+ .desktop files not displayed or executed correctly in 19.04

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

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

Title:
  .desktop files not displayed or executed correctly in 19.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  I told VirtualBox to create a desktop icon for one of my virtual
  machines. It worked just fine in cosmic.

  After upgrading to disco, however, instead of showing up as an icon,
  it shows up as a ".desktop" text file, and double-clicking it just
  opens the text file in gedit.

  I tried deleting and recreating the icon in VirtualBox, and that
  didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:52:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1812746/+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 1812190] Re: distorted and disappearing icons on the toolbar at the top

2019-01-21 Thread Daniel van Vugt
I think this might be a duplicate of bug 1812266:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

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

Title:
  distorted and disappearing icons on the toolbar at the top

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1. I don't see the language switching icon. 
  2. I expect to see her switching languages. 
  3. When installed on a new computer, some icons disappear (language, 
network), or the display is distorted, for example, the wi-fi icon is displayed 
with a delay of about a minute.

  ---
  1. Не вижу иконки переключения языка. 
  2. Ожидаю увидеть её переключаясь между языками. 
  3. При установки на новый компьютер пропадают некоторые иконки (языковая, 
сетевая), или искажается отображение, например значёк wi-fi отображается с 
запазданием около минуты.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 15:03:16 2019
  InstallationDate: Installed on 2018-08-17 (153 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to bionic on 2018-12-27 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812190/+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 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-21 Thread Daniel van Vugt
Ah, I see. You started with Ubuntu GNOME 14.04 and then upgraded. So you
likely still have the upstream theme that is grey. And "grey" is not a
problem.

I now think this might be one of the incarnations of bug 1769383. I
think maybe a few related bugs have been grouped in there so first
please wait for the fix for bug 1769383 to see if it improves things.

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812014] Re: keyboard not responding after suspend after some time

2019-01-21 Thread Daniel van Vugt
Can you please:

1. Open a Terminal and run 'top'. Leave it running.

2. Suspend, resume and reproduce the bug.

3. About 10 seconds or more later, while the keyboard is not responding,
please take a photo of the Terminal window with 'top' running in it.

4. Attach the photo here.

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

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-01-21 Thread Treviño
Kai-Heng Feng,

What's the status of the kernel fix in bionic?

As to verify UI fixes we should get everything in.

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-shell source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1812014] Re: keyboard not responding after suspend after some time

2019-01-21 Thread Daniel van Vugt
I will still avoid mentioning "performance" in the bug title to stop
other people from jumping on board thinking this is the same as their
"performance" problems.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812014] Re: keyboard not responding after suspend after some time

2019-01-21 Thread Daniel van Vugt
OK then, maybe they are related. That's quite possible since gnome-shell
is basically one single threaded event loop.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1621282] Re: dconf-editor shouldn't be in Sundry

2019-01-21 Thread Jeremy Bicha
The Sundry folder has been removed from gnome-menus 3.31.4.

** Changed in: ubuntu-gnome
   Status: New => Fix Released

** Changed in: gnome-menus (Ubuntu)
   Status: New => Fix Released

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

Title:
  dconf-editor shouldn't be in Sundry

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-menus package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu GNOME 16.10 Beta by default, there is one item in the Sundry
  folder in the Activities Overview: dconf-editor. It should be moved to
  Utilities instead. Unlike some of the other stuff in Sundry, it's not
  a legacy app.

  I tried working on this bug by patching gnome-menus but it's not
  working in GNOME.

  I also saw that Debian patches gnome-menus to keep alacarte out of
  Sundry but in Debian testing, alacarte is in Sundry so something isn't
  working right at all.

  Personally, "Sundry" never did make much sense and I don't believe it
  was ever defined. The category hasn't been updated in years. I think
  we should remove the Sundry category.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1621282/+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 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-21 Thread Daniel van Vugt
Thanks Josh.

I *think* that there are two issues you are facing:

1. The nouveau kernel driver doesn't support your Nvidia GPU properly,
which is why "I have to boot with `nouveau.modeset=0`, otherwise boot
hangs at Plymouth after entering my disk encryption password.". But that
doesn't matter too much here since the desktop will be rendered using
the Intel GPU instead.

2. i3wm doesn't seem to be using compositing, so tearing and flickering
is expected. Maybe you can configure i3wm to enable compositing, or
maybe it doesn't support it at all. Either way that is a problem with
i3wm only.

Only #2 is the real problem here. If you would like to avoid tearing
then I suggest you will need to use a different window manager or
desktop environment. Not i3wm.

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

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

** No longer affects: gnome-shell (Ubuntu)

** Summary changed:

- Tearing and/or flickering when using Intel graphics
+ Tearing and/or flickering when using i3wm

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

Title:
  Tearing and/or flickering when using i3wm

Status in Ubuntu:
  Invalid

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1811808/+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 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Core 2 T7200]

2019-01-21 Thread Daniel van Vugt
Note to developers: This system seems to have an Intel GMA 950 GPU.
Limited to OpenGL 1.4? So it is much older than the CPUs that bug
1727356 was about. Still, this system should start up eventually even if
using software rendering.

** Summary changed:

- When booting, the computer hangs at a purple screen and no login prompt is 
ever displayed
+ When booting, the computer hangs at a purple screen and no login prompt is 
ever displayed [Apple Macbook 2,1 - Core 2 T7200]

** Summary changed:

- When booting, the computer hangs at a purple screen and no login prompt is 
ever displayed [Apple Macbook 2,1 - Core 2 T7200]
+ When booting, the computer hangs at a purple screen and no login prompt is 
ever displayed [Apple Macbook 2,1 - Intel GMA 950]

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

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

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+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 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-01-21 Thread Daniel van Vugt
Doug,

This bug was a request to get two missing commits into Ubuntu. They are
already in some versions of Ubuntu so:

> Since this bug is fixed in Ubuntu 18.10 onward I'm going to mark it as
fixed and we can nominate 18.04 to get the fix later.

This bug is Fix Released in 18.10 onward, but not 18.04 yet. "Fix
Released" is still the correct status since that tracks the current
Ubuntu release.

That all said, there are still problems with Wayland support in the
Nvidia driver outlined above so we don't yet recommend it for anyone,
even in 19.04, and even though this bug is fixed.

Please log your own new bug to describe any problems you have rather
than adding comments here. This bug is for the original reporter only.

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+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 1811900] Re: SRU 3.28 latest git to bionic

2019-01-21 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-21 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055

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

Title:
  gnome-shell filling up syslog with thousands/millions of entries with
  stack traces ending in osdWindow.js (lines 206/207 in bionic, lines
  223/224 in cosmic)

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-01-21 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-shell source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1800101] Re: gnome-shell uses 100% CPU

2019-01-21 Thread Daniel van Vugt
Ansis, please log your own separate bugs for each different scenario
that uses high CPU. When doing so note also that strace information is
not useful, but thanks anyway.

This bug is for René Schultz Madsen only, still awaiting feedback from
comment #11.

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

Title:
  gnome-shell uses 100% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  For no obvious reason gnome-shell starts to use 100% CPU.

  This is a standard install of Ubuntu 18.04 with no special extensions
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 10:03:02 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-08-15 (71 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800101/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt

2019-01-21 Thread Daniel van Vugt
** No longer affects: gnome-shell (Ubuntu)

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Problem is occurring if dual monitor is used. Second monitor is
  repeatingly blank and activated again. At the bottom it probably
  contains the upper part of the first monitor. I had the same problem
  at 18.04 when using gdm3 without wayland during logon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic i686
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: i386
  AssertionMessage: double free or corruption (fasttop)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 21:02:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_signal_restore_set (set=0xbfcd5e9c) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
   __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
   __GI_abort () at abort.c:79
   __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption 
(fasttop)") at malloc.c:5350
  Title: gnome-shell assert failure: double free or corruption (fasttop)
  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/mutter/+bug/1790525/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou

2019-01-21 Thread Daniel van Vugt
Gert,

I agree bug 1795760 is different. It has been unmarked as a duplicate so
maybe use that instead?

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2:
  error 0: invalid global wl_output (20)\n"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+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 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture

2019-01-21 Thread Daniel van Vugt
** Summary changed:

- Xwayland crashed with SIGABRT in OsAbort()
+ Xwayland crashed with SIGABRT in OsAbort() from ... from 
FatalError("wl_surface@429: error 2: Failed to create a texture for surface 
429: Failed to create texture 2d due to size/format constraints\n")

** This bug is no longer a duplicate of bug 1745799
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: 
invalid global wl_output (20)\n"]

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

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from ... from
  FatalError("wl_surface@429: error 2: Failed to create a texture for
  surface 429: Failed to create texture 2d due to size/format
  constraints\n")

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This bug contains a crash related to bug 1795089.
  Local code is used for libmutter, to solve bug 1790525 and to display 
buffersizes at module setup_spans at cogl/cogl/cogl-texture-2d-sliced.c and at 
module allocate_from_bitmap at cogl/cogl/driver/gl/cogl-texture-2d-gl.c .

  Dual monitor is used without a monitors.xml files usable by gdm3 with
  wayland.

  After logging in using ubuntu with wayland both screens are shown, but
  crash after a short time without user doing anything.

  At syslog we see the displayed buffersizes which are too large before
  the crash:

  Oct  2 23:57:42 Gert2 gnome-shell[2636]: GK_allocate_from_bitmap 2560 1024
  Oct  2 23:57:42 Gert2 gnome-shell[2636]: GK_cogl_set_error Failed to create 
texture 2d due to size/format constraints
  Oct  2 23:57:42 Gert2 gnome-shell[2636]: Failed to allocate texture: Failed 
to create texture 2d due to size/format constraints

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xwayland 2:1.20.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  2 23:57:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
     Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4ccc6cca-be3d-4471-9677-1012a53ebfd7 ro splash quiet vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   _start ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/11/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795760/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-21 Thread Treviño
** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell filling up syslog with thousands/millions of entries with
  stack traces ending in osdWindow.js (lines 206/207 in bionic, lines
  223/224 in cosmic)

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 

[Desktop-packages] [Bug 1812436] Re: Display locking leaves the Ubuntu dock available and functional

2019-01-21 Thread Alex Murray
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

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

** Information type changed from Private Security to Public Security

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

** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  Display locking leaves the Ubuntu dock available and functional

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm not 100% sure how to trigger the initial issue but after some time
  working with an Ubuntu 18.10 release (fresh install of 18.04 and then
  upgraded to 18.10) when I press the Windows key + L to lock the screen
  I'm still able to see the Ubuntu dock and click on them to interact
  with the launchers. I'm able to launch processes, see the list of
  launched apps and stop them, all that with the screen locked.

  My current package version is 3.30.1-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812436/+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 1796661] Re: Firefox can't download files to an fscrypt protected, unlocked folder

2019-01-21 Thread Troels Liebe Bentsen
The issue is because firefox does a rename from the /tmp folder to the
encrypted home folder, right now fscrypt returns EPERM instead of EXDEV
that would be normal when the operation can not complete because of
crossing a mount point or in this case unencrypted to an encrypted
folder.

The upstream firefox bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1521041

But one could argue that the kernel interface is broken and it should
return EXDEV as tools like mv also breaks, there are some patches in the
works but I don't know how far they are, maybe ubuntu could carry them
until they go upstream:

https://patchwork.kernel.org/patch/9943001/

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

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

Title:
  Firefox can't download files to an fscrypt protected, unlocked folder

Status in firefox package in Ubuntu:
  New

Bug description:
  My Downloads folder is encrypted by fscrypt. I can save and read files
  in there.  However, for Firefox - all downloads fail and it says only
  "download failed" and offers a button to retry which fails again.
  After a failed attempt, a file is created with a proper file name but
  no content (0 bytes).

  When I changed the download dir to a different non-fscrypted folder,
  everything works properly and files do get properly saved.

  I switched to Chromium and Chromium has no problems downloading files
  into any dirs, regardless encrypted or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 62.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pkolaczk   3692 F pulseaudio
   /dev/snd/pcmC0D0c:   pkolaczk   3692 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pkolaczk   3692 F...m pulseaudio
  BuildID: 20181002091723
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 12:10:57 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-04-12 (543 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.0.1 dev enxd481d7358c11 proto dhcp metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev enxd481d7358c11 proto kernel scope link src 192.168.0.2 
metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=62.0.3/20181002091723
  RelatedPackageVersions: adobe-flashplugin 1:20180911.1-0ubuntu0.18.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796661/+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 1811900] Re: SRU 3.28 latest git to bionic

2019-01-21 Thread Treviño
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+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 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov
turns of DNS automatic => turn off automatic DNS

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Launchpad Bug Tracker
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-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1812266

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov
** Attachment added: "Screenshot from 2019-01-21 23-11-46.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+attachment/5231234/+files/Screenshot%20from%202019-01-21%2023-11-46.png

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov
That is intentionally done by NM to prevent leaking DNS queries. Which
is privacy sensitive (ie. do _not_ use "public" dns, to query VPN
encrypted hostnames).

If you do not want to use router configured DNS servers, you can specify
per-connection DNS server overrides in network-manager, which is imho
what you should be doing.

Ie. wipe the resolved.conf settings of DNS=, go into system settings
into each of your connections (ie. the wlan & ethernet one) and in
ipv4/ipv6 tabs, turns of DNS automatic, and specify manual DNS servers
there. Then NM will push those to resolved (note you will need to
reconnect).

It's best to use per-connection DNS servers, and specifically per
connection DNS overrides and configure that all in NM. Do not override /
provide fallbacks in resolved.conf. It is poor taste.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812754] [NEW] Libreoffice writer adds blank pages on multiple inputs

2019-01-21 Thread Kevin O'Gorman
Public bug reported:

When I have multiple .txt files on the command line and start
libreoffice writer, it adds (many) blank pages to the documents.  These
blanks contain nothing at all and I have not figured out how to remove
them.  But they are included when I print them.

I'm attaching a file on which this happens.  It contains an anonymized
fragment of the original, repeates a number of times.  I suggest you
create two copies, called perhaps junk1.txt and junk2.txt.

I use the command "soffice junk*" to load them into the writer, and I
get the extra blank pages.

If, however, I just do soffice junk1.txt, I get a document of the
correct size.

I can do that of course, but it is still an annoying and inconvenient
error for my workflow.

---

One hint to debugging: if I do this:

for i in junk1.txt junk2.txt
do
  soffice $i &
done

I see the problem.  If, however, I introduce a delay the problem does
not appear.  Like so:

for i in junk1.txt junk2.txt
do
  sleep 2
  soffice $i &
done

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jan 21 13:58:01 2019
InstallationDate: Installed on 2018-10-18 (95 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "file that exibits the problem"
   https://bugs.launchpad.net/bugs/1812754/+attachment/5231229/+files/junk1.txt

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

Title:
  Libreoffice writer adds blank pages on multiple inputs

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I have multiple .txt files on the command line and start
  libreoffice writer, it adds (many) blank pages to the documents.
  These blanks contain nothing at all and I have not figured out how to
  remove them.  But they are included when I print them.

  I'm attaching a file on which this happens.  It contains an anonymized
  fragment of the original, repeates a number of times.  I suggest you
  create two copies, called perhaps junk1.txt and junk2.txt.

  I use the command "soffice junk*" to load them into the writer, and I
  get the extra blank pages.

  If, however, I just do soffice junk1.txt, I get a document of the
  correct size.

  I can do that of course, but it is still an annoying and inconvenient
  error for my workflow.

  ---

  One hint to debugging: if I do this:

  for i in junk1.txt junk2.txt
  do
soffice $i &
  done

  I see the problem.  If, however, I introduce a delay the problem does
  not appear.  Like so:

  for i in junk1.txt junk2.txt
  do
sleep 2
soffice $i &
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 21 13:58:01 2019
  InstallationDate: Installed on 2018-10-18 (95 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812754/+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 1800101] Re: gnome-shell uses 100% CPU

2019-01-21 Thread Ansis Atteka
I am seeing high CPU utilization by gnome-shell process as well.
Especially when using Chrome Web Browser and moving/resizing windows.
Chrome usage goes up too. This issue happens consistently on 18.04. The
system becomes barely responsible to user input.

Based on strace output of gnome-shell process here is behavior that
caught my attention:

1, gnome-shell invokes clock_gettime() and futex() system calls excessively.
2. gnome-shell on recvmsg() system call receives errors.

sudo strace -c -f -p `pidof gnome-shell`
strace: Process 2028 attached with 18 threads
^Cstrace: Process 2028 detached
strace: Process 2141 detached
...
strace: Process 2566 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 69.380.047219131236 3 futex
 18.600.012661   3  4375   clock_gettime
  5.180.003527   9   390   346 recvmsg
  2.050.001398  10   137   poll
  1.860.001263   4   315   getpid
  1.250.000851  1269   writev
  0.840.000570   962   write
  0.520.000357   2   156   sched_yield
  0.230.000156   437   read
  0.060.38  38 1   restart_syscall
  0.030.19   6 3   nanosleep
-- --- --- - - 
100.000.068059  5581   349 total


It seems that high CPU usage originates from NVidia's shared library
(binary distributed with libnvidia-gl-390:amd64 debian package). The
gnome-shell process loads this library.


# sudo strace -k -o /tmp/aaa -f -p `pidof gnome-shell`

Here is proof that those calls to clock_gettime() system function
originate from NVidia library:

2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=821854879}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=824319178}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=826767633}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=829303953}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=831753193}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=834216603}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=836654560}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=839135214}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=841593660}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]
 > /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.390.77(vk_icdGetInstanceProcAddr+0x5865)
 >  [0xab445]
2028  clock_gettime(CLOCK_MONOTONIC, {tv_sec=14361, tv_nsec=844017483}) = 0
 > /lib/x86_64-linux-gnu/libc-2.27.so(syscall+0x19) [0x11b839]


As for recvmsg() - while it is not necessarily a bug, it is questionable that a 
user space code after just doing recvmsg() and receiving EAGAIN error on 
non-blocking Unix Domain Socket needs to again call recvmsg() without going 
though poll() system call. Here is snippet that I repeatedly see in the strace 
output:


2028  [7f7e93d77567] recvmsg(537095]>, {msg_namelen=0}, 0) = 
-1 EAGAIN (Resource temporarily unavailable)
 > /lib/x86_64-linux-gnu/libpthread-2.27.so(recvmsg+0x47) [0x12567]
 > /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0(xcb_wait_for_special_event+0x4a8) 
 > [0xd888]
 > /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0(xcb_poll_for_reply64+0x178) 
 > [0xe358]
 > /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0(_XFreeX11XCBStructure+0x849) 
 > [0x3dd79]
 > 

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-01-21 Thread Doug McMahon
Maybe I'm missing the point of this bug, if so sorry about that.
The bug seems to be basically about being able to log into a wayland session 
while using nvidia drivers. Though the description has changed a time or two.

So question could be simply rephrased  - Does the fix released imply
that nvidia should be working on 19.04 on all nvidia devices?

It's stated above that - 
"mutter 3.30.2 in 18.10 & 19.04:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, but compiled in 
anyway by accident because the new build deps were weak, and it's working**"

 "** EGLStreams working means Wayland clients get full Nvidia
acceleration but I thought it was broken for a while because that also
includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver
bug? "

What I mentioned is that no m series nvidia i've tested gets nvidia support in 
a wayland session.
(- when logging into wayland one is automatically switched to Intel

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+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 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-01-21 Thread Till Kamppeter
** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  Unable to install hplip 3.18.12 on linux mint 19.1

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  RESTART OR RE-PLUG IS REQUIRED
  --
  If you are installing a USB connected printer, and the printer was plugged in 
when you started this installer, you
  will need to either restart your PC or unplug and re-plug in your printer 
(USB cable only). If you choose to restart, 
  run this command after restarting: hp-setup (Note: If you are using a 
parallel connection, you will have to restart   
  your PC. If you are using network/wireless, you can ignore and continue). 


  Restart or re-plug in your printer (r=restart, p=re-plug in*,
  i=ignore/continue, q=quit) : i

  
  PRINTER SETUP
  -
  Please make sure your printer is connected and powered on at this time.
  Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : 
u

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Printer/Fax Setup Utility ver. 9.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp)
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 


  
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 

  Done.

  
  RE-STARTING HP_SYSTRAY
  --

  HP Linux Imaging and Printing System (ver. 3.18.12)
  System Tray Status Service ver. 2.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: 
PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)

  :~/Downloads$ hp-plugin

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  
  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.18.12 Plugin Self Extracting 
Archive.

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Installer ver. 3.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Plug-in version: 3.18.12
  Installed HPLIP version: 3.18.12
  Number of files to install: 55

  Plugin installation failed
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.

  From kernel log

  
  hplip/plugin.py" name="/etc/xdg/Trolltech.conf" pid=4238 comm="python" 
requested_mask="k" denied_mask="k" fsuid=1000 ouid=0
  [ 9015.754212] audit: type=1400 audit(1548011993.816:100): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" 
name="/run/sudo/ts/" pid=4240 comm="sudo" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [ 9015.862631] audit: type=1400 audit(1548011993.924:101): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/utmp" 
pid=4240 comm="sudo" requested_mask="k" denied_mask="k" fsuid=0 

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-21 Thread Josh Holland
> Does using a Wayland session avoid the bug?

Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note:
after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 &&
apt autoremove --purge`), I have to boot with `nouveau.modeset=0`,
otherwise boot hangs at Plymouth after entering my disk encryption
password.)

In Wayland, xrandr prints the following:

$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
340mm x 190mm
   1920x1080 59.96*+

> Also, what shell are you using?

If you mean shell-as-in-graphical, and I understand correctly what that
means, then I'm using i3wm. If you mean shell-as-in-CLI, then bash.

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811808/+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 1811105] Re: Browser hangs when 'open with' dialog opens.

2019-01-21 Thread TORE
confirming this behaviour as well. also "view page info" is freezing the 
browser.
i just tried the version before, and this works fine (v63.0.3).

Start-Date: 2019-01-16  21:09:52
Commandline: apt upgrade
[...] firefox:amd64 (63.0.3+build1-0ubuntu0.16.04.1, 
64.0+build3-0ubuntu0.16.04.1) [...]

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

Title:
  Browser hangs when 'open with' dialog opens.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 18.04.1 LTS x86_64 with GNOME 3.28.3.
  2) Firefox: Installed: 64.0+build3-0ubuntu0.18.04.1
  3) Dialog box 'open as' to respond to click events in elements and whole 
browser not get inoperable.
  4) Dialog box 'open as' hangs, gets inoperable to click commands (close, 
cancel, ok, save file) when trying to open some attacked file.

  My browser started to hang when the dialog 'open as' appears. It's
  very useful since it quickly opens an attached file from gmail or
  browsing pdf/doc files.

  When the dialog opens, both the dialog and the browser window get
  extremely slow and i have to click several times for the dialog to
  close. No other button responds and sometimes the crash dialog asks if
  i want to force quit or wait.

  I'm having this problem for two weeks now and got so annoyed that
  sadly had to switch back to chrome. This is a very nice feature that
  doesn't work on said browser.

  I already uninstalled/installed, cleaned data and installed a nightly
  build without success. I suspect it's something related to window
  manager or nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   3261 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  9 13:28:59 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet dhcp
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-14 (785 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (140 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 234
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K45A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K45A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1811105/+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 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unable to install hplip 3.18.12 on linux mint 19.1

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  RESTART OR RE-PLUG IS REQUIRED
  --
  If you are installing a USB connected printer, and the printer was plugged in 
when you started this installer, you
  will need to either restart your PC or unplug and re-plug in your printer 
(USB cable only). If you choose to restart, 
  run this command after restarting: hp-setup (Note: If you are using a 
parallel connection, you will have to restart   
  your PC. If you are using network/wireless, you can ignore and continue). 


  Restart or re-plug in your printer (r=restart, p=re-plug in*,
  i=ignore/continue, q=quit) : i

  
  PRINTER SETUP
  -
  Please make sure your printer is connected and powered on at this time.
  Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : 
u

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Printer/Fax Setup Utility ver. 9.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp)
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 


  
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 

  Done.

  
  RE-STARTING HP_SYSTRAY
  --

  HP Linux Imaging and Printing System (ver. 3.18.12)
  System Tray Status Service ver. 2.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: 
PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)

  :~/Downloads$ hp-plugin

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  
  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.18.12 Plugin Self Extracting 
Archive.

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Installer ver. 3.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Plug-in version: 3.18.12
  Installed HPLIP version: 3.18.12
  Number of files to install: 55

  Plugin installation failed
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.

  From kernel log

  
  hplip/plugin.py" name="/etc/xdg/Trolltech.conf" pid=4238 comm="python" 
requested_mask="k" denied_mask="k" fsuid=1000 ouid=0
  [ 9015.754212] audit: type=1400 audit(1548011993.816:100): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" 
name="/run/sudo/ts/" pid=4240 comm="sudo" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [ 9015.862631] audit: type=1400 audit(1548011993.924:101): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/utmp" 

[Desktop-packages] [Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-01-21 Thread Feris-juan
Hi, I've got the same problem, I've got:
error: Python gobject/dbus may be not installed
error: Plug-in install failed.
 then the script stops and a widow with: lug-In install failed appears.

My Python 2.7.15rc1


My hp-check log:

-desktop:~$ hp-check log
Saving output in log file: /home/juan/hp-check.log

HP Linux Imaging and Printing System (ver. 3.18.12)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: 22-19.1 version is not supported. Using 22-19 versions
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 GNU/Linux
 Host: juan-desktop
 Proc: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 GNU/Linux
 Distribution: 22 19.1
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.18.12
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for 22 distro  
19.1 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.18.12

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/HP
ppdbase=/usr/share/ppd
doc=/usr/share/doc/hplip-3.18.12
html=/usr/share/doc/hplip-3.18.12
icon=/usr/share/applications
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv/hp
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=no
foomatic-drv-install=no
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.18.12
restricted-build=no
ui-toolkit=qt4
qt3=no
qt4=yes
qt5=no
policy-kit=no
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=yes
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
[plugin]
installed = 1
eula = 1
version = 3.18.12


Current contents of '~/.hplip/hplip.conf' file:
[upgrade]
notify_upgrade = true
last_upgraded_time = 1547657460
pending_upgrade_time = 0
latest_available_version = 3.17.10

[installation]
date_time = 01/21/19 16:39:24
version = 3.18.12


 


--
| COMPILEDEP |
--

 gcc  gcc - GNU Project C and C++ Compiler  
   REQUIRED-   7.3.0   OK -
 make make - GNU make utility to maintain groups of programs
   REQUIRED3.0 4.1 OK -
 libtool  libtool - Library building support services   
   REQUIRED-   2.4.6   OK -


| General Dependencies |


 libcryptolibcrypto - OpenSSL cryptographic library 
   REQUIRED-   1.1.0   OK -
 python-xml   Python XML libraries  
   REQUIRED-   2.2.5   OK -
 libnetsnmp-devel libnetsnmp-devel - SNMP networking library development 
files REQUIRED5.0.9   5.7.3   OK -
 sane-devel   SANE - 

[Desktop-packages] [Bug 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Julian Andres Klode
This is caused by network-manager pushing ~. as the search domain. This
effectively makes resolved ignore the DNS servers I configured. I could
fix this by adding Domains=~. to resolved.conf, but I don't know, this
does not feel right - network-manager essentially breaks a resolved
feature.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1325525] Re: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d

2019-01-21 Thread Nikolai Bozhenov
I can confirm that the issue is still present in 18.04:
- 53-monospace-lcd-filter.conf is not linked into conf.d (not sure if it is a 
bug by itself)
- when the file is linked into conf.d, the warning about broken config appears 
(this is definitely a bug)

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

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

Title:
  Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu-trusty, and noticed that in Thunderbird the
  fonts are rendered incorrectly. It seemed that the problem is with
  sub-pixel rendering.

  After much googling and finding nothing I've started to compare the 
/etc/fonts/conf.d dir on my Precise machin with the trusty one. I noticed that 
on trusty the 53-monospace-lcd-filter.conf file is missing from the conf.d dir, 
but is available in the conf.avail.
  After I created the symlink and rebooted, my thunderbird font rendering 
became normal again.

  But now if I start from something from the terminal it says:
  "Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 
10: Having multiple values in  isn't supported and may not work as 
expected"

  So the 1st question, why did you leave out the monospace-lcd-
  filter.conf from the fontconfig conf.d, and the second is why didn't
  you update it so it won't complaing about the multiple test tags.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun  2 12:43:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:308c]
  MachineType: LENOVO 3492C4G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=a1bd4186-b465-4605-845f-12c9de2dc180 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F1KT44AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrF1KT44AUS:bd12/21/2012:svnLENOVO:pn3492C4G:pvrThinkCentreEdge72:rvnLENOVO:rn:rvrNODPK:cvnLENOVO:ct3:cvr:
  dmi.product.name: 3492C4G
  dmi.product.version: ThinkCentre Edge72
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jun  2 12:37:17 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9
   inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16498 
   vendor DEL
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325525/+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 1812663] Re: Background Color And Text Color Both Wite with Dark Theme

2019-01-21 Thread Sebastien Bacher
The issue is an upstream one and should be reported on
https://gitlab.gnome.org/GNOME/gedit/issues

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

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

Title:
  Background Color And Text Color Both Wite with Dark Theme

Status in gedit package in Ubuntu:
  New

Bug description:
  The background color and the text color are both white when using the
  dark layout.

  $ cat .config/gtk-3.0/settings.ini 
  [Settings]
  gtk-application-prefer-dark-theme=1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gedit 3.30.2-0ubuntu0.18.10.2
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 13:01:50 2019
  InstallationDate: Installed on 2017-12-15 (402 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1812663/+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 1812683] Re: rhythmbox crashes when trying to play music

2019-01-21 Thread Sebastien Bacher
Could you install the dbgsym
(https://wiki.ubuntu.com/Debug%20Symbol%20Packages) for glib, gtk and
rhythmbox and get a debug backtrace?

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  rhythmbox crashes when trying to play music

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #37 0x4d57 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 16:14:12 2019
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1812683/+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 1812745] [NEW] Rubbish Bin icon on desktop doesn't work, then suddenly starts working

2019-01-21 Thread Jonathan Kamens
Public bug reported:

Immediately after upgrading from cosmic to disco, double-clicking the
"Rubbish Bin" icon on my desktop does nothing.

I try many times, does nothing.

I open a Nautilus window by clicking on the Nautilus icon in the
sidebar, and select "Rubbish Bin" in that window, and I am able to view
it just fine.

Then I double-click the Rubbish Bin icon on the desktop again, and a
window flashes quickly and then disappears.

Then I click it again, and now it is magically working properly, i.e.,
double-clicking opens a Nautilus window displaying the Rubbish Bin.

A couple minutes later I try again, and it's not working again.

Etc.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 15:48:31 2019
InstallationDate: Installed on 2019-01-02 (19 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  Rubbish Bin icon on desktop doesn't work, then suddenly starts working

Status in nautilus package in Ubuntu:
  New

Bug description:
  Immediately after upgrading from cosmic to disco, double-clicking the
  "Rubbish Bin" icon on my desktop does nothing.

  I try many times, does nothing.

  I open a Nautilus window by clicking on the Nautilus icon in the
  sidebar, and select "Rubbish Bin" in that window, and I am able to
  view it just fine.

  Then I double-click the Rubbish Bin icon on the desktop again, and a
  window flashes quickly and then disappears.

  Then I click it again, and now it is magically working properly, i.e.,
  double-clicking opens a Nautilus window displaying the Rubbish Bin.

  A couple minutes later I try again, and it's not working again.

  Etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:48:31 2019
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1812745/+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 1812746] [NEW] desktop icon created by VirtualBox no longer working in disco

2019-01-21 Thread Jonathan Kamens
Public bug reported:

I told VirtualBox to create a desktop icon for one of my virtual
machines. It worked just fine in cosmic.

After upgrading to disco, however, instead of showing up as an icon, it
shows up as a ".desktop" text file, and double-clicking it just opens
the text file in gedit.

I tried deleting and recreating the icon in VirtualBox, and that didn't
help.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 15:52:33 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (19 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  desktop icon created by VirtualBox no longer working in disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I told VirtualBox to create a desktop icon for one of my virtual
  machines. It worked just fine in cosmic.

  After upgrading to disco, however, instead of showing up as an icon,
  it shows up as a ".desktop" text file, and double-clicking it just
  opens the text file in gedit.

  I tried deleting and recreating the icon in VirtualBox, and that
  didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:52:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812746/+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 1711534] Re: Application list cluttered on a fresh Artful installation

2019-01-21 Thread Jeremy Bicha
The Sundry app folder is being removed from Ubuntu 19.04.

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

Title:
  Application list cluttered on a fresh Artful installation

Status in gnome-menus package in Ubuntu:
  Invalid

Bug description:
  GNOME Shell application list contains many rarely-used and sometimes
  redundant app icons like:

  * 3 different icons for fcitx
  * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself)
  * ImageMagick (Most probably rarely used, especially when there's also EOG)
  * Language Support, Input Method (There's a language panel in 
gnome-control-center, so this looks like a unity-control-center leftover)

  Because of that, the application list is 3 pages long, making other
  apps unnecessarily hard to find.

  One way to solve that would be to pack rarely-used, but still useful
  stuff into GNOME's Sundry app folder. Completely redundant icons can
  probably be just removed.

  Original suggestion: https://didrocks.fr/2017/08/03/ubuntu--
  guadec-2017-and-plans-for-gnome-shell-migration/#comment-3455664382

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1711534/+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 1711534] Re: Application list cluttered on a fresh Artful installation

2019-01-21 Thread Jeremy Bicha
The Sundry app folder is being removed.

Please file new separate bugs for any remaining issues.

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

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

Title:
  Application list cluttered on a fresh Artful installation

Status in gnome-menus package in Ubuntu:
  Invalid

Bug description:
  GNOME Shell application list contains many rarely-used and sometimes
  redundant app icons like:

  * 3 different icons for fcitx
  * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself)
  * ImageMagick (Most probably rarely used, especially when there's also EOG)
  * Language Support, Input Method (There's a language panel in 
gnome-control-center, so this looks like a unity-control-center leftover)

  Because of that, the application list is 3 pages long, making other
  apps unnecessarily hard to find.

  One way to solve that would be to pack rarely-used, but still useful
  stuff into GNOME's Sundry app folder. Completely redundant icons can
  probably be just removed.

  Original suggestion: https://didrocks.fr/2017/08/03/ubuntu--
  guadec-2017-and-plans-for-gnome-shell-migration/#comment-3455664382

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1711534/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou

2019-01-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "error9_patch.txt" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2:
  error 0: invalid global wl_output (20)\n"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Petruhin Alexandr
this bug came from this bugfix:

https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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


Re: [Desktop-packages] [Bug 543758] Re: cheese crashed with SIGSEGV when webcam is already in use

2019-01-21 Thread Thiago Figueiro
Unfortunately I’m no longer in a position to reproduce this bug. Feel
free to close it.

Sent on the run; please excuse my brevity.

> On 22 Jan 2019, at 03:11, Paul White <543...@bugs.launchpad.net> wrote:
> 
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
> 
> Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
> 
> Do you still see a problem related to the one that you reported in a
> currently supported version of Ubuntu? Please let us know if you do and
> in which version of Ubuntu otherwise this report can be left to expire
> in approximately 60 days time.
> 
> Thank you for helping make Ubuntu better.
> 
> Paul White
> [Ubuntu Bug Squad]
> 
> ** Changed in: cheese (Ubuntu)
>   Status: Triaged => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (604196).
> https://bugs.launchpad.net/bugs/543758
> 
> Title:
>  cheese crashed with SIGSEGV when webcam is already in use
> 
> Status in Cheese:
>  Expired
> Status in cheese package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Binary package hint: cheese
> 
>  Not much to say. I have recently (yesterday) upgraded from 9.10 to
>  10.4 Beta 1. I just installed Cheese and it crashed after about 5
>  seconds. The problem was that mplayer was open and the same time and
>  "reading" the webcam ie I had run the command "mplayer /dev/v4l/by-id
>  /usb-0402_USB2.0_Camera-video-index0" and that was still running while
>  I tried opening cheese. Shutting down Mplayer fixed the problem and
>  Cheese is working now.
> 
>  So the problems seems to be that Cheese throws a segfault when
>  accessing a camera that is already in use.
> 
>  ProblemType: Crash
>  Architecture: i386
>  Date: Sun Mar 21 23:04:18 2010
>  Disassembly: => 0x0:Cannot access memory at address 0x0
>  DistroRelease: Ubuntu 10.04
>  ExecutablePath: /usr/bin/cheese
>  NonfreeKernelModules: nvidia
>  Package: cheese 2.29.92-0ubuntu1
>  ProcCmdline: cheese
>  ProcEnviron:
>   LANG=da_DK.utf8
>   SHELL=/bin/bash
>  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
>  SegvAnalysis:
>   Segfault happened at: 0x0:Cannot access memory at address 0x0
>   PC (0x) not located in a known VMA region (needed executable 
> region)!
>  SegvReason: executing NULL VMA
>  Signal: 11
>  SourcePackage: cheese
>  StacktraceTop:
>   ?? ()
>   ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>  Title: cheese crashed with SIGSEGV
>  Uname: Linux 2.6.32-16-generic i686
>  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cheese/+bug/543758/+subscriptions

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

Title:
  cheese crashed with SIGSEGV when webcam is already in use

Status in Cheese:
  Expired
Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cheese

  Not much to say. I have recently (yesterday) upgraded from 9.10 to
  10.4 Beta 1. I just installed Cheese and it crashed after about 5
  seconds. The problem was that mplayer was open and the same time and
  "reading" the webcam ie I had run the command "mplayer /dev/v4l/by-id
  /usb-0402_USB2.0_Camera-video-index0" and that was still running while
  I tried opening cheese. Shutting down Mplayer fixed the problem and
  Cheese is working now.

  So the problems seems to be that Cheese throws a segfault when
  accessing a camera that is already in use.

  ProblemType: Crash
  Architecture: i386
  Date: Sun Mar 21 23:04:18 2010
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/cheese
  NonfreeKernelModules: nvidia
  Package: cheese 2.29.92-0ubuntu1
  ProcCmdline: cheese
  ProcEnviron:
   LANG=da_DK.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: cheese
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
  Title: cheese crashed with SIGSEGV
  Uname: Linux 2.6.32-16-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1812735] [NEW] Andyrock has to update this placeholder bug :)

2019-01-21 Thread Treviño
Public bug reported:

Something in OSK doesn't work, he knows about it!

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Released

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Released

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => High

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

Title:
  Andyrock has to update this placeholder bug :)

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Something in OSK doesn't work, he knows about it!

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

2019-01-21 Thread Hans P Möller
Created attachment 148473
lubuntu LXQt file saver

Hi Michael,
the problem is in Lubuntu 18.10 which uses LXQt, the checkbox doesn't exist 
there (see attachment). In KDE it exists, as you pointed.

Who creates the checkbox? Libreoffice or the filemanager (in kubuntu
dolphin)?

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

2019-01-21 Thread Michael Weghorn
Created attachment 148457
Screenshot of save dialog in KDE 5

For me, with a current daily build of the "master" branch, the file
extension is automatically added when using the "kde5" VCL plugin and
taking these steps:

1) open a new Writer document
2) "File" -> "Save as"
3) type "test" as file name (without ".docx" at the end)
4) select filter "Word 2007-2019 (.docx)"
5) make sure the checkbox "Automatically select filename extension" is checked
6) click "OK"

The attached screenshots shows the dialog at the point in time I click
"OK".

The file is the saved as "test.docx".

Is this the scenario that this bug report is covering or did I
misunderstand anything?

Version: 6.3.0.0.alpha0+
Build ID: 87bf8b7900fe4757bd8494f7a72966915f653eb6
CPU threads: 2; OS: Linux 4.19; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-19_19:05:11
Locale: en-US (en_DK.UTF-8); UI-Language: en-US
Calc: threaded

With an older build of master (~1 month old, as of commit
6ba8d6533081dab96c00695dd7a908e0f7bcf164; currently don't have a newer
one with gtk3_kde5 available), I can confirm that this works as
described above with kde5, but not with gtk3_kde5. So this looks like it
might be a gtk3_kde5 problem only, but I might be missing something...

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

2019-01-21 Thread Jan-Marek Glogowski
FYI KDE4 used to have its own auto-extension checkbox in the file open
dialog, so the LO KDE4 integration used that KDE setting and skipped
LOs' own handling. Probably that setting doesn't exist anymore, as file
dialogs are now Qt5 based and now LO has to handle the file auto-
extension on its own.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou

2019-01-21 Thread Gert van de Kraats
I created bug #1795760, which describes a Xwayland-abort and got the
status duplicate of 1745799.

Below is a part of the symbolic trace of the abort.

 #7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n", 
args=0xbf9c7994 "\027uܷ\255\001") at ../../../../../hw/xwayland/xwayland.c:1137
 msg = "wl_surface@429: error 2: Failed to create a texture for surface 
429: Failed to create texture 2d due to size/format constraints\n", '\000' 

 #8 0xb7dc5fef in wl_log (fmt=0xb7dc71ea "%s@%u: error %d: %s\n") at 
../src/wayland-util.c:404

Problem can be solved by using slicing at shm_buffer_attach() at
src/wayland/meta-wayland-buffer.c, if size of texture is too large for
graphics card.

I attach a bug-fix to this bug, which is tested during a long time.


** Attachment added: "error9_patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+attachment/5231177/+files/error9_patch.txt

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2:
  error 0: invalid global wl_output (20)\n"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+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 1808684] Re: Remove 'Archive Mounter' from options to mount ISO files

2019-01-21 Thread Launchpad Bug Tracker
This bug was fixed in the package nautilus - 1:3.30.5-1ubuntu1

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

  * Update to the current stable version
  * debian/mount-archive.desktop, debian/nautilus.install,
debian/patches/03_translations_list_update.patch:
- remove the custom 'mount archive' handler which was added years back,
  nowadays gnome-disk-utility provide a similar feature
  (lp: #1808684)

nautilus (3.30.5-1) unstable; urgency=medium

  * New upstream release
  * Don't have nautilus-data recommend nautilus
  * Restore -Wl,-O1 to our LDFLAGS
  * debian/copyright: nautilus is GPL-3+ instead of GPL-2+

 -- Sebastien Bacher   Thu, 17 Jan 2019 15:46:31
+0100

** Changed in: nautilus (Ubuntu)
   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/1808684

Title:
  Remove 'Archive Mounter' from options to mount ISO files

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Steps:

  1. Open nautilus
  2. Right-click on an ISO image file (like a Windows 10 setup ISO file)
  3. Choose 'Open With Other Application'
  4. Choose 'Archive Mounter'
  5. The mounted fie is empty

  I believe that option is legacy, useless and a duplicate of 'Disk
  Image Mounter', which is the right option to choose to mount ISO
  files. When I mount with 'Archive Mounter', I get an empty mounted
  file with nothing in it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 16 12:53:53 2018
  InstallationDate: Installed on 2018-12-06 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1808684/+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 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

2019-01-21 Thread Launchpad Bug Tracker
This bug was fixed in the package deja-dup - 38.3-1

---
deja-dup (38.3-1) unstable; urgency=medium

  * New upstream release:
- If some files couldn't be backed up, don't override that message
  with successful verification message. (lp: #1371613)
- Tell user how much free space is needed when backup location is tiny
  (lp: #1103567)

 -- Sebastien Bacher   Thu, 17 Jan 2019 11:24:31
+0100

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1371613/+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 1103567] Re: "Backup location is too small" should mention how much space is required

2019-01-21 Thread Launchpad Bug Tracker
This bug was fixed in the package deja-dup - 38.3-1

---
deja-dup (38.3-1) unstable; urgency=medium

  * New upstream release:
- If some files couldn't be backed up, don't override that message
  with successful verification message. (lp: #1371613)
- Tell user how much free space is needed when backup location is tiny
  (lp: #1103567)

 -- Sebastien Bacher   Thu, 17 Jan 2019 11:24:31
+0100

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  "Backup location is too small" should mention how much space is
  required

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  My backup fails with this error:

  Backup location is too small.  Try using one with more space.

  I've since tried to make more space, but I still get this error.

  This error would be much more useful if it told me how much free space
  was required.

  $ lsb_release -d
  Description:  Ubuntu 12.10
  $ dpkg-query -W deja-dup duplicity
  deja-dup  24.0-0ubuntu1
  duplicity 0.6.19-0ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1103567/+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 1018677] Re: scanner doesn't work on bootup

2019-01-21 Thread Thomas Zahreddin
I updated libusb-0.1.so.4 to libusb-dev in ubuntu 18.04 LTS and the
error was gone.

BTW: i am astonished how such an error can remain so long in the
operating system :-(

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

Title:
  scanner doesn't work on bootup

Status in libusb package in Ubuntu:
  Confirmed

Bug description:
  When the computer boots up (12.04) with the scanner attached lsusb
  lists the scanner

  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 03f0:1705 Hewlett-Packard ScanJet 5590
  Bus 002 Device 003: ID 0424:2502 Standard Microsystems Corp. 
  Bus 002 Device 004: ID 0424:2602 Standard Microsystems Corp. USB 2.0 Hub
  Bus 002 Device 005: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card 
Reader
  Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

  On Bus 002 Device 002

  crw-rw-r--+ 1 root root 189, 129 Jun 27 21:51 /dev/bus/usb/002/002

  But when I run scanimage -L

  
  >scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  doesn't work as root either

  scanimage -L
  [sudo] password for manojav: 

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  the only way to get the scanner working again is to power it off (unplug) and 
plug it again. this time its recognized by scanimage -L or xsane running as 
non-root as well root.

  looks like something has got a hold of the device and not letting it
  go! its similar to when a scanning app crashes and leaves things is a
  bad state. only way to clear that is power off the scanner and plug it
  back-in

  this has been happening since 11.10, and now also w/ 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xsane 0.998-3ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun 27 22:00:50 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xsane
  UpgradeStatus: Upgraded to precise on 2012-06-26 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/1018677/+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 1812699] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.77

2019-01-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  Error/crash occurred while installing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Jan 21 10:51:27 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in 
package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1812699/+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 1812699] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.

2019-01-21 Thread James
Public bug reported:

Error/crash occurred while installing.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Mon Jan 21 10:51:27 2019
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
InstallationDate: Installed on 2019-01-20 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  Error/crash occurred while installing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Jan 21 10:51:27 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in 
package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


  1   2   >