[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

2017-09-05 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Incomplete
Status in OEM Priority Project:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions

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


[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2017-09-05 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Importance: Critical => High

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project xenial series:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

   * It is a very bad user experience that the WiFi device is recognized
  as an Ethernet device making Ubuntu users unable to connect to WiFi
  network.

  [Test Case]

   * Find some laptop that can reduplicate this issue.
   * Keep rebooting the system until you see this issue.
   * Usually this issue can be reduplicated within 10 reboot cycles on the 
right laptop.

  [Regression Potential]

   * No trivial regression.

  [Other Info]
   
   * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial

  [Original Bug Description]

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

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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


[Desktop-packages] [Bug 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop

2017-09-05 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Importance: Critical => High

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

Title:
  "disable touchpad while typing" doesn't work on xps 13 and some other
  laptop

Status in OEM Priority Project:
  Triaged
Status in Xserver Xorg Input Synaptics:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  It's reported that there are lots of false action of touch pad as using 
keyboard on xps 13
  with the factory image.

  The factory image is based on xenial.

  One propose that install xserver-xorg-input-libinput with modification
  90-libinput.conf in /usr/share/X11/xorg.conf.d from

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  EndSection
  ...

  to

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  Option "Tapping" "on"
  Option "PalmDetection" "on"
  EndSection
  ...

  helps a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1672619/+subscriptions

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


[Desktop-packages] [Bug 1713981] Re: Xwayland segfaults when using kvm (since 2:1.19.3-1ubuntu4)

2017-09-05 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Fix Released

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

Title:
  Xwayland segfaults when using kvm (since 2:1.19.3-1ubuntu4)

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Using GNOME/wayland in artful, I get that Xwayland/shell segfault when
  using kvm

  Thread 1 "Xwayland" received signal SIGSEGV, Segmentation fault.
  0x0092f4790b6e in zwp_pointer_constraints_v1_lock_pointer (lifetime=2, 
region=0x0, pointer=, surface=, 
zwp_pointer_constraints_v1=0x92f72d8060)
  at ./pointer-constraints-unstable-v1-client-protocol.h:347
  347   ./pointer-constraints-unstable-v1-client-protocol.h: Aucun fichier ou 
dossier de ce type.
  #0  0x0092f4790b6e in zwp_pointer_constraints_v1_lock_pointer 
(lifetime=2, region=0x0, pointer=, surface=, 
  zwp_pointer_constraints_v1=0x92f72d8060) at 
./pointer-constraints-unstable-v1-client-protocol.h:347
  #1  xwl_pointer_warp_emulator_lock (warp_emulator=0x92f7951ab0) at 
../../../../../hw/xwayland/xwayland-input.c:2590
  #2  0x0092f47930f8 in xwl_seat_maybe_lock_on_hidden_cursor 
(xwl_seat=xwl_seat@entry=0x92f72d7dd0) at 
../../../../../hw/xwayland/xwayland-input.c:2762
  #3  0x0092f4794660 in xwl_seat_maybe_lock_on_hidden_cursor 
(xwl_seat=0x92f72d7dd0) at ../../../../../hw/xwayland/xwayland-input.c:2823
  #4  xwl_seat_confine_pointer (xwl_seat=0x92f72d7dd0, xwl_window=0x92f7464630) 
at ../../../../../hw/xwayland/xwayland-input.c:2814
  #5  0x0092f48d60cf in ActivatePointerGrab (mouse=0x92f724e890, 
grab=0x92f797b910, time=..., autoGrab=) at 
../../../../dix/events.c:1531
  #6  0x0092f48d0db4 in GrabDevice (client=client@entry=0x92f769b470, 
dev=dev@entry=0x92f724e890, pointer_mode=1, keyboard_mode=1, 
grabWindow=, 
  ownerEvents=, ctime=0, mask=0x7ffcba605420, grabtype=1, 
curs=0, confineToWin=31457299, status=0x7ffcba60541f "") at 
../../../../dix/events.c:5120
  #7  0x0092f48d3a1a in ProcGrabPointer (client=0x92f769b470) at 
../../../../dix/events.c:4908
  #8  0x0092f48c5e58 in Dispatch () at ../../../../dix/dispatch.c:479
  #9  0x0092f48c9e80 in dix_main (argc=10, argv=0x7ffcba605628, 
envp=) at ../../../../dix/main.c:287
  #10 0x7f6be880b421 in __libc_start_main (main=0x92f478ec50 , 
argc=10, argv=0x7ffcba605628, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffcba605618) at ../csu/libc-start.c:291
  #11 0x0092f478ec8a in _start ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1713981/+subscriptions

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1705157 ***
https://bugs.launchpad.net/bugs/1705157

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 1705157, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1705157
   "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland 
maybe Xorg)

** This bug is no longer a duplicate of bug 1705157
   "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland 
maybe Xorg)

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

** This bug has been marked a duplicate of bug 1705157
   "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland 
maybe Xorg)

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)

2017-09-05 Thread Khurshid Alam
If I install lightdm and reboot into lightdm all the sessions are
clearly visible including Gnome, Ubuntu on xorg etc and they work as the
name say.

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

Title:
  "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe
  Wayland maybe Xorg)

Status in gnome-session:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)

2017-09-05 Thread Khurshid Alam
Looks like same as bug #1714876

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

Title:
  "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe
  Wayland maybe Xorg)

Status in gnome-session:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Khurshid Alam
pcuser@artful-dev:~$ apt-cache policy gnome-session ubuntu-session

gnome-session:
  Installed: 3.25.90-0ubuntu2
  Candidate: 3.25.90-0ubuntu2
  Version table:
 *** 3.25.90-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status
ubuntu-session:
  Installed: 3.25.90-0ubuntu2
  Candidate: 3.25.90-0ubuntu2
  Version table:
 *** 3.25.90-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1702794] Re: Automatically switch audio devices on connection

2017-09-05 Thread Daniel van Vugt
It sounds like we might be able to drop module-switch-on-connect in future, as 
PulseAudio 11.0 solves the same problem by default:
  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/

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

Title:
  Automatically switch audio devices on connection

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

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

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


[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2017-09-05 Thread 潇湘居士
This bug is also present in ubuntu x86_64 14.04.5.

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+subscriptions

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


[Desktop-packages] [Bug 1714783] Re: *beta 1 release* screen scrambling upon startup.

2017-09-05 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  *beta 1 release* screen scrambling upon startup.

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

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1714783] ProcCpuinfoMinimal.txt

2017-09-05 Thread Charlie Luna
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1714783/+attachment/4945118/+files/ProcCpuinfoMinimal.txt

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1714783] GsettingsChanges.txt

2017-09-05 Thread Charlie Luna
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1714783/+attachment/4945116/+files/GsettingsChanges.txt

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1714783] JournalErrors.txt

2017-09-05 Thread Charlie Luna
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1714783/+attachment/4945117/+files/JournalErrors.txt

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1714783] Re: *beta 1 release* screen scrambling upon startup.

2017-09-05 Thread Charlie Luna
apport information

** Tags added: apport-collected

** Description changed:

  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the problem
  is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for the
  flash, it's automatic on my phone.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-09-01 (4 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
+ Package: linux
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
+ Tags:  artful
+ Uname: Linux 4.12.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1714783/+attachment/4945115/+files/Dependencies.txt

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()

2017-09-05 Thread Anders Kaseorg
This is happening to me very frequently (several times a day) on both
Wayland and Xorg.  On Wayland, it brings down the entire session.

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  shell_gtk_embed_window_created_cb() from g_closure_invoke() from
  signal_emit_unlocked_R()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 02:41:44 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (562 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
   PC (0x7feb5dff7e26) ok
   source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/gnome-shell/libgnome-shell.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

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

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


[Desktop-packages] [Bug 1715213] Re: Adopt openSUSE patch that adds high-res icons for Firefox, so the Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox icon

2017-09-05 Thread Nate Graham
** Description changed:

  Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
- Because of this, is you use KDE Plasma with the Large Icons alt-tab task
+ Because of this, if you use KDE Plasma with the Large Icons alt-tab task
  switcher, the Firefox icons look ugly: https://i.imgur.com/LdL7wlM.png
  
  openSUSE packagers patch in larger icons, and so in openSUSE, they look
  sharp and crisp: https://i.imgur.com/Le8ZhWg.png
  
  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371932
  
  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
- https://bugzilla.opensuse.org/show_bug.cgi?id=1057115
+ https://build.opensuse.org/package/view_file/openSUSE:Factory/MozillaFirefox
+ /firefox-branded-icons.patch?expand=1
+ 
+ (I have also asked the openSUSE folks to upstream their patch, though I
+ don't have high hopes that Mozilla will take it:
+ https://bugzilla.opensuse.org/show_bug.cgi?id=1057115)
  
  This way, KDE Plasma users will get nice Firefox icons in their Large
  Icons alt-tab task switchers.

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

Title:
  Adopt openSUSE patch that adds high-res icons for Firefox, so the
  Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox
  icon

Status in One Hundred Papercuts:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
  Because of this, if you use KDE Plasma with the Large Icons alt-tab
  task switcher, the Firefox icons look ugly:
  https://i.imgur.com/LdL7wlM.png

  openSUSE packagers patch in larger icons, and so in openSUSE, they
  look sharp and crisp: https://i.imgur.com/Le8ZhWg.png

  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371932

  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
  https://build.opensuse.org/package/view_file/openSUSE:Factory/MozillaFirefox
  /firefox-branded-icons.patch?expand=1

  (I have also asked the openSUSE folks to upstream their patch, though
  I don't have high hopes that Mozilla will take it:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1057115)

  This way, KDE Plasma users will get nice Firefox icons in their Large
  Icons alt-tab task switchers.

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

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


[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

2017-09-05 Thread Daniel van Vugt
Upstream says the fix is here:
https://git.gnome.org/browse/mutter/commit/?id=dd4ad4efc419e9f1f00477116fbfee8fba7fff25

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

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

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1715179] Re: gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from meta_wayland_finalize() from meta_finalize() from meta_run()

2017-09-05 Thread Daniel van Vugt
Upstream mentioned that the crashes in meta_finalize are fixed here:
https://git.gnome.org/browse/mutter/commit/?id=807658e9725bd8d3693e3a7178c72546b8835e63

But the bug mentioned in that commit seems to be the wrong bug (covers
multiple issues/fixes).

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715179

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free()
  from meta_wayland_finalize() from meta_finalize() from meta_run()

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

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1711920] Re: gnome-shell crashed with SIGTRAP in g_settings_get_value(key="multi-monitor")

2017-09-05 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  gnome-shell crashed with SIGTRAP in g_settings_get_value(key="multi-
  monitor")

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It was working fine, then I restarted and it kept crashing. Unity
  works fine though.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 20 23:54:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'telegramdesktop.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: Upgraded to artful on 2017-08-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1715179] Re: gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from meta_wayland_finalize() from meta_finalize() from meta_run()

2017-09-05 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGSEGV in __GI___libc_free()
+ gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from 
meta_wayland_finalize() from meta_finalize() from meta_run()

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free()
  from meta_wayland_finalize() from meta_finalize() from meta_run()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1715237] Re: Update to 3.18.12 in Xenial

2017-09-05 Thread Jeremy Bicha
** Also affects: epiphany-browser (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: epiphany-browser (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: epiphany-browser (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: epiphany-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: epiphany-browser (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to 3.18.12 in Xenial

Status in Epiphany Browser:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in epiphany-browser source package in Xenial:
  Triaged

Bug description:
  [Impact]

  Upstream released 3.18.12. Xenial and derivatives will benefit from
  these fixes.

  https://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-18
  https://git.gnome.org/browse/epiphany/log/?h=gnome-3-18

  Epiphany 3.18.12
  

  - Fix adblocker blocking too much (#14, #787011)
  - Fix numerous history bugs, e.g. search provider breaking history (#778649)
  - Fix some memory corruption (#779180)
  - Fix security popover crash (#785338)

  [Test Case]

  Install the update. Ensure that the browser still works. Navigate to
  different sites.

  [Regression Potential]

  This is a new bug-fix release in the stable 3.18.x series. Upstream
  cherry-picks the fixes that they believe are important. Since these
  are only bug fixes, the regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/1715237/+subscriptions

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


[Desktop-packages] [Bug 1715266] Re: package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': Read-only file sy

2017-09-05 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 liblouis in Ubuntu.
https://bugs.launchpad.net/bugs/1715266

Title:
  package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable
  to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-
  new': Read-only file system

Status in liblouis package in Ubuntu:
  New

Bug description:
  had a hardrive error.  fixed with fsck manually on reboot.  next boot
  got this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblouis12 3.0.0-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   liblouis-data:amd64: Install
   liblouis12:amd64: Install
   python3-louis:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Sep  5 01:44:59 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   liblouis-data 3.0.0-3ubuntu0.2
  DpkgHistoryLog:
   Start-Date: 2017-09-05  01:44:58
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: liblouis12:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2), python3-louis:amd64 
(3.0.0-3, 3.0.0-3ubuntu0.2), liblouis-data:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2)
  DuplicateSignature:
   package:liblouis12:3.0.0-3ubuntu0.2
   Unpacking liblouis-data (3.0.0-3ubuntu0.2) over (3.0.0-3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblouis-data_3.0.0-3ubuntu0.2_all.deb (--unpack):
unable to securely remove 
'/usr/share/doc/liblouis-data/changelog.Debian.gz.dpkg-new': Read-only file 
system
  ErrorMessage: unable to securely remove 
'/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': Read-only file system
  InstallationDate: Installed on 2016-10-16 (324 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblouis
  Title: package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable 
to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': 
Read-only file system
  UpgradeStatus: Upgraded to zesty on 2017-07-25 (42 days ago)

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

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


[Desktop-packages] [Bug 1715266] [NEW] package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': Read-only file

2017-09-05 Thread Brooke
Public bug reported:

had a hardrive error.  fixed with fsck manually on reboot.  next boot
got this.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblouis12 3.0.0-3ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 liblouis-data:amd64: Install
 liblouis12:amd64: Install
 python3-louis:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Sep  5 01:44:59 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 liblouis-data 3.0.0-3ubuntu0.2
DpkgHistoryLog:
 Start-Date: 2017-09-05  01:44:58
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: liblouis12:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2), python3-louis:amd64 
(3.0.0-3, 3.0.0-3ubuntu0.2), liblouis-data:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2)
DuplicateSignature:
 package:liblouis12:3.0.0-3ubuntu0.2
 Unpacking liblouis-data (3.0.0-3ubuntu0.2) over (3.0.0-3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/liblouis-data_3.0.0-3ubuntu0.2_all.deb (--unpack):
  unable to securely remove 
'/usr/share/doc/liblouis-data/changelog.Debian.gz.dpkg-new': Read-only file 
system
ErrorMessage: unable to securely remove 
'/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': Read-only file system
InstallationDate: Installed on 2016-10-16 (324 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: liblouis
Title: package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable to 
securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': 
Read-only file system
UpgradeStatus: Upgraded to zesty on 2017-07-25 (42 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable
  to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-
  new': Read-only file system

Status in liblouis package in Ubuntu:
  New

Bug description:
  had a hardrive error.  fixed with fsck manually on reboot.  next boot
  got this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblouis12 3.0.0-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   liblouis-data:amd64: Install
   liblouis12:amd64: Install
   python3-louis:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Sep  5 01:44:59 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   liblouis-data 3.0.0-3ubuntu0.2
  DpkgHistoryLog:
   Start-Date: 2017-09-05  01:44:58
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: liblouis12:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2), python3-louis:amd64 
(3.0.0-3, 3.0.0-3ubuntu0.2), liblouis-data:amd64 (3.0.0-3, 3.0.0-3ubuntu0.2)
  DuplicateSignature:
   package:liblouis12:3.0.0-3ubuntu0.2
   Unpacking liblouis-data (3.0.0-3ubuntu0.2) over (3.0.0-3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblouis-data_3.0.0-3ubuntu0.2_all.deb (--unpack):
unable to securely remove 
'/usr/share/doc/liblouis-data/changelog.Debian.gz.dpkg-new': Read-only file 
system
  ErrorMessage: unable to securely remove 
'/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': Read-only file system
  InstallationDate: Installed on 2016-10-16 (324 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblouis
  Title: package liblouis12 3.0.0-3ubuntu0.2 failed to install/upgrade: unable 
to securely remove '/usr/lib/x86_64-linux-gnu/liblouis.so.12.0.0.dpkg-new': 
Read-only file system
  UpgradeStatus: Upgraded to zesty on 2017-07-25 (42 days ago)

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

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


[Desktop-packages] [Bug 1706500] Re: Update snap store name "Ubuntu Store"

2017-09-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Update snap store name "Ubuntu Store"

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Currently various things are shown for the snap "Source" field:
  3.20: "Ubuntu Snappy Store" - hard-coded
  3.22 / 3.24: "dashboard.snapcraft.io" - is inferred from the snap metadata
  The officially decided store name is "Ubuntu Store" and this should show in 
this field.

  [Test Case]
  1. Open GNOME Software.
  2. Install a snap (e.g. moon-buggy).
  3. Select installed tab.
  4. Look at the "Source" field when looking at the app details.

  Expected result:
  The source is "Ubuntu Store"

  Observed result:
  The source is something else.

  [Regression Potential]
  Small risk of breaking existing code.

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

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


[Desktop-packages] [Bug 1706043] Re: /usr/bin/gnome-software:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_insert_internal:gs_plugin_loader_add_event:gs_plugin_loader_create_event_from_error

2017-09-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  /usr/bin/gnome-
  
software:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_insert_internal:gs_plugin_loader_add_event:gs_plugin_loader_create_event_from_error

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  New defect in artful which started with 3.24.3-0ubuntu1 and in the top
  5 weekly crashes for the desktop packages set.

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

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

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


[Desktop-packages] [Bug 1706500] Re: Update snap store name "Ubuntu Store"

2017-09-05 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Artful)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Update snap store name "Ubuntu Store"

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Currently various things are shown for the snap "Source" field:
  3.20: "Ubuntu Snappy Store" - hard-coded
  3.22 / 3.24: "dashboard.snapcraft.io" - is inferred from the snap metadata
  The officially decided store name is "Ubuntu Store" and this should show in 
this field.

  [Test Case]
  1. Open GNOME Software.
  2. Install a snap (e.g. moon-buggy).
  3. Select installed tab.
  4. Look at the "Source" field when looking at the app details.

  Expected result:
  The source is "Ubuntu Store"

  Observed result:
  The source is something else.

  [Regression Potential]
  Small risk of breaking existing code.

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

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


[Desktop-packages] [Bug 1715264] [NEW] shutdown system dialog installation hangs

2017-09-05 Thread Humphrey van Polanen Petel
Public bug reported:

Ubuntu Software Center offers Shutdown System Dialog.
This means that it is deemed compatible with Ubuntu.
The description refers to the Mate desktop -- is that a worry?
Version to be installed is mate-gnome-main-menu-applet 1.8.0-5build1

Problem is that the install hangs halfway through (see attached).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-center 16.01+16.04.20160420
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep  6 09:52:11 2017
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2017-07-27 (40 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Selection_025.jpg"
   
https://bugs.launchpad.net/bugs/1715264/+attachment/4945047/+files/Selection_025.jpg

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

Title:
  shutdown system dialog installation hangs

Status in software-center package in Ubuntu:
  New

Bug description:
  Ubuntu Software Center offers Shutdown System Dialog.
  This means that it is deemed compatible with Ubuntu.
  The description refers to the Mate desktop -- is that a worry?
  Version to be installed is mate-gnome-main-menu-applet 1.8.0-5build1

  Problem is that the install hangs halfway through (see attached).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center 16.01+16.04.20160420
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  6 09:52:11 2017
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2017-07-27 (40 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1706500] Re: Update snap store name "Ubuntu Store"

2017-09-05 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => Fix Committed

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

Title:
  Update snap store name "Ubuntu Store"

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Currently various things are shown for the snap "Source" field:
  3.20: "Ubuntu Snappy Store" - hard-coded
  3.22 / 3.24: "dashboard.snapcraft.io" - is inferred from the snap metadata
  The officially decided store name is "Ubuntu Store" and this should show in 
this field.

  [Test Case]
  1. Open GNOME Software.
  2. Install a snap (e.g. moon-buggy).
  3. Select installed tab.
  4. Look at the "Source" field when looking at the app details.

  Expected result:
  The source is "Ubuntu Store"

  Observed result:
  The source is something else.

  [Regression Potential]
  Small risk of breaking existing code.

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

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


[Desktop-packages] [Bug 1715213] Re: Adopt openSUSE patch that adds high-res icons for Firefox, so the Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox icon

2017-09-05 Thread Simon Quigley
** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

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

Title:
  Adopt openSUSE patch that adds high-res icons for Firefox, so the
  Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox
  icon

Status in One Hundred Papercuts:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
  Because of this, is you use KDE Plasma with the Large Icons alt-tab
  task switcher, the Firefox icons look ugly:
  https://i.imgur.com/LdL7wlM.png

  openSUSE packagers patch in larger icons, and so in openSUSE, they
  look sharp and crisp: https://i.imgur.com/Le8ZhWg.png

  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371932

  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1057115

  This way, KDE Plasma users will get nice Firefox icons in their Large
  Icons alt-tab task switchers.

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

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


[Desktop-packages] [Bug 1706500] Re: Update snap store name "Ubuntu Store"

2017-09-05 Thread Robert Ancell
commit 6d4b2dee2d3f5d36c7b1b518ac54ee6e2c354313
Author: Robert Ancell 
Date:   Wed Sep 6 11:09:45 2017 +1200

snap: Correct the app origin

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

Title:
  Update snap store name "Ubuntu Store"

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  [Impact]
  Currently various things are shown for the snap "Source" field:
  3.20: "Ubuntu Snappy Store" - hard-coded
  3.22 / 3.24: "dashboard.snapcraft.io" - is inferred from the snap metadata
  The officially decided store name is "Ubuntu Store" and this should show in 
this field.

  [Test Case]
  1. Open GNOME Software.
  2. Install a snap (e.g. moon-buggy).
  3. Select installed tab.
  4. Look at the "Source" field when looking at the app details.

  Expected result:
  The source is "Ubuntu Store"

  Observed result:
  The source is something else.

  [Regression Potential]
  Small risk of breaking existing code.

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

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


[Desktop-packages] [Bug 1715255] [NEW] libreoffice has uninstalled, will not launch or open documents.

2017-09-05 Thread Kendra Moyer
Public bug reported:

I am using Ubuntu 17.04 and libreoffice has uninstalled making it so I
cannot make written documents.  I am recently having trouble with
loading new software in ubuntu 17.04 through the command line and
through the ubuntu app store.

ProblemType: Bug
DistroRelease: Kali 2017.1
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Sep  5 18:46:58 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-03-23 (166 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kali-rolling

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

Title:
  libreoffice has uninstalled, will not launch or open documents.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 17.04 and libreoffice has uninstalled making it so I
  cannot make written documents.  I am recently having trouble with
  loading new software in ubuntu 17.04 through the command line and
  through the ubuntu app store.

  ProblemType: Bug
  DistroRelease: Kali 2017.1
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Sep  5 18:46:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-23 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  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/1715255/+subscriptions

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


[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)

2017-09-05 Thread Bug Watch Updater
** Changed in: gnome-session
   Status: Unknown => Confirmed

** Changed in: gnome-session
   Importance: Unknown => Medium

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

Title:
  "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe
  Wayland maybe Xorg)

Status in gnome-session:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1715237] Re: Update to 3.18.12 in Xenial

2017-09-05 Thread Bug Watch Updater
** Changed in: epiphany-browser
   Status: Unknown => Fix Released

** Changed in: epiphany-browser
   Importance: Unknown => Wishlist

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

Title:
  Update to 3.18.12 in Xenial

Status in Epiphany Browser:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  [Impact]

  Upstream released 3.18.12. Xenial and derivatives will benefit from
  these fixes.

  https://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-18
  https://git.gnome.org/browse/epiphany/log/?h=gnome-3-18

  Epiphany 3.18.12
  

  - Fix adblocker blocking too much (#14, #787011)
  - Fix numerous history bugs, e.g. search provider breaking history (#778649)
  - Fix some memory corruption (#779180)
  - Fix security popover crash (#785338)

  [Test Case]

  Install the update. Ensure that the browser still works. Navigate to
  different sites.

  [Regression Potential]

  This is a new bug-fix release in the stable 3.18.x series. Upstream
  cherry-picks the fixes that they believe are important. Since these
  are only bug fixes, the regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/1715237/+subscriptions

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


[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-05 Thread Adam Smith
Not in Ubuntu.  The link above is from March.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1714634] Re: starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000]

2017-09-05 Thread Robert Ancell
Please re-open if it re-occurs.

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

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

Title:
  starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4
  in libc-2.24.so[b6413000+1b3000]

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  In: xubuntu-17.10-beta1-desktop-i386.iso, running in 'Try Ubuntu'.

  Everytime I try to start gnome-software I get nothing except this error in 
dmesg:
  [  388.510237] gnome-software[4251]: segfault at 0 ip b64548e6 sp bffaa1c8 
error 4 in libc-2.24.so[b63c4000+1b3000]
  [  672.893089] gnome-software[4400]: segfault at 0 ip b650a8e6 sp bfdb6e68 
error 4 in libc-2.24.so[b647a000+1b3000]
  [  735.140781] gnome-software[4464]: segfault at 0 ip b648f8e6 sp bfa5aaa8 
error 4 in libc-2.24.so[b63ff000+1b3000]
  [  859.557640] gnome-software[4474]: segfault at 0 ip b64a38e6 sp bffe1d68 
error 4 in libc-2.24.so[b6413000+1b3000]

  apport does not seems to catch it:
  xubuntu@xubuntu:~$ apport-cli
  Aucun rapport de plantage en attente. Essayer --help pour plus d'informations.
  (no report)

  (gdb) run
  Starting program: /usr/bin/gnome-software 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
  [New Thread 0xb39b0b40 (LWP 4665)]
  [New Thread 0xb2fffb40 (LWP 4666)]
  [New Thread 0xb25ffb40 (LWP 4667)]
  [New Thread 0xb1032b40 (LWP 4668)]

  Thread 1 "gnome-software" received signal SIGSEGV, Segmentation fault.
  __strchr_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S:60
  60../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S: Aucun fichier ou 
dossier de ce type.
  (gdb) bt
  #0  __strchr_sse2_bsf () at 
../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S:60
  #1  0xb7e84f7e in g_param_spec_pool_lookup ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #2  0xb7e7fe07 in g_object_new_valist ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #3  0xb7e802a9 in g_object_new ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #4  0x0043af6c in ?? ()
  #5  0x00447313 in gs_shell_change_mode ()
  #6  0x00449d1f in gs_shell_set_mode ()
  #7  0x00423af3 in ?? ()
  #8  0xb7e78d08 in g_closure_invoke ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #9  0xb7e8bb95 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #10 0xb7e94bf3 in g_signal_emit_valist ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #11 0xb7e953a5 in g_signal_emit ()
 from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #12 0xb7bf4330 in g_application_activate ()
 from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  #13 0xb7bf4b13 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  #14 0xb7bf4d3f in g_application_run ()
 from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  ---Type  to continue, or q  to quit---

  CPU supports SSE2:
  xubuntu@xubuntu:~$ cat /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 15
  model : 75
  model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
  stepping  : 2
  microcode : 0x62
  cpu MHz   : 1000.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fdiv_bug  : no
  f00f_bug  : no
  coma_bug  : no
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 1
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 
3dnowext 3dnow rep_good cpuid pni cx16 lahf_lm cmp_legacy svm extapic 
cr8_legacy 3dnowprefetch vmmcall
  bugs  : fxsave_leak sysret_ss_attrs swapgs_fence amd_e400
  bogomips  : 2009.18
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 40 bits physical, 48 bits virtual
  power management: ts fid vid ttp tm stc

  processor : 1
  vendor_id : AuthenticAMD
  cpu family: 15
  model : 75
  model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
  stepping  : 2
  microcode : 0x62
  cpu MHz   : 1000.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 1
  cpu cores : 2
  apicid: 1
  initial apicid: 1
  fdiv_bug  : no
  f00f_bug  : no
  coma_bug  : no
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 1
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 
3dnowext 3dnow rep_good cpuid pni cx16 lahf_lm cmp_legacy svm extapic 
cr8_legacy 3dnowprefetch vmmcall
  bugs  : fxsave_leak sysret_ss_attrs 

[Desktop-packages] [Bug 1699216] Re: Encrypted home support

2017-09-05 Thread Jeremy Soller
tsimonq2, I have subscribed ubuntu-release. We have modifications in our
PPA that utilize this patch to accountsservice. If the patch to
accountsservice is not merged in Ubuntu's version, our version will be
overridden when there is another accountsservice release.

Since this is a feature that is desired in Ubuntu, I think it would be
best to allow for the patch to accountsservice to be merged in for use
by others, regardless of the patches to gnome-control-center or gnome-
initial-setup. At the moment, we have a safely forked version of these
packages that cannot be overridden.

The issue with accountservice, is that it cannot be forked, renamed, and
then use a Provides Conflicts Replaces. This leaves us in a dangerous
place where we may have to revert our changes to add encrypted home to
gnome-control-center and gnome-initial-setup.

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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


[Desktop-packages] [Bug 1699216] Re: Encrypted home support

2017-09-05 Thread Simon Quigley
@Jeremy:

If you get a Feature Freeze Exception as defined here[1] or an ack from
a member of the release team, I'll be happy to get it uploaded for you.

I want to upload your patches, I just don't want to break freeze and
have to apologize to the release team... sorry. :/

[1] https://wiki.ubuntu.com/FreezeExceptionProcess

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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


[Desktop-packages] [Bug 1715237] [NEW] Update to 3.18.12 in Xenial

2017-09-05 Thread Amr Ibrahim
Public bug reported:

[Impact]

Upstream released 3.18.12. Xenial and derivatives will benefit from
these fixes.

https://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-18
https://git.gnome.org/browse/epiphany/log/?h=gnome-3-18

Epiphany 3.18.12


- Fix adblocker blocking too much (#14, #787011)
- Fix numerous history bugs, e.g. search provider breaking history (#778649)
- Fix some memory corruption (#779180)
- Fix security popover crash (#785338)

[Test Case]

Install the update. Ensure that the browser still works. Navigate to
different sites.

[Regression Potential]

This is a new bug-fix release in the stable 3.18.x series. Upstream
cherry-picks the fixes that they believe are important. Since these are
only bug fixes, the regression is low.

** Affects: epiphany-browser
 Importance: Unknown
 Status: Unknown

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


** Tags: upgrade-software-version xenial

** Bug watch added: GNOME Bug Tracker #787316
   https://bugzilla.gnome.org/show_bug.cgi?id=787316

** Also affects: epiphany-browser via
   https://bugzilla.gnome.org/show_bug.cgi?id=787316
   Importance: Unknown
   Status: Unknown

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

Title:
  Update to 3.18.12 in Xenial

Status in Epiphany Browser:
  Unknown
Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  [Impact]

  Upstream released 3.18.12. Xenial and derivatives will benefit from
  these fixes.

  https://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-18
  https://git.gnome.org/browse/epiphany/log/?h=gnome-3-18

  Epiphany 3.18.12
  

  - Fix adblocker blocking too much (#14, #787011)
  - Fix numerous history bugs, e.g. search provider breaking history (#778649)
  - Fix some memory corruption (#779180)
  - Fix security popover crash (#785338)

  [Test Case]

  Install the update. Ensure that the browser still works. Navigate to
  different sites.

  [Regression Potential]

  This is a new bug-fix release in the stable 3.18.x series. Upstream
  cherry-picks the fixes that they believe are important. Since these
  are only bug fixes, the regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/1715237/+subscriptions

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


[Desktop-packages] [Bug 1714890] Re: tibetan unicode font rendering not correct.

2017-09-05 Thread Brian Murray
** Tags added: regression-update

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

Title:
  tibetan unicode font rendering not correct.

Status in firefox package in Ubuntu:
  New

Bug description:
  With ubuntu-16.04.3-desktop-amd64.iso fresh install firefox show wrong font 
rendering (test-hung.html)
  openoffice, gedit shows it correct
  The same error after all updates.

  With ubuntu-16.04.1-desktop-amd64.iso fresh install all programs show the 
correct rendering.
  with the update of firefox from verion 50.0 to 51.0 the wrong form is 
appearing only in firefox

  With ubuntu-17.04-desktop-amd64.iso fresh install then firefox,
  openoffice, gedit all show the wrong rendering. This bug stays after
  all updates.

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

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


[Desktop-packages] [Bug 1715229] Re: gnome-shell crashed with SIGSEGV in g_closure_invoke()

2017-09-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1714330 ***
https://bugs.launchpad.net/bugs/1714330

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in g_closure_invoke()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Can't tell which of the issues I am facing with gnome shell belongs to this 
auto generated bug-report.
  It might be related to the following behaviour:
  Sometimes I get logged out during normal usage (browsing, emails, file 
browser) - I think it happens when I use alt+tab.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Sep  5 21:21:28 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-04-15 (143 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3e90edc836:mov0x1a0(%rax),%rax
   PC (0x7f3e90edc836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1715019] Re: Gnome-Shell on Wayland Poweroff system menu button not working

2017-09-05 Thread Jean-Baptiste Lallement
Thank you Carla for following-up. I'm closing this report and as usual
don't hesitate to submit any bug you may find.

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

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1715139] package brltty 5.3.1-2ubuntu2 [modified: lib/brltty/libbrlttybbl.so lib/brltty/libbrlttybhw.so lib/brltty/libbrlttyxlx.so] failed to install/upgrade: package brltty is

2017-09-05 Thread Brian Murray
*** This bug is a duplicate of bug 1643117 ***
https://bugs.launchpad.net/bugs/1643117

DuplicateSignature:
 Processing triggers for man-db (2.7.5-1) ...
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package brltty (--configure):
  package brltty is not ready for configuration

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

Title:
  package brltty 5.3.1-2ubuntu2 [modified: lib/brltty/libbrlttybbl.so
  lib/brltty/libbrlttybhw.so lib/brltty/libbrlttyxlx.so] failed to
  install/upgrade: package brltty is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in brltty package in Ubuntu:
  New

Bug description:
  problems while installing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: brltty 5.3.1-2ubuntu2 [modified: lib/brltty/libbrlttybbl.so 
lib/brltty/libbrlttybhw.so lib/brltty/libbrlttyxlx.so]
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   udev: Install
   brltty: Configure
   udev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Sep  5 17:36:32 2017
  DuplicateSignature:
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package brltty (--configure):
package brltty is not ready for configuration
  ErrorMessage: package brltty is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-09-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: brltty
  Title: package brltty 5.3.1-2ubuntu2 [modified: lib/brltty/libbrlttybbl.so 
lib/brltty/libbrlttybhw.so lib/brltty/libbrlttyxlx.so] failed to 
install/upgrade: package brltty is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Brad Figg
I'm also seeing odd scaling issues with the recent update. What's
interesting is that once I bring up gnome-tweak-tool all my scaling
issues "go away" the title bars, fonts, login screen etc. are "fixed"
and properly scaled.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 13:03:53 2017
  InstallationDate: Installed on 2017-07-30 (27 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-05 Thread Alexander Karlstad
This has been happening to me lately. I am using 17.04.

I have a feeling it might be IPv6 related since we just started using
that at work, so it's only affecting me there. Usually I see the
following in my syslog:

> Sep  5 15:40:46 laptop avahi-daemon[1158]: Withdrawing address record for 
> 1234:5678:4556::99 on eth0.
> Sep  5 15:40:46 laptop avahi-daemon[1158]: Leaving mDNS multicast group on 
> interface eth0.IPv6 with address 1234:5678:4556::99.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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


[Desktop-packages] [Bug 1715019] Re: Gnome-Shell on Wayland Poweroff system menu button not working

2017-09-05 Thread Carla Sella
Hi Guys,
Thanks for your help.
I solved the problem uninstalling the "Suspend button" extension (I had 
forgotten it was installed).
Carla

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1715213] [NEW] Adopt openSUSE patch that adds high-res icons for Firefox, so the Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox icon

2017-09-05 Thread Nate Graham
Public bug reported:

Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
Because of this, is you use KDE Plasma with the Large Icons alt-tab task
switcher, the Firefox icons look ugly: https://i.imgur.com/LdL7wlM.png

openSUSE packagers patch in larger icons, and so in openSUSE, they look
sharp and crisp: https://i.imgur.com/Le8ZhWg.png

I have opened a ticket with Mozilla, but it has been ignored:
https://bugzilla.mozilla.org/show_bug.cgi?id=1371932

So until they fix it upstream, we may want to consider adopting the
openSUSE patch in Ubuntu:
https://bugzilla.opensuse.org/show_bug.cgi?id=1057115

This way, KDE Plasma users will get nice Firefox icons in their Large
Icons alt-tab task switchers.

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

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

Title:
  Adopt openSUSE patch that adds high-res icons for Firefox, so the
  Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox
  icon

Status in firefox package in Ubuntu:
  New

Bug description:
  Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
  Because of this, is you use KDE Plasma with the Large Icons alt-tab
  task switcher, the Firefox icons look ugly:
  https://i.imgur.com/LdL7wlM.png

  openSUSE packagers patch in larger icons, and so in openSUSE, they
  look sharp and crisp: https://i.imgur.com/Le8ZhWg.png

  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371932

  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1057115

  This way, KDE Plasma users will get nice Firefox icons in their Large
  Icons alt-tab task switchers.

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

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


[Desktop-packages] [Bug 1715211] Re: gvfsd-smb-browse crashed with signal 7

2017-09-05 Thread Apport retracing service
** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-smb-browse crashed with signal 7

Status in gvfs package in Ubuntu:
  New

Bug description:
  It crashed while the Preferences of epiphany-browser was opening.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep  5 20:17:44 2017
  Disassembly: => 0x7ff3b2702fb6:   Cannot access memory at address 
0x7ff3b2702fb6
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-06-21 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 
/org/gtk/gvfs/exec_spaw/3
  Signal: 7
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-smb-browse crashed with signal 7
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-05 Thread NJ
On my Mint (18.2 and I think I did it on 18.3 too - both Cinnamon) the
network-manager downgrade sufficed; I did not need to adjust resolvconf.
However, I don't think I was using a 'PPTP tunnel'.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1715211] [NEW] gvfsd-smb-browse crashed with signal 7

2017-09-05 Thread Amr Ibrahim
Public bug reported:

It crashed while the Preferences of epiphany-browser was opening.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Sep  5 20:17:44 2017
Disassembly: => 0x7ff3b2702fb6: Cannot access memory at address 0x7ff3b2702fb6
ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
InstallationDate: Installed on 2017-06-21 (75 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 
/org/gtk/gvfs/exec_spaw/3
Signal: 7
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-smb-browse crashed with signal 7
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Information type changed from Private to Public

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

Title:
  gvfsd-smb-browse crashed with signal 7

Status in gvfs package in Ubuntu:
  New

Bug description:
  It crashed while the Preferences of epiphany-browser was opening.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep  5 20:17:44 2017
  Disassembly: => 0x7ff3b2702fb6:   Cannot access memory at address 
0x7ff3b2702fb6
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-06-21 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 
/org/gtk/gvfs/exec_spaw/3
  Signal: 7
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-smb-browse crashed with signal 7
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-05 Thread herrtimson
No, people go back to 52 because it is working and it is under active
developement, hence gets sec. updates. firefox 53 and 54 branches are
stalled, they are very likely vulnerable.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-05 Thread Adam Smith
On the Mozilla bug people are saying they had 54 working, but there was
no 53 or 54 on armhf in Ubuntu?  That is why people are rolling back to
52 isn't it?

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-05 Thread dlotton
Just an FYI, I have to downgrade both network-manager=1.2.2-0ubuntu0.16.04.4 
and resolvconf=1.78ubuntu2.  Doing one or the other would not fix the problem 
on my system (Linux Mint Mate 18.1).
 
I'm using a PPTP tunnel.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-05 Thread Shawn B
Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue
is resolved. Pretty simple.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-05 Thread NJ
@lukas-d: I understand, but perhaps you are thinking that I work for
Canonical or that I have the skill to contribute to the network-manager
project. Neither of those things are true. I am a frustrated user (with
fairly low programming ability).

It seems to me that switching to a distribution that is not Ubuntu and
is not based on Ubuntu might be an idea, in your circumstances.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1715188] [NEW] Artist / Album folder names not renamed after correcting ID3 tags (as Banshee does)

2017-09-05 Thread indigocat
Public bug reported:

When adding music files, they're stored under folders that follow the
original Artist / Album names, and aren't renamed after the new,
corrected names.

Example:

-I add a 10-song album, named "Frop", by "Bob Dobbs", with songs named A, B, 
C...H, I, and J.
-In the ID3 tag, the artist name isn't "Bob Dobbs", but "Dob Bobbs", and the 
album name "Frop" is misspelled as "Prof".

-In the Music Library Folder, songs are stored under folder structure Music/Dob 
Bobbs/Prof/
-In Rhythmbox, I correct ID3 tags, so artist name is "Bob Dobbs", album name is 
"Frop".

-Expected: directory structure changes from Music/Dob Bobbs/Prof/ to Music/Bob 
Dobbs/Frop/ 
-What happens: directory structure is *still* Music/Dob Bobbs/Prof/

In Banshee, this directory structure is renamed after the ID3 tags. Rhythmbox 
doesn't seem to do this.
I want to switch to Rhythmbox because it's still maintained and uses less 
memory, unlike Banshee.


I'm using elementary OS Loki, based on Ubuntu 16.04 LTS.
Rhythmox version is 3.4.0.

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

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

Title:
  Artist / Album folder names not renamed after correcting ID3 tags (as
  Banshee does)

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  When adding music files, they're stored under folders that follow the
  original Artist / Album names, and aren't renamed after the new,
  corrected names.

  Example:

  -I add a 10-song album, named "Frop", by "Bob Dobbs", with songs named A, B, 
C...H, I, and J.
  -In the ID3 tag, the artist name isn't "Bob Dobbs", but "Dob Bobbs", and the 
album name "Frop" is misspelled as "Prof".

  -In the Music Library Folder, songs are stored under folder structure 
Music/Dob Bobbs/Prof/
  -In Rhythmbox, I correct ID3 tags, so artist name is "Bob Dobbs", album name 
is "Frop".

  -Expected: directory structure changes from Music/Dob Bobbs/Prof/ to 
Music/Bob Dobbs/Frop/ 
  -What happens: directory structure is *still* Music/Dob Bobbs/Prof/

  In Banshee, this directory structure is renamed after the ID3 tags. Rhythmbox 
doesn't seem to do this.
  I want to switch to Rhythmbox because it's still maintained and uses less 
memory, unlike Banshee.

  
  I'm using elementary OS Loki, based on Ubuntu 16.04 LTS.
  Rhythmox version is 3.4.0.

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

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


[Desktop-packages] [Bug 1715153] Re: FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Jeremy Bicha
This bug was fixed in the package clutter-1.0 - 1.26.2+dfsg-3

---
clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

  * Release to unstable
  * debian/control.in:
- Drop Build-Depends on libgl1-mesa-dri
  * debian/rules:
- Ignore test failures on Debian. See bug 874077.

  * Allow tests to fail the build on Ubuntu. The tests fail in Debian.

 -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

  * Convert from cdbs to dh
  * Bump debhelper compat to 10
  * Add debian/libclutter-1.0-0.docs to install NEWS and README
  * Convert to automatic dbgsym package
  * Add autopkgtest to run clutter-1.0-tests
  * debian/control.in:
- Build-depend on dbus for build tests
- Build-depend on libgl1-mesa-dri for build tests since Debian's
  libgl1-mesa-glx currently only recommends it
  * debian/rules:
- Allow tests to not fail the build this time
  * Add debian/patches/skip-failing-tests.patch:
- Skip failing test so that we can run all the other tests

 -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

** Changed in: clutter-1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  Fix Released

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

-- 
Mailing list: https://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 1715153] Re: FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Iain Lane
On Tue, Sep 05, 2017 at 02:42:38PM -, Jeremy Bicha wrote:
> I tested that the new version builds in an artful PPA. (Test failures
> are still ignored on s390x since 1 or tests fail there and I didn't know
> a way to better selectively ignore specific test failures by arch.)

Do it in the code - make the test call g_test_skip() when appropriate.

The changes look ok, please go ahead.

BTW, you can debdiff amd64.changes files to get all the changes in one
go, if you have the old one around or don't mind rebuilding to get it or
clicking a lot on Launchpad.

 status confirmed

Cheers,

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


** Changed in: clutter-1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  Confirmed

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

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


[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

2017-09-05 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => Confirmed

** Changed in: mutter
   Importance: Unknown => 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/1714330

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

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

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 157690] Fw: Make money using affiliate programs

2017-09-05 Thread orowitz
*** This bug is a duplicate of bug 86698 ***
https://bugs.launchpad.net/bugs/86698

When I started my first blog online,  I really had no intention of making any 
money from it. I started  writing my  first blog simply because  I thought it 
was fun.
However, I started to  learn about how much  money can actually be  made 
online, which is when I started to get serious about learning how to make that 
happen. The biggest windfall in my business is learning  how to make money 
using  affiliate programs.
read more  here 
http://farstone.in/top_dengi_n2x.php?m=EMTU3NjkwQGJ1Z3MubGF1bmNocGFkLm5ldA--

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

Title:
  update-manager crashed with SIGSEGV in
  gtk_text_view_check_keymap_direction()

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Binary package hint: update-manager

  install and restart

  ProblemType: Crash
  Architecture: i386
  Date: Sat Oct  6 22:36:02 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/update-manager
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: cdrom
  Package: update-manager 1:0.80
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
  ProcCwd: /root
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: update-manager
  StacktraceTop:
   gtk_text_view_check_keymap_direction (text_view=0x85f3808)
   gtk_text_view_ensure_layout (text_view=0x85f3808)
   gtk_text_view_update_layout_width (text_view=0x0)
   gtk_text_view_value_changed (adj=0x0, text_view=0x85f3808)
   _gtk_marshal_VOID__OBJECT_OBJECT (closure=0x85f05a0,
  Title: update-manager crashed with SIGSEGV in 
gtk_text_view_check_keymap_direction()
  Uname: Linux Ubuntu710GustyGibbonBeta 2.6.22-13-generic #1 SMP Thu Oct 4 
17:18:44 GMT 2007 i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev scanner 
tape

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/157690/+subscriptions

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


[Desktop-packages] [Bug 1715179] ThreadStacktrace.txt

2017-09-05 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1715179/+attachment/4944803/+files/ThreadStacktrace.txt

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

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

** Summary changed:

- gnome-shell crashed with SIGSEGV in free()
+ gnome-shell crashed with SIGSEGV in __GI___libc_free()

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1715179] Stacktrace.txt

2017-09-05 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1715179/+attachment/4944801/+files/Stacktrace.txt

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1715179] StacktraceSource.txt

2017-09-05 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1715179/+attachment/4944802/+files/StacktraceSource.txt

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1715179] gnome-shell crashed with SIGSEGV in free()

2017-09-05 Thread Apport retracing service
StacktraceTop:
 __GI___libc_free (mem=0x18160562e9) at malloc.c:2984
 g_free (mem=) at ../../../../glib/gmem.c:189
 meta_wayland_finalize () at wayland/meta-wayland.c:409
 meta_finalize () at core/main.c:301
 meta_run () at core/main.c:650

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Rachel Greenham
I care slightly less than I used to because I just now persuaded ubuntu
wayland session to run on nvidia-384 proprietary drivers. :-) Something
which I presume is intended to be the default behaviour at some point,
or at least for Nouveau.

So since I reported this bug the move to gnome 3.25 has made it
possible, for me at least, to leave Xorg behind, along with problems
like this. I'm sure you'll have plenty of people who can't, or won't,
for one reason or another, but I'm not one of them. nouveau and nvidia
didn't work with wayland out of the box though; I had to pick up hints
from archlinux forums and suchlike to figure out the necessary
incantations. Presumably that'll get ironed out before release ;-)
because now it's working it seems fine, apart from a minor redraw glitch
while dragging windows larger, which if I'm going to make anything of
I'll report elsewhere.

Final note though: The new 3.25 gnome-control-center was necessary to
actually select the correct desktop scaling factor, and that's still
only in gnome3-staging. (If there's a gsettings key for that new
setting, I can't find it.)

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of 

[Desktop-packages] [Bug 1715179] [NEW] gnome-shell crashed with SIGSEGV in __GI___libc_free()

2017-09-05 Thread Jean-Baptiste Lallement
Public bug reported:

Ubuntu Artful Desktop up to date

Test Case
1. Login with wayland
2. Logout
3. Login with X
4. Logout
5. Repeat from step 1 until this crash happens

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  5 16:28:07 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2014-07-23 (1140 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5f3bde9d52 :mov(%rax),%rdi
 PC (0x7f5f3bde9d52) ok
 source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 free () from /lib/x86_64-linux-gnu/libc.so.6
 meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: gnome-shell crashed with SIGSEGV in free()
UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in __GI___libc_free()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Artful Desktop up to date

  Test Case
  1. Login with wayland
  2. Logout
  3. Login with X
  4. Logout
  5. Repeat from step 1 until this crash happens

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 16:28:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1140 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5f3bde9d52 :  mov(%rax),%rdi
   PC (0x7f5f3bde9d52) ok
   source "(%rax)" (0x181400) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in free()
  UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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


[Desktop-packages] [Bug 1715013] Re: Wired Network Stops Working

2017-09-05 Thread Jean-Baptiste Lallement
** Tags removed: wayland-session

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

Title:
  Wired Network Stops Working

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi, this is the second bug I report, and I hope I'm reporting that one
  in a better way than the first, I'm including a report at least this
  time xD

  The thing is that sometimes wired network stops working and needs to
  be turned off and on to get it back to the work. It's happening weeks
  ago, is not a recent problem, that's why I decided to finally learn
  how to generate reports and submit the bug ^^

  Sorry, but I cant check if it happens as well using wifi... I've got
  no wifi card on this PC :(

  Thanks and sorry my bad English ^^

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 20:22:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-07-19 (47 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.7 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  653b2178-e532-30d6-adbe-28f87300fb98  802-3-ethernet  
1504549178  lun 04 sep 2017 20:19:38 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/2  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  653b2178-e532-30d6-adbe-28f87300fb98  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1715153] Re: FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Jeremy Bicha
I tested that the new version builds in an artful PPA. (Test failures
are still ignored on s390x since 1 or tests fail there and I didn't know
a way to better selectively ignore specific test failures by arch.)

** Patch added: "source.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/1715153/+attachment/4944788/+files/source.debdiff

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  New

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Jean-Baptiste Lallement
Could you please paste the complete output of the command?

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Jean-Baptiste Lallement
@Khurshid, right, it is likely bug 1705157 but I'd like to confirm that
ubuntu-session is installed and it is the latest version.

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1715153] Re: FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Jeremy Bicha
The -dbg package has been removed because we migrated to automatic debug
symbols.

** Patch added: "binary.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/1715153/+attachment/4944770/+files/binary.debdiff

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  New

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

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


[Desktop-packages] [Bug 1714596] Re: PDF images are blank

2017-09-05 Thread Bryan Quigley
** Description changed:

- 1. Download this PDF - 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
+ 1. Download a PDFs with images such as - 
+ 
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
+ 
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
+ http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf
+ 
  2. Open in Evince, note how first page is blank
  
  Open with Firefox and note how it displays a nice intro page.
  
  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not
  
  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.
  
  Given my testing in Fedora (C#2) which worked fine with same version of
  poppler and by downgrading the packages I believe this a Ubuntu specific
  poppler bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Khurshid Alam
** Changed in: gdm (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1694303] Re: Font issues in Zesty

2017-09-05 Thread Carlo Lobrano
Confirmed on light-themes 16.10+17.04.20170406-0ubuntu1

not reproducible on 16.10+17.10.20170518-0ubuntu1

** Package changed: gitg (Ubuntu) => light-themes (Ubuntu)

** Changed in: light-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Font issues in Zesty

Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of font issues with gitg (version: 3.23.0-1) in Zesty:

  - commit description text is white (which is unreadable on light gray 
background in the default Ubuntu theme)
  - diffs are not in monospaced font anymore

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Khurshid Alam
For some people it's exactly opposite. All sessions are xorg regardless
of session name.

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1714876] Re: GDM doesn't show xorg session at login (Artful)

2017-09-05 Thread Khurshid Alam
gnome-session: 3.25.90-0ubuntu
ubuntu-session: 3.25.90-0ubuntu

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

Title:
  GDM doesn't show xorg session at login (Artful)

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  With gdm It shows only two session:

  1) Ubuntu

  2) Ubuntu on wayland

  With (1), I have no .xauthority and display is set to wayland-0

  2) gives black screen.

  However If I install lightdm and reboot into lightdm all the sesssions
  are clearly visible including Gnome, Ubuntu on xorg etc.

  gnome-session: 3.25.90-0ubuntu

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

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


[Desktop-packages] [Bug 1715156] Re: Kubuntu 17.10 requires Wi-Fi password twice

2017-09-05 Thread Saurav Sengupta
** Package changed: network-manager (Ubuntu) => plasma-nm (Ubuntu)

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

Title:
  Kubuntu 17.10 requires Wi-Fi password twice

Status in plasma-nm package in Ubuntu:
  New

Bug description:
  Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma
  5.10.5) requires the password twice, on both the live session and the
  installed system. This is similar to, but may not be identical to,
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1572244. The password entered in the Plasma Network
  Manager widget does not appear in the password field of the selected
  network in System Settings, unless it is entered again at the second
  prompt or in the connection editor.

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

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


[Desktop-packages] [Bug 1715157] Re: Ubuntu software center won't install updates.

2017-09-05 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 gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1715157

Title:
  Ubuntu software center won't install updates.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The updates I'm trying to install are OS Updates and Software 3.20.5.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-software-common 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 09:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:gnome-software-common:3.20.5-0ubuntu0.16.04.5
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package gnome-software-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-01 (65 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.20.5-0ubuntu0.16.04.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1715159] [NEW] Redundant titlebar in GTK3 CSD applications

2017-09-05 Thread Saurav Sengupta
Public bug reported:

GTK3 applications which use client-side decorations (CSD), such as GNOME
Disks, are shown with an "extra" standard titlebar on Kubuntu 17.10 Beta
1. This standard titlebar is redundant and appears to be a regression.

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


** Tags: artful kubuntu kwin

** Summary changed:

- Redundant titlebar in GTK3 header bar applications
+ Redundant titlebar in GTK3 CSD applications

** Package changed: network-manager (Ubuntu) => kwin (Ubuntu)

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

Title:
  Redundant titlebar in GTK3 CSD applications

Status in kwin package in Ubuntu:
  New

Bug description:
  GTK3 applications which use client-side decorations (CSD), such as
  GNOME Disks, are shown with an "extra" standard titlebar on Kubuntu
  17.10 Beta 1. This standard titlebar is redundant and appears to be a
  regression.

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

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


[Desktop-packages] [Bug 1694303] [NEW] Font issues in Zesty

2017-09-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a couple of font issues with gitg (version: 3.23.0-1) in Zesty:

- commit description text is white (which is unreadable on light gray 
background in the default Ubuntu theme)
- diffs are not in monospaced font anymore

** Affects: light-themes (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Font issues in Zesty
https://bugs.launchpad.net/bugs/1694303
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to light-themes in Ubuntu.

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


[Desktop-packages] [Bug 1715156] [NEW] Kubuntu 17.10 requires Wi-Fi password twice

2017-09-05 Thread Saurav Sengupta
Public bug reported:

Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma
5.10.5) requires the password twice, on both the live session and the
installed system. This is similar to, but may not be identical to,
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1572244.
The password entered in the Plasma Network Manager widget does not
appear in the password field of the selected network in System Settings,
unless it is entered again at the second prompt or in the connection
editor.

** Affects: plasma-nm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful kubuntu network-manager plasma

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

Title:
  Kubuntu 17.10 requires Wi-Fi password twice

Status in plasma-nm package in Ubuntu:
  New

Bug description:
  Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma
  5.10.5) requires the password twice, on both the live session and the
  installed system. This is similar to, but may not be identical to,
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1572244. The password entered in the Plasma Network
  Manager widget does not appear in the password field of the selected
  network in System Settings, unless it is entered again at the second
  prompt or in the connection editor.

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

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


[Desktop-packages] [Bug 1715157] [NEW] Ubuntu software center won't install updates.

2017-09-05 Thread Charles Asner
Public bug reported:

The updates I'm trying to install are OS Updates and Software 3.20.5.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-software-common 3.20.5-0ubuntu0.16.04.5
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Sep  5 09:56:20 2017
Dependencies:
 
DuplicateSignature:
 package:gnome-software-common:3.20.5-0ubuntu0.16.04.5
 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
 dpkg: error processing package gnome-software-common (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-07-01 (65 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gnome-software
Title: package gnome-software-common 3.20.5-0ubuntu0.16.04.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  Ubuntu software center won't install updates.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The updates I'm trying to install are OS Updates and Software 3.20.5.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-software-common 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 09:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:gnome-software-common:3.20.5-0ubuntu0.16.04.5
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package gnome-software-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-01 (65 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.20.5-0ubuntu0.16.04.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Jeremy Bicha
I don't have a Hi-DPI screen so I'm unsure about all the details.

My understanding is that you need to configure HiDPI for Qt apps
separately.

I think that GNOME Shell 3.25.90 doesn't really support HiDPI for X,
just for Wayland. That may be a regression, but Hi-DPI support in GNOME
Shell has been redesigned to prepare to support fractional scaling in
Wayland in a future release and it may be a lot more complicated for all
that to work well on X too.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm 

Re: [Desktop-packages] [Bug 1715153] [NEW] FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Iain Lane
On Tue, Sep 05, 2017 at 01:33:31PM -, Launchpad Bug Tracker wrote:
> clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium
> 
>   * Release to unstable
>   * debian/control.in:
> - Drop Build-Depends on libgl1-mesa-dri
>   * debian/rules:
> - Ignore test failures on Debian. See bug 874077.
> 
>   * Allow tests to fail the build on Ubuntu. The tests fail in Debian.
> 
>  -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400
> 
> clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium
> 
>   * Convert from cdbs to dh
>   * Bump debhelper compat to 10
>   * Add debian/libclutter-1.0-0.docs to install NEWS and README
>   * Convert to automatic dbgsym package
>   * Add autopkgtest to run clutter-1.0-tests
>   * debian/control.in:
> - Build-depend on dbus for build tests
> - Build-depend on libgl1-mesa-dri for build tests since Debian's
>   libgl1-mesa-glx currently only recommends it
>   * debian/rules:
> - Allow tests to not fail the build this time
>   * Add debian/patches/skip-failing-tests.patch:
> - Skip failing test so that we can run all the other tests
> 
>  -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

Please supply a debian/ debdiff and a binary debdiff between what we
have in artful now and your proposed upload.

What testing have you done?

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

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  New

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

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


[Desktop-packages] [Bug 1714688] Re: orca fails to start

2017-09-05 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-orca - 3.25.4-0ubuntu2

---
gnome-orca (3.25.4-0ubuntu2) artful; urgency=medium

  [ Alex ARNAUD ]
  * Build-depend on and run dh-autoreconf. This was accidentally dropped
when merging 3.24. (LP: #1714688)

 -- Jeremy Bicha   Tue, 05 Sep 2017 08:41:14 -0400

** Changed in: gnome-orca (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  orca fails to start

Status in gnome-orca package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu desktop team,

  Since the upgrade from Orca 3.22 to 3.24 or 3.25 it is no longer
  possible to start Orca if it wants to use GSettings.

  Steps to reproduce:
  1) Upgrade to the last gnome-orca release
  2) Remove the folder "~/.local/share/orca/" if you've it
  3) Launch Orca from a terminal to see the log

  You will obtain the following error message:
  http://paste.ubuntu.com/25451496/

  Why we've this bug? See my comment on another bug that explain the
  origin of the issue: https://bugs.launchpad.net/ubuntu/+source/gnome-
  orca/+bug/1704847/comments/9

  The issue comes from because the new package doesn't include the
  GSettings backend it uses with the patches "0001-Add-GSettings-
  backend-to-Orca.patch".

  To fix the issue we could include again "autoreconf.mk" to the "debian/rules" 
file.
  You could find the diff here: http://paste.ubuntu.com/25451573/

  Best regards.

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

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


[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

2017-09-05 Thread Matej Kovacic
I can confirm this issue. I have fresh install of 17.04, and it happens
when LO is started by clicking on an document. If LO is started from the
launcher or from the dash, this will not appear.

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  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/1589215/+subscriptions

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Rachel Greenham
... or if you meant does the gnome tweak tool *itself* appear with its
user interface elements at the correct size or too small? It shows at
the correct size, including the titlebar... but actually contrary to my
original report *all* titlebars, both the system and integrated type,
are now being shown with text at the correct size.

In gnome-shell itself - the top bar, the menus and indicators off that,
the applications and activities views - the text is still half-size.
Also in at least some QT apps (eg: nextcloud-client) the text is still
half-size, but GTK-based apps that had half-sized text in the original
bug report, eg: hexchat, sublime text, etc., those now seem fine.

So there is a change since originally reporting. The problem does seem
more restricted just to gnome-shell and non-GTK-based apps.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value 

[Desktop-packages] [Bug 1715153] [NEW] FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

2017-09-05 Thread Jeremy Bicha
Public bug reported:

Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Explanation of FeatureFreeze exception:

The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian experimental)
were already in artful for about 7 weeks from May to early July until
1.26.2+dfsg-1 was uploaded to unstable and autosynced to Ubuntu.

I delayed pushing my changes from experimental to unstable because of
the Debian Stretch freeze and because I was surprised that the tests
failed on Debian.

I've now opened https://bugs.debian.org/874077 and ignored the test
failures on Debian.

Generally, we want to have packages in main run their build tests and
fail the build if the tests fail.

https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

Changelog entries since current artful version 1.26.2+dfsg-1:

clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

  * Release to unstable
  * debian/control.in:
- Drop Build-Depends on libgl1-mesa-dri
  * debian/rules:
- Ignore test failures on Debian. See bug 874077.

  * Allow tests to fail the build on Ubuntu. The tests fail in Debian.

 -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

  * Convert from cdbs to dh
  * Bump debhelper compat to 10
  * Add debian/libclutter-1.0-0.docs to install NEWS and README
  * Convert to automatic dbgsym package
  * Add autopkgtest to run clutter-1.0-tests
  * debian/control.in:
- Build-depend on dbus for build tests
- Build-depend on libgl1-mesa-dri for build tests since Debian's
  libgl1-mesa-glx currently only recommends it
  * debian/rules:
- Allow tests to not fail the build this time
  * Add debian/patches/skip-failing-tests.patch:
- Skip failing test so that we can run all the other tests

 -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

** Affects: clutter-1.0 (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: clutter-1.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  FFe: Sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable (main)

Status in clutter-1.0 package in Ubuntu:
  New

Bug description:
  Please sync clutter-1.0 1.26.2+dfsg-3 (main) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  The changes from 1.26.2+dfsg-2 (1.26.0+dfsg-4 from Debian
  experimental) were already in artful for about 7 weeks from May to
  early July until 1.26.2+dfsg-1 was uploaded to unstable and autosynced
  to Ubuntu.

  I delayed pushing my changes from experimental to unstable because of
  the Debian Stretch freeze and because I was surprised that the tests
  failed on Debian.

  I've now opened https://bugs.debian.org/874077 and ignored the test
  failures on Debian.

  Generally, we want to have packages in main run their build tests and
  fail the build if the tests fail.

  https://launchpad.net/ubuntu/+source/clutter-1.0/+changelog

  Changelog entries since current artful version 1.26.2+dfsg-1:

  clutter-1.0 (1.26.2+dfsg-3) unstable; urgency=medium

* Release to unstable
* debian/control.in:
  - Drop Build-Depends on libgl1-mesa-dri
* debian/rules:
  - Ignore test failures on Debian. See bug 874077.

* Allow tests to fail the build on Ubuntu. The tests fail in Debian.

   -- Jeremy Bicha   Sat, 02 Sep 2017 17:14:56 -0400

  clutter-1.0 (1.26.2+dfsg-2) experimental; urgency=medium

* Convert from cdbs to dh
* Bump debhelper compat to 10
* Add debian/libclutter-1.0-0.docs to install NEWS and README
* Convert to automatic dbgsym package
* Add autopkgtest to run clutter-1.0-tests
* debian/control.in:
  - Build-depend on dbus for build tests
  - Build-depend on libgl1-mesa-dri for build tests since Debian's
libgl1-mesa-glx currently only recommends it
* debian/rules:
  - Allow tests to not fail the build this time
* Add debian/patches/skip-failing-tests.patch:
  - Skip failing test so that we can run all the other tests

   -- Jeremy Bicha   Thu, 31 Aug 2017 13:07:16 -0400

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

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Rachel Greenham
The only scaling setting in tweak tool is the one in the Fonts section,
which appears to be exposing org.gnome.desktop.interface text-scaling-
factor. It scales the *text*. It scales all text relative to its
original size. So if I set it to 2.0 the text that's half size will be
the correct size, but the text that already *was* the correct size will
be twice that size, and mostly too big for the windows it's in, as only
the text has been scaled, not most of the other user interface
components.

As described in the original post under the paragraph starting
"gsettings org.gnome.desktop.interface text-scaling-factor"

I've never seen the point of that setting. It's always done that, but
only setting the text scale without the rest of the user interface is
useless.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything 

[Desktop-packages] [Bug 1715030] Re: Please remove firefox from artful on s390x and ppc64el

2017-09-05 Thread Jeremy Bicha
I'm setting the bug to incomplete because it needs more triage of the
reverse-depends so that it's clear what we want the Archive Admins to
do.

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

** Summary changed:

- Please remove firefox from artful on s390x and ppc64el
+ Please remove firefox from artful on ppc64el

** Description changed:

  As discussed at https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-September/039962.html
  
- please remove firefox from armhf and ppc64el for artful.
+ please remove firefox from ppc64el for artful.
  
- ppc64el has the same output except without lubuntu-desktop and 
lubuntu-gtk-desktop
- $ reverse-depends src:firefox -a armhf
+ $ reverse-depends src:firefox -a ppc64el
  Reverse-Recommends
  ==
  * ardour(for firefox)
  * djview-plugin (for firefox)
  * gcu-plugin(for firefox)
  * jclic (for firefox)
  * kubuntu-desktop   (for firefox)
  * kubuntu-full  (for firefox)
  * libknopflerfish-osgi-java-doc  (for firefox)
  * lxde  (for firefox)
  * lxqt  (for firefox)
  * nip2  (for firefox)
  * rhythmbox-mozilla (for firefox)
  * ubuntu-desktop(for firefox)
  * ubuntu-gnome-desktop  (for firefox)
  * ubuntu-mate-core  (for firefox)
  * ubuntu-mate-desktop   (for firefox)
  * ubuntukylin-desktop   (for firefox-locale-zh-hans)
  * ubuntukylin-desktop   (for firefox)
  * ubuntustudio-desktop  (for firefox)
  * xsane (for firefox)
  * xubuntu-desktop   (for firefox)
  
  Reverse-Depends
  ===
  * cinnamon-desktop-environment  (for firefox) (arch:all)
  * firefox-launchpad-plugin  (for firefox) (arch:all)
  * garmin-plugin (for firefox)
  * gnome-core(for firefox)
- * lubuntu-desktop   (for firefox)
- * lubuntu-gtk-desktop   (for firefox)
  * mediatomb (for firefox)
  * mozplugger(for firefox)
  * sugar-firefox-activity(for firefox)
  * ubuntu-defaults-zh-cn (for firefox-locale-zh-hans)
  * ubuntu-online-tour(for firefox)
  * webhttrack(for firefox)
  * xul-ext-classic-theme-restorer  (for firefox) (arch:all)
  * xul-ext-colorfultabs  (for firefox)(arch:all)
  * xul-ext-form-history-control  (for firefox) (arch:all)
  * xul-ext-https-finder  (for firefox) (arch:all)
  * xul-ext-iceweasel-branding(for firefox) (arch:all)
  * xul-ext-kwallet5  (for firefox)
  * xul-ext-lightbeam (for firefox)
  * xul-ext-mozvoikko (for firefox)
  * xul-ext-password-editor   (for firefox)
  * xul-ext-pdf.js(for firefox)
  * xul-ext-self-destructing-cookies  (for firefox)
  * xul-ext-spdy-indicator(for firefox)
  * xul-ext-ublock-origin (for firefox)
  * xul-ext-video-without-flash   (for firefox)
  * xul-ext-y-u-no-validate   (for firefox)
  
  Plan
  
- Please also remove 
+ Please also remove
  
  garmin-plugin (armhf and ppc64el)
  mozplugger everywhere and blacklist it

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

Title:
  Please remove firefox from artful on ppc64el

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  As discussed at https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-September/039962.html

  please remove firefox from ppc64el for artful.

  $ reverse-depends src:firefox -a ppc64el
  Reverse-Recommends
  ==
  * ardour(for firefox)
  * djview-plugin (for firefox)
  * gcu-plugin(for firefox)
  * jclic (for firefox)
  * kubuntu-desktop   (for firefox)
  * kubuntu-full  (for firefox)
  * libknopflerfish-osgi-java-doc  (for firefox)
  * lxde  (for firefox)
  * lxqt  (for firefox)
  * nip2  (for firefox)
  * rhythmbox-mozilla (for firefox)
  * ubuntu-desktop(for firefox)
  * ubuntu-gnome-desktop  (for firefox)
  * ubuntu-mate-core  (for firefox)
  * ubuntu-mate-desktop   (for firefox)
  * ubuntukylin-desktop   (for firefox-locale-zh-hans)
  * ubuntukylin-desktop   (for firefox)
  * ubuntustudio-desktop  (for firefox)
  * xsane (for firefox)
  * xubuntu-desktop   (for firefox)

  Reverse-Depends
  ===
  * cinnamon-desktop-environment  (for firefox) (arch:all)
  * firefox-launchpad-plugin  (for firefox) (arch:all)
  * 

[Desktop-packages] [Bug 1714688] Re: orca fails to start

2017-09-05 Thread Jeremy Bicha
** Changed in: gnome-orca (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: gnome-orca (Ubuntu)
   Importance: Undecided => High

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

Title:
  orca fails to start

Status in gnome-orca package in Ubuntu:
  Fix Committed

Bug description:
  Dear Ubuntu desktop team,

  Since the upgrade from Orca 3.22 to 3.24 or 3.25 it is no longer
  possible to start Orca if it wants to use GSettings.

  Steps to reproduce:
  1) Upgrade to the last gnome-orca release
  2) Remove the folder "~/.local/share/orca/" if you've it
  3) Launch Orca from a terminal to see the log

  You will obtain the following error message:
  http://paste.ubuntu.com/25451496/

  Why we've this bug? See my comment on another bug that explain the
  origin of the issue: https://bugs.launchpad.net/ubuntu/+source/gnome-
  orca/+bug/1704847/comments/9

  The issue comes from because the new package doesn't include the
  GSettings backend it uses with the patches "0001-Add-GSettings-
  backend-to-Orca.patch".

  To fix the issue we could include again "autoreconf.mk" to the "debian/rules" 
file.
  You could find the diff here: http://paste.ubuntu.com/25451573/

  Best regards.

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

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


[Desktop-packages] [Bug 395108] Re: Allow alphabetical sorting of bookmarks in Nautilus

2017-09-05 Thread Bug Watch Updater
** Changed in: nautilus
   Status: New => Expired

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

Title:
  Allow alphabetical sorting of bookmarks in Nautilus

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have added lots of bookmarks in Nautilus but I find that when I add
  a new one it appears at the end of the list. I would like to be able
  to sort them alphabetically. Where there are dot .files the dot should
  be ignored for the purposes of sorting by first letter of the folder
  name.

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

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


[Desktop-packages] [Bug 35347] Re: bookmarks need subfolders

2017-09-05 Thread Sebastien Bacher
upstream closed the bug with that comment

"
At the time this was reported, there was no list of Recent Servers, so servers 
had to be saved in bookmarks.

This is no longer the case. Currently, remote URLs are saved on a list
of Recent Servers, not on the Bookmarks list.

Therefore, marking this old bug as obsolete."

doing the same here

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

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

Title:
  bookmarks need subfolders

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  ...ever thought about having 100 such bookmarks?

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

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


[Desktop-packages] [Bug 1252203] Re: hits "nautilus_window_get_slots NAUTILUS_IS_WINDOW (window)" assert on opening bookmarks not available at start

2017-09-05 Thread Sebastien Bacher
there has been no e.u.c report since 3.6, closing the bug

** Changed in: nautilus (Ubuntu)
   Status: Triaged => 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/1252203

Title:
  hits "nautilus_window_get_slots NAUTILUS_IS_WINDOW (window)" assert on
  opening bookmarks not available at start

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nautilus.  This problem was most recently seen with version
  1:3.6.3-0ubuntu16, the problem page at
  https://errors.ubuntu.com/problem/0e5eee470d33c7f3240a8f1f478183a83c7c4c25
  contains more details.

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

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


[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

2017-09-05 Thread Dean Henrichsmeyer
On the affected system if you launch gnome tweak tool will it do the
appropriately HiDPI scaling for everything but the title bar and
notifications?

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 13:03:53 2017
  InstallationDate: Installed on 2017-07-30 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: 

[Desktop-packages] [Bug 268497] Re: double clicking on a non local bookmark trigger a dbus error

2017-09-05 Thread Sebastien Bacher
upstream closed with this comment

"Nautilus no longer implements the sidebar itself, but uses the
GtkPlacesSidebar widget, which doesn't seem to have this bug, or at
least I can't reproduce it.

Please reopen or report a new bug if this bug affects a recent version."

doing the same here

** Changed in: nautilus (Ubuntu)
   Status: Triaged => 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/268497

Title:
  double clicking on a non local bookmark trigger a dbus error

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When I try to connect to a lan netshare from my other computers which
  both using Windows XP home/pro. I try brows the lan trough nautilus
  and the icon "network" then I get my computers in the list and
  dubbelclick one of them and try to access my shares. But then I get
  the error like above ( DBus error
  org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered
  )

  I'm using ubuntu 64bits 8.10 I didn't had this problem with 8.04.
  Though I couldn't get the network list trough nautilus->network. I had
  to manually type in the smb://search

  I've tried run: /usr/lib/gvfs/gvfsd -r but it didn't return anything...
  I'm not sure if I had this problem from the start but I think so. I can't 
recall the opposite.

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

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


[Desktop-packages] [Bug 1700764] Re: snap policykit prompt in Turkish language

2017-09-05 Thread Sebastien Bacher
@Douglas, what ubuntu serie are you using and what snap-glib package
version?

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

Title:
  snap policykit prompt in Turkish language

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd-glib package in Ubuntu:
  Triaged

Bug description:
  I for the first time installed a snap package via gnome-software, and
  was asked to init the snap system by entering my credentials/creating
  an account. After doing that, a Gnome dialog popped up where I should
  enter my password - I am in Austria and using Ubuntu GNOME in German -
  but the words there seem Turkish (?) to me - or at least a language I
  can't understand. See screenshot.

  I suppose there was a problem picking the right translation - bu I
  don't know if this is a snap problem or a gnome-software one - I just
  picked one to start this bug report here.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu3.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 26 22:05:01 2017
  InstallationDate: Installed on 2016-11-27 (211 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-06-17 (8 days ago)

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

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


[Desktop-packages] [Bug 1715117] Re: Cannot launch wifi settings from wifi indicator "Settings panel for desktop file gnome-wifi-panel.desktop could not be loaded!"

2017-09-05 Thread Sebastien Bacher
that's going to be fixed when g-c-c gets updated

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

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

Title:
  Cannot launch wifi settings from wifi indicator "Settings panel for
  desktop file gnome-wifi-panel.desktop could not be loaded!"

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

Bug description:
  On latest artful desktop the wifi settings panel cannot be launched
  and the following error is logged in the journal

  Settings panel for desktop file gnome-wifi-panel.desktop could not be
  loaded!

  This panel is available in a newer version of gnome-control-center
  
https://git.gnome.org/browse/gnome-control-center/commit/?id=016efdfac8e06a6c223e8dd8ede990bb2d49b8bd

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 12:06:41 2017
  InstallationDate: Installed on 2013-09-03 (1462 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715117/+subscriptions

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


[Desktop-packages] [Bug 1715122] Re: Location indicator icon in Gnome Ubuntu won't change even it's disabled

2017-09-05 Thread Sebastien Bacher
that's fixed in the artful serie

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

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

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

Title:
  Location indicator icon in Gnome Ubuntu won't change even it's
  disabled

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The location indicator won't change its icon when it got disabled.
  Users can't tell what's the current state unless click on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep  5 18:40:36 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['topic...@phocean.net', 
'alternate-...@gnome-shell-extensions.gcampax.github.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'suspend-button@laserb']"
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'evolution.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'skypeforlinux.desktop', 'google-chrome.desktop', 'org.gnome.Terminal.desktop', 
'hexchat.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-07-12 (54 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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/1715122/+subscriptions

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


[Desktop-packages] [Bug 1715030] Re: Please remove firefox from artful on armhf and ppc64el

2017-09-05 Thread Sebastien Bacher
Right, the archs we want to remove it from are ppc64el and s390x

** Summary changed:

- Please remove firefox from artful on armhf and ppc64el
+ Please remove firefox from artful on s390x and ppc64el

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

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

Title:
  Please remove firefox from artful on s390x and ppc64el

Status in firefox package in Ubuntu:
  New

Bug description:
  As discussed at https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-September/039962.html

  please remove firefox from armhf and ppc64el for artful.

  ppc64el has the same output except without lubuntu-desktop and 
lubuntu-gtk-desktop
  $ reverse-depends src:firefox -a armhf
  Reverse-Recommends
  ==
  * ardour(for firefox)
  * djview-plugin (for firefox)
  * gcu-plugin(for firefox)
  * jclic (for firefox)
  * kubuntu-desktop   (for firefox)
  * kubuntu-full  (for firefox)
  * libknopflerfish-osgi-java-doc  (for firefox)
  * lxde  (for firefox)
  * lxqt  (for firefox)
  * nip2  (for firefox)
  * rhythmbox-mozilla (for firefox)
  * ubuntu-desktop(for firefox)
  * ubuntu-gnome-desktop  (for firefox)
  * ubuntu-mate-core  (for firefox)
  * ubuntu-mate-desktop   (for firefox)
  * ubuntukylin-desktop   (for firefox-locale-zh-hans)
  * ubuntukylin-desktop   (for firefox)
  * ubuntustudio-desktop  (for firefox)
  * xsane (for firefox)
  * xubuntu-desktop   (for firefox)

  Reverse-Depends
  ===
  * cinnamon-desktop-environment  (for firefox) (arch:all)
  * firefox-launchpad-plugin  (for firefox) (arch:all)
  * garmin-plugin (for firefox)
  * gnome-core(for firefox)
  * lubuntu-desktop   (for firefox)
  * lubuntu-gtk-desktop   (for firefox)
  * mediatomb (for firefox)
  * mozplugger(for firefox)
  * sugar-firefox-activity(for firefox)
  * ubuntu-defaults-zh-cn (for firefox-locale-zh-hans)
  * ubuntu-online-tour(for firefox)
  * webhttrack(for firefox)
  * xul-ext-classic-theme-restorer  (for firefox) (arch:all)
  * xul-ext-colorfultabs  (for firefox)(arch:all)
  * xul-ext-form-history-control  (for firefox) (arch:all)
  * xul-ext-https-finder  (for firefox) (arch:all)
  * xul-ext-iceweasel-branding(for firefox) (arch:all)
  * xul-ext-kwallet5  (for firefox)
  * xul-ext-lightbeam (for firefox)
  * xul-ext-mozvoikko (for firefox)
  * xul-ext-password-editor   (for firefox)
  * xul-ext-pdf.js(for firefox)
  * xul-ext-self-destructing-cookies  (for firefox)
  * xul-ext-spdy-indicator(for firefox)
  * xul-ext-ublock-origin (for firefox)
  * xul-ext-video-without-flash   (for firefox)
  * xul-ext-y-u-no-validate   (for firefox)

  Plan
  
  Please also remove 

  garmin-plugin (armhf and ppc64el)
  mozplugger everywhere and blacklist it

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

-- 
Mailing list: https://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   >