date:20171213

Here's the same fix, for bionic.

Unfortunately even with this fix it's too hard for me to tell if it's
any improvement. My system seems to reliably default to the last used
audio profile for the device. Even if I have removed and re-paired the
device. So it seems like the fix at most is only necessary for brand new
devices you've never had on your system before.

** Patch added: "pulseaudio_11.1-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720684/+attachment/5022464/+files/pulseaudio_11.1-1ubuntu2.debdiff

** Changed in: pulseaudio (Ubuntu)
   Importance: High => Medium

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

Title:
  Bluetooth speaker used the HSP/HFP profile by default rather than the
  higher-quality A2DP profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Kubuntu 17.04
  Bluetooth device: 
https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1
 (itentifies itself as "C6")

  The above Bluetooth speaker paired and started streaming audio
  perfectly in Kubuntu 17.04. But the audio quality was poor, because
  the default audio profile was the low-quality HSP/HFP one. When I
  switched it to the A2DP profile, it sounded perfect again.

  Can we make A2DP the default playback profile for Bluetooth audio
  devices?

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-12-13 Thread PeterPall

That is the only thing I would ask: We now have found out to make the
package work out-of-the-box. Is there any chance that the maintainer
picks up the changes - which greatly would improve the usability of
Linux?

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Released
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731459] Re: Black band in scanned images

2017-12-13 Thread Duane Barry

Workaround is to install sane-backends-1.0.25 from the sane Project Site.
This version seems to work properly with LiDE 200. I did not realise any side 
effects at the moment using 1.0.25.

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

Title:
  Black band in scanned images

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

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

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

[Desktop-packages] [Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...

2017-12-13 Thread Stéphane Charette

Anyone know either the cause, or a solution?

If it helps, the two computers where I'm seeing this also happen to be
the two host computers where I run Virtualbox.

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

Title:
  Login screen showing Authentication Failed Switch to greeter...

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

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

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

2017-12-13 Thread Rocko

gnome-shell froze just again after entering my password when I was
running gnome-shell in an X session, and with X running the cursor does
not freeze and I can use CTRL-ALT-F1 to switch back to the gdm login
screen. I was able to log into another gnome-shell a different user;
unfortunately, before I was able to run those commands in comment #2, I
tried enabling dash-to-dock from gnome-tweak-tool, and this totally
froze the Wayland session and I had to hard reboot the laptop since I
didn't have access to another PC to get a ssh session.

I don't know if it is relevant, but loginctl reported this for the
locked session:

IdleHint=yes
IdleSinceHint=151321923789
IdleSinceHintMonotonic=80125362795
LockedHint=yes

If I try the same thing with two user sessions now after rebooting,
IdleHint and LockedHint are both 'no' for both the screen-locked session
and the current session. (Incidentally, gnome-shell no longer runs for
my other user now that I have tried to enable dash-to-dock - I had to
run a unity session. Perhaps Ubuntu should have waited for gnome-shell
to become more stable before switching to it?)


When a Wayland session freezes, CTRL-ALT-DEL no longer works. Is this something 
that can be configured or fixed? It is quite ridiculous that gnome-shell should 
be able to completely lock up the PC - surely only critical kernel faults 
should be able to do that.

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

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

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

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

[Desktop-packages] [Bug 1737083] Re: Epiphany does not start

2017-12-13 Thread Sugar Tang

Sorry to respond so late. What file do want me to open and get its
content?

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

Title:
  Epiphany does not start

Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 16.04 LTS
  Epiphany:3.18.11-0ubuntu1

  Epiphany does not start!

  Using CLI to start it, the following error message showed up:

  (epiphany:3361): GLib-GIO-ERROR **: Settings schema 
'org.gnome.Epiphany.lockdown' is not installed
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-08-30 (99 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: epiphany-browser 3.18.11-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Tags:  xenial
  Uname: Linux 4.4.0-103-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/epiphany-browser/+bug/1737083/+subscriptions

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

[Desktop-packages] [Bug 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  specific SVG file breaks Ubuntu 16.04 desktop + nautilus

Status in librsvg:
  Expired
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  Saving following file on Desktop (Ubuntu 16.04.1) results in:

  1. Wallpaper and all icons on the desktop disappear
  2. Nautilus starts for ~1sec then breaks with "Floating point exception"

  I suspect it's related to librsvg. In syslog I have many records
  similar to this one:

  kernel: [   20.076864] traps: nautilus[2270] trap divide error
  ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in
  librsvg-2.so.2.40.13[7f63fbdc9000+35000]

  Here is the file (I can't even attach it here with Firefox, because it
  makes it crash):

  http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink"; 
xmlns:ev="http://www.w3.org/2001/xml-events";>
  

   

   
   https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA";
 result="pattern" width="4" height="4"/>
 
 

  

  

  

   
  
   
  

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

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

[Desktop-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll

2017-12-13 Thread Reuben Lifshay

I tested with evdev with the same daily image and it doesn't work there
either.

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

Title:
  Razer Naga Chroma wheel tilt being remapped to vertical scroll

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7)
  are being remapped to scroll up and down (buttons 4, and 5) as per
  xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems

   Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  7 14:25:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1303]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 5986: Acer, Inc
   Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04nRSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.version: galp2
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80-1~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  7 14:21:19 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1737993] Re: Gnome-shell segfault and returns to login screen

Please have a look in /var/crash and if you find a relevant crash file
then upload it using this command:

  apport-cli /var/crash/YOURFILE.crash

This bug is incomplete because we don't yet know which crash it is.
Quite likely it's one of the ones in functions starting with "st_" in
this list:

  https://errors.ubuntu.com/?package=gnome-shell&period=month

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

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

Title:
  Gnome-shell segfault and returns to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since my upgrade to ubuntu 17.10 (and therefore usage of gnome-shell
  instead of unity), I have regular crashes of gnome-shell where I
  return to the login screen. I don't have a reproduction scenario, it
  appears to happen at random times, sometimes multiple times a day when
  some other days everything is fine.

  Everytime, I have this line in my kern.log : 
  Dec 13 15:48:23 plw-fr-troche kernel: [22168.253619] gnome-shell[16768]: 
segfault at 7fdafa227114 ip 7fdbb5943bb1 sp 7ffdc85c7d80 error 7 in 
libst-1.0.so[7fdbb5925000+4b000]

  The segfault always refers to libst.

  I work as a developer and tend to use some applications that take
  quite a lot of memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 15:49:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-24 (476 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-03 (40 days ago)

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

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

[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login

Maybe consider using bug 1292398 instead, and/or updating that one.

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

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

Title:
  Dual monitor configuration not saved across logout / login

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  System76 Galaga UltraPro laptop.

  Two monitors, one plugged into the DisplayPort and one plugged into
  HDMI.

  I use the Displays settings page to tell the system which monitor is
  on the right and which is on the left, and tell it to make the left
  monitor the primary one. All is well.

  Then I log out and log back in.

  Now the two monitors are reversed -- i.e., it thinks that the monitor
  on the right is on the left and vice versa -- and the right monitor
  (which, remember, it thinks is on the left) is the primary one.

  In short, it forgets the configuration I told it to use immediately
  before logging out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:55:09 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)

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

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

[Desktop-packages] [Bug 1738117] Re: totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from g_daemon_f

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

Probably close enough to call a duplicate of bug 1738025

** Summary changed:

- 
/usr/bin/totem:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_lookup:_g_daemon_vfs_mountspec_get_uri_scheme:g_daemon_file_get_uri_scheme
+ totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() 
from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from 
g_daemon_file_get_uri_scheme()

** This bug has been marked a duplicate of bug 1738025
   totem crashed with SIGSEGV in g_str_hash()

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

Title:
  totem crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  _g_daemon_vfs_mountspec_get_uri_scheme() from
  g_daemon_file_get_uri_scheme()

Status in totem package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/285c102b1cdec405fdd1e6fa862327d2a161f0b9 
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/totem/+bug/1738117/+subscriptions

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

[Desktop-packages] [Bug 1738118] Re: totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from g_daemon_f

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

** Summary changed:

- 
/usr/bin/totem:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_lookup:_g_daemon_vfs_mountspec_get_uri_scheme:g_daemon_file_has_uri_scheme
+ totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() 
from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from 
g_daemon_file_has_uri_scheme()

** This bug has been marked a duplicate of bug 1738025
   totem crashed with SIGSEGV in g_str_hash()

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

Title:
  totem crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  _g_daemon_vfs_mountspec_get_uri_scheme() from
  g_daemon_file_has_uri_scheme()

Status in totem package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e 
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/totem/+bug/1738118/+subscriptions

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

[Desktop-packages] [Bug 1738025] Re: totem crashed with SIGSEGV in g_str_hash()

** Information type changed from Private to Public

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

Title:
  totem crashed with SIGSEGV in g_str_hash()

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e

  ---

  I had nautilus open to display media files on a NAS drive. I double
  clicked on a file and waited for totem to open. It didn't. I was then
  prompted to report the problem. nautilus seems to be working correctly
  as I can navigate the NAS drive without problem.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 13 15:41:15 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-11-07 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1c4e3871f0 :   movsbl (%rdi),%edx
   PC (0x7f1c4e3871f0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
  Title: totem crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1738117] [NEW] totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from g_daemon

2017-12-13 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/285c102b1cdec405fdd1e6fa862327d2a161f0b9 
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/.

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


** Tags: artful trusty utopic vivid wily xenial yakkety zesty

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

Title:
  totem crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  _g_daemon_vfs_mountspec_get_uri_scheme() from
  g_daemon_file_get_uri_scheme()

Status in totem package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/285c102b1cdec405fdd1e6fa862327d2a161f0b9 
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/totem/+bug/1738117/+subscriptions

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

[Desktop-packages] [Bug 1738025] Re: totem crashed with SIGSEGV in g_str_hash()

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

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

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

Title:
  totem crashed with SIGSEGV in g_str_hash()

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e

  ---

  I had nautilus open to display media files on a NAS drive. I double
  clicked on a file and waited for totem to open. It didn't. I was then
  prompted to report the problem. nautilus seems to be working correctly
  as I can navigate the NAS drive without problem.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 13 15:41:15 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-11-07 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1c4e3871f0 :   movsbl (%rdi),%edx
   PC (0x7f1c4e3871f0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
  Title: totem crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1738025] Re: totem crashed with SIGSEGV in g_str_hash()

Also tracking in:
https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e

** Description changed:

+ https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e
+ 
+ ---
+ 
  I had nautilus open to display media files on a NAS drive. I double
  clicked on a file and waited for totem to open. It didn't. I was then
  prompted to report the problem. nautilus seems to be working correctly
  as I can navigate the NAS drive without problem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 13 15:41:15 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-11-07 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
-  XDG_RUNTIME_DIR=
-  SHELL=/bin/bash
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
+  XDG_RUNTIME_DIR=
+  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7f1c4e3871f0 :   movsbl (%rdi),%edx
-  PC (0x7f1c4e3871f0) ok
-  source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
-  destination "%edx" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7f1c4e3871f0 :   movsbl (%rdi),%edx
+  PC (0x7f1c4e3871f0) ok
+  source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
+  destination "%edx" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
-  g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
-  () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
-  () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
+  g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
+  () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
+  () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
  Title: totem crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

Title:
  totem crashed with SIGSEGV in g_str_hash()

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e

  ---

  I had nautilus open to display media files on a NAS drive. I double
  clicked on a file and waited for totem to open. It didn't. I was then
  prompted to report the problem. nautilus seems to be working correctly
  as I can navigate the NAS drive without problem.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 13 15:41:15 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-11-07 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1c4e3871f0 :   movsbl (%rdi),%edx
   PC (0x7f1c4e3871f0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18
  Title: totem crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

[Desktop-packages] [Bug 1738118] [NEW] totem crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() from g_hash_table_lookup() from _g_daemon_vfs_mountspec_get_uri_scheme() from g_daemon

2017-12-13 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e 
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/.

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


** Tags: artful bionic kylin-17.10 precise trusty utopic vivid wily xenial 
yakkety zesty

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

Title:
  totem crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  _g_daemon_vfs_mountspec_get_uri_scheme() from
  g_daemon_file_has_uri_scheme()

Status in totem package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e 
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/totem/+bug/1738118/+subscriptions

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

[Desktop-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

2017-12-13 Thread WinEunuchs2Unix

Not sure I agree with #13 because message comes AFTER network is up:

Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4985] 
platform-linux: kernel support for IFLA_INET6_ADDR_GEN_MODE failed to detect; 
assume no support
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4991] manager: 
(enp59s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/0)
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.4998] keyfile: 
add connection in-memory (f1d049d0-ad20-3201-ac70-5cb8cc06a6e5,"Wired 
connection 1")
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5001] settings: 
(enp59s0): created default wired connection 'Wired connection 1'
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5007] device 
(enp59s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 13 05:52:20 alien NetworkManager[902]:   [1513169540.5025] device 
(enp59s0): link connected
Dec 13 05:52:20 alien kernel: alx :3b:00.0 enp59s0: NIC Up: 1 Gbps Full
Dec 13 05:52:20 alien NetworkManager[902]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
D

Ubuntu 16.04.3, Kernel 4.14.4, Skylake laptop. IPv6 disabled with kernel
command line in grub just because it life seems simpler that way. Only a
couple of minor network interruptions requiring reboot over the last
month.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-12-13 Thread Yuan-Chen Cheng

Hi @Łukasz, per #26, zesty version did fix LP: #1693756. If the
difference between SRU zesty version and the backport in LP: #1693756 is
something within two weeks, I think we should proceed to SRU zesty
version.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-12-13 Thread Gunnar Hjalmarsson

On 2017-12-13 18:46, Jeremy Bicha wrote:
> Would you be interested in filing the MIR bug to promote it to main?

Sure, I can do that.

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in Ubuntu Seeds:
  New
Status in ibus-libpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+subscriptions

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

[Desktop-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log

2017-12-13 Thread WinEunuchs2Unix

#19 works for me except there are two extra lines and another identical
file to change:

#authoptionalpam_kwallet.so
#authoptionalpam_kwallet5.so
#session optionalpam_kwallet.so auto_start
#session optionalpam_kwallet5.so auto_start

...are the four lines to comment out.

/etc/pam.d/lightdm
/etc/pam.d/lightdm-greeter

...are the two files to modify.

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

Title:
  Running without pam-kwallet installed issues a warning in auth.log

Status in lightdm package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error
  in auth.log:

  Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so

  This seems like a regression because with lightdm 1.10.0-0ubuntu1 or
  before I didn't have this error showing. FYI, I don't have the pam-
  kwallet package installed.

  
  $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  $ apt-cache policy lightdm pam-kwallet
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 09:12:37 2014
  InstallationDate: Installed on 2014-01-26 (81 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738110] [NEW] RSS feed in Rhythmbox pulling images instead of mp3 files

2017-12-13 Thread courtens

Public bug reported:

I reported this bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=791154

I was asked to report this bug report on launchpad.net and to state: "I
am requesting the commit to be backported." I am not sure how this
reporting all works.

Thank you for looking into it.
Nathaniel

---
1) Running fully updated Ubuntu 17.10 - Rhythmbox 3.4.1-2ubuntu5

2) apt-cache policy pkgname
   N: Unable to locate package pkgname

3) downloading mp3 file form rss feed

4) it is downloading the png file instead

** Affects: totem-pl-parser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  RSS feed in Rhythmbox pulling images instead of mp3 files

Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  I reported this bug here:
  https://bugzilla.gnome.org/show_bug.cgi?id=791154

  I was asked to report this bug report on launchpad.net and to state:
  "I am requesting the commit to be backported." I am not sure how this
  reporting all works.

  Thank you for looking into it.
  Nathaniel

  ---
  1) Running fully updated Ubuntu 17.10 - Rhythmbox 3.4.1-2ubuntu5

  2) apt-cache policy pkgname
 N: Unable to locate package pkgname

  3) downloading mp3 file form rss feed

  4) it is downloading the png file instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1738110/+subscriptions

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

[Desktop-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration

2017-12-13 Thread WinEunuchs2Unix

Have a three screen setup now:

1) Laptop screen primary gets User ID password on boot. After boot chrome 
windows which were on screen 2 are restored here along with this screens chrome 
windows.
2) HDMI nVvidia hardwired TV, steals focus on resume to password.
3) Thunderbolt 3 USB-C HDMI TV which occasionally doesn't get signal when 
rebooted and has to be powered off and on.

Other notes when booting all three monitors turn on and off a few times.
There is one patch applied during boot to enable nVidia HDMI sound:

setpci -vD -s 01:00.0 0x488.l=0x:0x
sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'
sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan'
systemctl restart lightdm.service

Ubuntu 16.04.3, Kernel 4.14.4, Skylake 6700HQ, nVidia GTX 970M, Samsung
Pro 960 NVMe SSD.

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

Title:
  Popup dialog "could not set the configuration for CRTC 65" steals
  keyboard, hinders login in 3-monitor configuration

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Every time I boot, while I'm trying to enter my password in the
  initial login screen (from Unity?), a dialog box pops up saying "Could
  not switch the monitor configuration  could not set the configuration
  for CRTC 65".

  The dialog box also steals the keyboard focus, which is very confusing
  if for some reason you're entering the password on an external display
  while the normally unused laptop display is not visible.  For example,
  three times in a row this morning I rebooted and tried unsuccessfully
  to log in.  Since the dialog box is only displayed on the laptop
  display, which I never use when external monitors are available, I had
  no idea why my keyboard seemed broken.

  Background:

  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above the laptop display.  I have a Samsung monitor to the right of
  the Viewsonic.  Since my laptop seems to only support two displays
  (which also seems true in Windows), I normally disable and totally
  ignore my laptop display, and may have papers propped up in front of
  it etc.

  Note that when I initially configured the third display I saw the
  following highly confusing behavior.  From Settings I tried to add a
  Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI
  passive connector, and got this dialog box when I hit "Apply":

     The selected configuration for displays could not be applied
     could not set the configuration for CRTC 65

  I clicked "OK" and got another dialog box:
     Failed to apply configuration: %s
     Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  It works if I disable my laptop monitor, so it looks like the problem
  is with adding a third display.  I would think it would be a pretty
  common use case to use two nice external displays and disable the
  laptop display.

  Even when the hardware can't handle a third display, the error
  messages should not be so confusing, and the login process shouldn't
  result in the keyboard being mysteriously stolen by a dialog box on a
  display which may never be visible.

  This is on Trusty 64-bit, up-to-date with upgrades.

  This bug seems similar to bug 1304627, but it seemed cleanest to get
  all the right information reported via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  9 15:35:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.vers

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

If I add "root" as member of the "lpadmin" group in /etc/group, all is
working perfecty: Kill button of the job list entry, "Clear all" at the
top of job list, and "Restart" in the print queue entry.

OdyX, WDYT? Should we add root as member of the lpadmin group?

shemgp, your latest patch is still not working for me, see comment #42.

Unsubscribing ubuntu-sponsors, as cups-pk-helper patch does not solve
the problem.

** Changed in: cups-pk-helper (Ubuntu)
   Status: Triaged => Incomplete

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

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

"Restart" button for the queue returns to work when I re-install the
original cups-pk-helper without the patch.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

I have applied the patch of comment #36 to cups-pk-helper now (nothing
uploaded, only local testing) and for me it does not work.

On the command line I have disabled a print queue and send a job to it,
by disabling the job stays in the queue so that one has time to do the
actual test.

Now I have started gnome-control-center and opened the section
"Devices"/"Printers". The queue I have stopped is shown as such and it
is also shown that it has one job. I clicked the "1 job" button to open
the job viewer. There are pause and kill buttons in the job line and a
"Clear all" button at the top. Neither with the kill button nor with the
"Clear all" button I can remove the jobe. I also cannot re-enable the
queue via the "Restart" in the print queue list.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

Added cups-pk-helper task and re-subscribed ubuntu-sponsors.

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

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

So then why does no one apply the patch of comment #36? OdyX (printing
maintainer for Debian) and me, we are OK with this solution.


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

** Also affects: cups-pk-helper (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cups-pk-helper (Ubuntu)
   Status: New => Triaged

** Changed in: cups-pk-helper (Ubuntu)
   Importance: Undecided => High

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-12-13 Thread Tom

Had same problems on my Dell XPS 15 9560. The last solution of Paul did
it for me, running ``hdajackretask``. But in my case, I had to uncheck
the override boxes. I remember I had to check them in the past, so I
presume a recent update (kernel? I have 17.04 with 4.10.0-42-generic)
changed things Is it back to normal now? Dont know...

Anyway, all seems perfect now :)

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1738097] [NEW] /usr/bin/gnome-panel:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

2017-12-13 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-panel.  This problem was most recently seen with package version 
1:3.24.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/dc29f4e711e53f418511ddaa5d8c3e7c11b9f7c5 
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/.

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


** Tags: artful saucy trusty vivid wily xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
panel:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-panel.  This problem was most recently seen with package version 
1:3.24.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/dc29f4e711e53f418511ddaa5d8c3e7c11b9f7c5 
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-panel/+bug/1738097/+subscriptions

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Felix

Welcome 2 Linux. Enduser is worthless!

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

Title:
  Deleting or stopping print jobs does not work

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

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-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/1690280

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

2017-12-13 Thread Robert Ancell

** Changed in: gnome-software (Ubuntu Zesty)
   Status: In Progress => 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/1690280

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-12-13 Thread Łukasz Zemczak

Ok, this actually looks better. It seems that the overlay was at fault
here indeed. Should we proceed instantly with SRUing the zesty version
(it can take time for it to get processed in the SRU queue), or do we
want to release LP: #1693756 first? Anyway, looking into if we can just
proceed with the backporting tomorrow in the morning.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Desktop-packages] [Bug 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Blade, Realtek ALC298, Black Mic, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to get the mic from the combo jack on my Razer Blade
  working. Headphones are functioning perfectly, but the mic seems to be
  picking up on random data, unrelated to sound output or my
  surroundings. I know the jack is working as I dual-boot Windows, and
  it works great there.

  I've added the `options snd-hda-intel model=laptop-dmic` line as
  recommended in some other threads, and tried setting pin 0x18 to mic
  using hdajackretask, but it hasn't fixed it or made any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Sat Jun 17 15:21:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-06 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276

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

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

[Desktop-packages] [Bug 1045790] Re: Rendering error on OCAL website

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  Rendering error on OCAL website

Status in librsvg:
  Expired
Status in openclipart:
  Invalid
Status in librsvg package in Ubuntu:
  New

Bug description:
  I uploaded an SVG that is a map of the UK and Ireland
  http://openclipart.org/detail/171939/uk-and-ireland-by-
  hellocatfood-171939 It was generated in Inkscape and then cleaned up
  using SVG Cleaner

  In Inkscape, GIMP and the Firefox SVG preview it displays correctly,
  but on OCAL it looks very weird!

  Steps to reproduce:
  Download the original SVG 
https://bugs.launchpad.net/librsvg/+bug/1045790/+attachment/3302221/+files/uk-ireland-vector_original.svg
  Download and install SVG Cleaner https://github.com/RazrFalcon/SVGCleaner/
  Run SVG Cleaner on the folder containing the SVG
  Look at the thumbnail preview on programs that use librsvg (Open Clip Art 
Library, Nautilus)

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

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

[Desktop-packages] [Bug 856210] Fw: many cool stuff

2017-12-13 Thread Fabio Rossi

Have you already seen all that cool stuff  ? I'm sure you're  going  to
love it ! Check it out
http://www.samtekintl.com/bjwgx.php?UE84NTYyMTBAYnVHUy5sYVVOY2hwYWQubmV0

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

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

2017-12-13 Thread Robert Ancell

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

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

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

** Changed in: gnome-software (Ubuntu Zesty)
 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/1690280

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  In Progress
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1738080] Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for perl-base
no debug symbol package found for perl-base


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGSEGV

Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid

Bug description:
  after login

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-16ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 13 22:00:33 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (102 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f14ee634b94:add0x20(%rdx),%rax
   PC (0x7f14ee634b94) ok
   source "0x20(%rdx)" (0x56318e952ea0) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  Stacktrace:
   #0  0x7f14ee634b94 in ?? () from 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-a

[Desktop-packages] [Bug 1738080] Xorg crashed with SIGSEGV

Stacktrace:
 #0  0x7f14ee634b94 in ?? ()
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

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

Title:
  Xorg crashed with SIGSEGV

Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid

Bug description:
  after login

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-16ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 13 22:00:33 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (102 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f14ee634b94:add0x20(%rdx),%rax
   PC (0x7f14ee634b94) ok
   source "0x20(%rdx)" (0x56318e952ea0) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  Stacktrace:
   #0  0x7f14ee634b94 in ?? () from 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1738080/+subscriptions

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

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

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1738080/+attachment/5022366/+files/ThreadStacktrace.txt

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Invalid

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

Title:
  Xorg crashed with SIGSEGV

Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid

Bug description:
  after login

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-16ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 13 22:00:33 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (102 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f14ee634b94:add0x20(%rdx),%rax
   PC (0x7f14ee634b94) ok
   source "0x20(%rdx)" (0x56318e952ea0) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  Stacktrace:
   #0  0x7f14ee634b94 in ?? () from 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1738080/+subscriptions

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

[Desktop-packages] [Bug 1738080] [NEW] Xorg crashed with SIGSEGV

2017-12-13 Thread Sosha

Public bug reported:

after login

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-16ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Dec 13 22:00:33 2017
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
InstallationDate: Installed on 2017-09-02 (102 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f14ee634b94:  add0x20(%rdx),%rax
 PC (0x7f14ee634b94) ok
 source "0x20(%rdx)" (0x56318e952ea0) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nvidia-graphics-drivers
Stacktrace:
 #0  0x7f14ee634b94 in ?? () from 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? ()
Title: Xorg crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2003
dmi.board.asset.tag: Default string
dmi.board.name: Z170-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.88-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-crash bionic regression single-occurrence ubuntu

** Information type changed from Private to Public

** Information type changed from Public to Private Security

** Information type changed from Private Security to Public

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

Title:
  Xorg crashed with SIGSEGV

Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid

Bug description:
  after login

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 2

[Desktop-packages] [Bug 901807] i found the stuff

2017-12-13 Thread leonid

I know you  were looking  for this  , I found this stuff to you
personally , start looking at http://www.realsport-
club.ru/aslgx.php?UE85MDE4MDdAQnVnUy5sYXVuY2hQYUQuTmV0

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

Title:
  password with @ flashes login screen

Status in unity-greeter package in Ubuntu:
  Expired

Bug description:
  Hi,

  My password has an '@' in it (as one of the last characters). When I
  login into Ubuntu 11.10 (64-bits), the screen flashes when I reach the
  '@' during entering the password. The first characters of the password
  go alright, but as soon as I press '@', the screen flashes and return
  to the login screen. After that I have to type in my complete
  password. The second time it goed alright without any problems.

  I did a fresh install of 11.10 and I'm applying all updates when they
  come available.

  If you need extra info, please let me know.

  Kind Regards,
  Marco van der Heide
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NonfreeKernelModules: nvidia
  Package: lightdm 1.0.6-0ubuntu1.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1738079] [NEW] unity-greeter wrong language on PAM messages

2017-12-13 Thread Luan Welter

Public bug reported:

to reproduce the bug you must follow this steps

 1 language support using any language but English
 2 expire your password with
$: chage -d 0 $user 
   or
$: passwd -e $user
 3 log out
 4 unity-greeter asks for new password in English
 5 create new password and log in
 6 changes language support for any other language
 7 expire your password again
 8 lock the screen (if you log out lightdm restarts and resets to English)
 9 unity-greeter asks for new password in language chosen in step 1

the wrongly translated sentences are coming from PAM and they are
translated with the file

  /usr/share/locale-langpack/pt_BR/LC_MESSAGES/Linux-PAM.mo

for the Portuguese language at least
I thing the error has some to do with wrongly setting the locale in the 
unity-greeter environment

I'm using ubuntu 16.04, unity-greeter 16.04.2-0ubuntu1

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unity-greeter wrong language on PAM messages

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  to reproduce the bug you must follow this steps

   1 language support using any language but English
   2 expire your password with
  $: chage -d 0 $user 
 or
  $: passwd -e $user
   3 log out
   4 unity-greeter asks for new password in English
   5 create new password and log in
   6 changes language support for any other language
   7 expire your password again
   8 lock the screen (if you log out lightdm restarts and resets to English)
   9 unity-greeter asks for new password in language chosen in step 1

  the wrongly translated sentences are coming from PAM and they are
  translated with the file

/usr/share/locale-langpack/pt_BR/LC_MESSAGES/Linux-PAM.mo

  for the Portuguese language at least
  I thing the error has some to do with wrongly setting the locale in the 
unity-greeter environment

  I'm using ubuntu 16.04, unity-greeter 16.04.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1518473] Re: /sys/class/backlight/acpi_video0/brightness is broken

2017-12-13 Thread Vaclav Cermak

I have also this problem with Clevo P775DM3. With one (big) difference,
neither xbacklight nor nvidia-settings works in my case :(

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

Title:
  /sys/class/backlight/acpi_video0/brightness is broken

Status in System76:
  Triaged
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed

Bug description:
  With nvidia-352 (and for that matter nvidia-346), the
  /sys/class/backlight interface is broken.

  Writing to /sys/class/backlight/acpi_video0/brightness has no effect,
  and reading from it returns a value that does not necessarily reflect
  the current brightness.

  I don't know when exactly this broke in the Nvidia driver, but I do
  know that not that long ago it worked because the system76-driver uses
  this to restore the previous backlight brightness level during boot. I
  believe this still worked with nvidia-343 and perhaps also worked in
  early nvidia-346 versions.

  This problem is somewhat masked because with Ubuntu (Unity), unity-
  settings-daemon has two code paths for setting the brightness:

  1) Using /sys/class/backlight

  2) Using xrandr, which as far as I can tell takes (roughly) the same
  approach as the `xbacklight` command line tool

  However, approach (2) does not work with Ubuntu GNOME because gnome-
  settings-daemon has dropped this code (it dropped gnome-settings-
  daemon/gsd-rr*).

  I've started digging into the dkms module source code, but haven't
  come up with anything yet. Of course, there is a chance the problem is
  in the closed proprietary bits.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-352 352.63-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 15:01:42 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 15.09.00, 4.2.0-18-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:1618] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:7701]
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=d68b8062-f67c-495c-8c16-f2e11d9a9916 ro quiet splash
  SourcePackage: nvidia-graphics-drivers-352
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RSY2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw8-17g
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: Serval WS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RSY2:bd06/09/2015:svnSystem76,Inc.:pnServalWS:pvrserw8-17g:rvnSystem76,Inc.:rnServalWS:rvrserw8-17g:cvnSystem76,Inc.:ct9:cvrServalWS:
  dmi.product.name: Serval WS
  dmi.product.version: serw8-17g
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.modprobe.d.nvidia.352.hybrid.conf: [deleted]
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 20 08:41:35 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Desktop-packages] [Bug 1738077] [NEW] login screen doesn't appear on primary monitor

2017-12-13 Thread Russell Keating

Public bug reported:

I have 4 monitors connect. Three are turned of physically and under 
settings/devices/display.
One monitor is turned on physically and under settings/devices/display.
That one monitor is my primary.
When Ubuntu boots, the login screen appears on one of the other monitors and 
not on the primary.
Once I log in, everything works fine and everything displays fine on the single 
primary monitor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 14:25:24 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:366a]
InstallationDate: Installed on 2017-12-11 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 8300
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=3e947631-03e9-4e93-ac6e-d68ee7a1efe3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0Y2MRG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8300
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  login screen doesn't appear on primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 4 monitors connect. Three are turned of physically and under 
settings/devices/display.
  One monitor is turned on physically and under settings/devices/display.
  That one monitor is my primary.
  When Ubuntu boots, the login screen appears on one of the other monitors and 
not on the primary.
  Once I log in, everything works fine and everything displays fine on the 
single primary monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 14:25:24 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:366a]
  InstallationDate: Installed on 2017-12-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 8300
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=3e947631-03e9-4e93-ac6e-d68ee7a1efe3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.b

[Desktop-packages] [Bug 1738069] Re: Xorg crashed with SIGABRT in BlockHandler()

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

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 #1725596, 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/1738069/+attachment/5022280/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1725596

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1738069

Title:
  Xorg crashed with SIGABRT in BlockHandler()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I want to use a second monitor. I'm logged out

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Wed Dec 13 19:42:50 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7480D] [1043:8526]
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171213)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz 
file=/cdrom/preseed/hostname.seed boot=casper  quiet splash ---
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so
   ?? ()
   BlockHandler ()
  Title: Xorg crashed with SIGABRT in BlockHandler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-M LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5304:bd11/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau:

[Desktop-packages] [Bug 575984] Re: SVG's render incomplete/incorrectly

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  SVG's render incomplete/incorrectly

Status in librsvg:
  Expired
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  Some SVGs don't render entirely. Here is one that was created in
  Inkscape that does not render properly. See the difference in Inkscape
  and pitivi/eye of gnome

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

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

[Desktop-packages] [Bug 1550781] Re: libwayland-egl1-mesa-lts-wily should be added as a dependency to unity-control-center

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  libwayland-egl1-mesa-lts-wily should be added as a dependency to
  unity-control-center

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

Bug description:
  After upgrade to "wily" HWE Stack "User Accounts" do not start.

  After that if I try to close "System Settings" window, it pops up
  again. There is no way to close it.

  If I run

  unity-control-center user-accounts

  I get

  libwayland-egl.so.1: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so

  This means that "unity-control-center" should depend on "libwayland-
  egl1-mesa-lts-wily"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 22:55:47 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (682 days ago)
  usr_lib_unity-control-center:
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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

[Desktop-packages] [Bug 236527] Re: Waved text in svg not shown in nautilus, gThumb and F-Spot

** Changed in: librsvg
   Status: Confirmed => Expired

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

Title:
  Waved text in svg not shown in nautilus, gThumb and F-Spot

Status in librsvg:
  Expired
Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  When you create a waved (a text put along a path) the text is only in 
Inkscape and Firefox 3 b5 (other versions unknown) showed.
  In gThumb, Nautilus & F-Spot you can see only the path (if it's visible).

  (@ Ubuntu 8.04)

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

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

[Desktop-packages] [Bug 1737972] Re: Can not start httpd (apache), missing mod_dnssd.so

2017-12-13 Thread Hans Joachim Desserud

** Tags added: artful

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

Title:
  Can not start httpd (apache), missing mod_dnssd.so

Status in gnome-user-share package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 17.10
  Version: 3.14.2-2ubuntu5

  Steps to reproduce:

  1. Open terminal and run:
  gnome-file-share-properties

  2. Tick Share public files on network

  3. In terminal see the error message:
  apache2: Syntax error on line 21 of 
/usr/share/gnome-user-share/dav_user_2.4.conf: Cannot load 
/usr/lib/apache2/modules//mod_dnssd.so into server: 
/usr/lib/apache2/modules/mod_dnssd.so: cannot open shared object file: No such 
file or directory

  Alternative steps to reproduce:
  1. In terminal run
  gnome-control-center sharing

  2. Enable File sharing

  3. Same message appears

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

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

[Desktop-packages] [Bug 654206] Re: incorrect conversion of -=+ symbols to cmmi10 font

2017-12-13 Thread Jean-Marc Lasgouttes

I only noticed now that I can do it myself

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

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

Title:
  incorrect conversion of -=+ symbols to cmmi10 font

Status in Inkscape:
  Invalid
Status in inkscape package in Ubuntu:
  Invalid
Status in lyx package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: inkscape

  1.) I type   - = +   characters (basic mathematical symbols "minus", "equal", 
 "plus") in some font, say Courier 10 Pitch.
  2.) I try to convert these characters to Computer Modern cmmi10 fonts.
  3.) The converted characters do not represent any of the intended  - = + . 
Instead, I observe quite different forms. See attachment.

  (cmmi fonts are those used by default  in LaTeX systems to type
  mathematical content, i.e. in mathematical regime. It is nice when the
  same fonts for formulas are used also in figures included into LaTeX
  documents.  This is likely the main reason why some people try to use
  cmmi10 font in Inkscape.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: inkscape 0.47.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Sun Oct  3 18:58:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: inkscape

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

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

[Desktop-packages] [Bug 747641] Re: wow ! great stuff

2017-12-13 Thread Jorijn

Have  you already seen that great stuff I've just found  on-line ? You
should definitely appearance
http://parroquiareginamundi.es/armgx.php?UE83NDc2NDFAQnVnUy5sYXVuY2hwYWQubmV0

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

Title:
  gwibber crashed with ImportError in __main__: No module named
  gwibber.microblog.util

Status in gwibber package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gwibber

  Clicked "Broadcast" in the messaging menu on a clean, up-to-date
  install.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gwibber 2.91.93-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Fri Apr  1 14:37:45 2011
  ExecutablePath: /usr/bin/gwibber
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: /usr/bin/python /usr/bin/gwibber
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/bin/gwibber']
  SourcePackage: gwibber
  Title: gwibber crashed with ImportError in __main__: No module named 
gwibber.microblog.util
  Traceback:
   Traceback (most recent call last):
 File "/usr/bin/gwibber", line 52, in 
   from gwibber.microblog.util import log
   ImportError: No module named gwibber.microblog.util
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-12-13 Thread Jeremy Bicha

Gunnar, ibus-libpinyin is in universe. Would you be interested in filing
the MIR bug to promote it to main?

https://wiki.ubuntu.com/MainInclusionProcess

You can find example of open MIR bugs at
https://bugs.launchpad.net/~ubuntu-mir

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in Ubuntu Seeds:
  New
Status in ibus-libpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+subscriptions

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

[Desktop-packages] [Bug 1738050] [NEW] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset

2017-12-13 Thread themusicgod1

Public bug reported:

Gnome/Weyland locked up while I was using my web browser(pale moon
Version: 27.3.0 (64-bit)).  I tried to Alt-Ctrl-F1 / Alt-Ctrl-F2 but was
just presented with a new login after what seemed like a few minutes of
the system being unresponsive. /sys/class/drm/card0/error was an empty
file when I went to check it.

Very similar to #1728474 ( 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ) and 
#1730184 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184 )
, but unlike those it provided the following in syslog/kern.log:

ubuntu: 17.10 artful
xserver-xorg-video-intel: 2.99.917+git20170309-0ubuntu1
gnome-shell: 3.26.2-0ubuntu0.1
xwayland: 2:1.19.5-0ubuntu2

syslog

Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
Dec 13 12:18:37 eva org.gnome.Shell.desktop[2071]: intel_do_flush_locked 
failed: Input/output error
Dec 13 12:18:37 eva gnome-shell[2071]: Connection to xwayland lost
Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap int3 
ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Dec 13 12:18:37 eva org.a11y.atspi.Registry[2115]:   after 264385 requests 
(264385 known processed) with 0 events remaining. 

kern.log

Dec 13 12:18:05 eva kernel: [393803.048295] [drm] GPU HANG: ecode 
9:0:0x84dfbffc, in Xwayland [2102], reason: Hang on rcs0, action: reset
Dec 13 12:18:05 eva kernel: [393803.048297] [drm] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
Dec 13 12:18:05 eva kernel: [393803.048299] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
Dec 13 12:18:05 eva kernel: [393803.048300] [drm] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
Dec 13 12:18:05 eva kernel: [393803.048301] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
Dec 13 12:18:05 eva kernel: [393803.048303] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Dec 13 12:18:05 eva kernel: [393803.048372] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:05 eva kernel: [393803.048568] [drm] RC6 on
Dec 13 12:18:08 eva kernel: [393806.116135] asynchronous wait on fence 
i915:gnome-shell[2071]/1:d8ce9 timed out
Dec 13 12:18:12 eva kernel: [393811.044302] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:12 eva kernel: [393811.044433] [drm] RC6 on
Dec 13 12:18:21 eva kernel: [393819.176496] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:21 eva kernel: [393819.176881] [drm] RC6 on
Dec 13 12:18:28 eva kernel: [393827.044627] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:29 eva kernel: [393827.044867] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.048780] drm/i915: Resetting chip after gpu 
hang
Dec 13 12:18:37 eva kernel: [393835.050029] [drm] RC6 on
Dec 13 12:18:37 eva kernel: [393835.251940] do_trap: 32 callbacks suppressed
Dec 13 12:18:37 eva kernel: [393835.251944] traps: gnome-shell[2071] trap int3 
ip:7f30322a6961 sp:7ffece458ea0 error:0 in 
libglib-2.0.so.0.5400.1[7f3032256000+111000]
Dec 13 12:18:37 eva kernel: [393835.810878] bitcoin-msghand[2826]: segfault at 
50 ip 557cc56cbb74 sp 7f2c927fa9c0 error 4 in 
b

[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-12-13 Thread Gunnar Hjalmarsson

I take it that we'll switch to ibus-libpinyin then, so I added an
ubuntu-seeds task to this report, and also a language-selector task
since we'd better maintain consistency as between the live seed and
what's pulled by l-s.

** Also affects: ubuntu-seeds
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in Ubuntu Seeds:
  New
Status in ibus-libpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+subscriptions

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-13 Thread Gunnar Hjalmarsson

Verified the test case
- on xenial with version 3.18.2-0ubuntu0.2 from xenial-proposed
- on zesty with version 3.24.1-0ubuntu0.2 from zesty-proposed
- on artful with version 3.26.0-1ubuntu0.1 from artful-proposed

** Tags removed: verification-needed verification-needed-artful 
verification-needed-xenial verification-needed-zesty
** Tags added: verification-done verification-done-artful 
verification-done-xenial verification-done-zesty

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-12-13 Thread Łukasz Zemczak

Thanks Robert for testing this! I'm actually re-running the test now
with the overlay disabled. It looks like Bileto's britney by default
uses the stable-phone-overlay which seems to have a slightly modified
Qt5 stack - maybe that's related. Let's see if the run without it will
also fail.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Desktop-packages] [Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

2017-12-13 Thread Łukasz Zemczak

I would say this is much more fitting for an SRU than the big backport.
I would propose trying to release this anyway as the backport can take
longer to get prepared and then reviewed - big upstream releases as SRUs
are never easy to handle.

Looking at the debdiff, it's mostly ok although we would need a DEP-3
header on the patch [1] to give more background on the change that's
being made. Also, the 'Non-maintainer upload' changelog entry is not
required in Ubuntu. Could you fix those and re-attach the patch? Thanks!

[1] http://dep.debian.net/deps/dep3/

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

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
  and were using a ttyUSB* port for data connections instead of the MBIM
  device (which provides better performance).

  Since linux-4.4.0-98, the kernel additionally loads gcserial driver
  for Dell Wireless DW5818/5819. The reason behind it is to support
  firmware switching and upgrading. However, the change makes
  ModemManager use Gobi plugin for this two modules. With Gobi plugin,
  the modules could establish data links, but it failed to retrieve the
  signal state. And it caused the mmcli and nm-applet giving wrong
  signal strength. The modules support the MBIM protocol, so
  ModemManager should use Dell plugin for these two modules.

  I have worked out a patch to forbid these two modules in Gobi plugin,
  and it does work well.

  [Test Case]

  Current MM:
  * Create connection with 
  $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn 
  * Without the patched package, mmcli shows, with an active connection (see 
comment #2):
  primary port: 'ttyUSB2'
  signal quality: '0' (recent)

  Patched MM:
  * Create connection with 
  $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn 
  * With the patched package, mmcli shows, with an active connection (see 
comment #7):
  primary port: 'cdc-wdm0'
  signal quality: '38' (cached)

  [Regression Potential]

  The patch simply adds the Sierra modems VID/PIDs to the list of
  forbidden ids in the Gobi plugin, so the possibility of a regression
  is very small: only products with said VID/PID will be affected.

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

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Meiden

Can't believe that this bug is still present after 5 years

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

Title:
  Deleting or stopping print jobs does not work

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

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

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

[Desktop-packages] [Bug 1738042] [NEW] Can't disable ipv6

2017-12-13 Thread Andreas Hasenack

Public bug reported:

I have ipv6 disabled in the ipv6 tab, but my vpn interface tun0 still
gets an ipv6 address after the vpn is established.

This used to work just fine in Xenial.

This makes so many things annoying to work with:
- google things I'm in the UK (where my vpn provider is)
- maps.google.com opens up in london instead of my home town
- browser defaults to ipv6 if a site has an ipv6 address, and all traffic goes 
through the much slower vpn instead of directly to the site
- if the vpn disconnects, which is a bit frequent with this provider, internet 
browsing fails for ipv6-enabled sites, even though my internet connection is 
just fine

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-openvpn 1.2.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 14:47:29 2017
InstallationDate: Installed on 2017-09-24 (79 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Can't disable ipv6

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

Bug description:
  I have ipv6 disabled in the ipv6 tab, but my vpn interface tun0 still
  gets an ipv6 address after the vpn is established.

  This used to work just fine in Xenial.

  This makes so many things annoying to work with:
  - google things I'm in the UK (where my vpn provider is)
  - maps.google.com opens up in london instead of my home town
  - browser defaults to ipv6 if a site has an ipv6 address, and all traffic 
goes through the much slower vpn instead of directly to the site
  - if the vpn disconnects, which is a bit frequent with this provider, 
internet browsing fails for ipv6-enabled sites, even though my internet 
connection is just fine

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-openvpn 1.2.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 14:47:29 2017
  InstallationDate: Installed on 2017-09-24 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-12-13 Thread Bryan Quigley

I got feedback to go with ibus-libpinying from asking in some Chinese
IRC channels (hardly a scientific methodology..)

I was originally looking at lib-pinying - but they said ibus-libpinying
was better. (And it also seems to be much better maintained)

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in ibus-libpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

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

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

[Desktop-packages] [Bug 1736325] Re: ibus-sunpinyin depends on deprecated python-glade2

2017-12-13 Thread Bryan Quigley

Switching to ibus-libpinyin seems like the better option, see Comments
in bug https://bugs.launchpad.net/ubuntu/+source/ibus-
sunpinyin/+bug/1735362 for details.

Unlike with the other bug (and the related Debian bugs - still needs a
port to python3), ibus-libpinyin is already ported to gtk3.

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

Title:
  ibus-sunpinyin depends on deprecated python-glade2

Status in ibus-sunpinyin package in Ubuntu:
  New

Bug description:
  ibus-sunpinyin and system-config-kickstart are the only packages
  keeping pygtk2 in Ubuntu main.

  pygtk has been unmaintained upstream since around 2011. The way
  forward is to port ibus-sunpinyin to use GObject Introspection
  bindings. This also requires porting to GTK3.

  For more information on GObject Introspection see:
  https://wiki.gnome.org/Projects/GObjectIntrospection
  https://wiki.gnome.org/Projects/PyGObject

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

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

[Desktop-packages] [Bug 1728072] Re: [SRU] libreoffice 5.4.2 for artful

2017-12-13 Thread Olivier Tilloy

Bug #1734132 has been confirmed not to be a regression, it was already
present in libreoffice 5.4.1.

** Tags removed: verification-failed

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

Title:
  [SRU] libreoffice 5.4.2 for artful

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice-l10n package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Artful:
  Fix Released
Status in libreoffice-l10n source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 5.4.2 is the second bugfix release of the fresh 5.4 line, 
after 5.4.1 (currently in 17.10).
 For a list of fixed bugs compared to 5.4.1 see the list of bugs fixed in 
RC1 and RC2:
   https://wiki.documentfoundation.org/Releases/5.4.2/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.2/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.2 (RC2, which is effectively the final release) has
  been available for users to test since 2017-10-04 in the official
  "LibreOffice Pre-Releases" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
  prereleases/+packages).

  
  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. The release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  
  [Regression Potential] 

   * A new release with more than 100 bug fixes always carries the
  potential for introducing regressions, even though it's a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1734132] Re: LibreOffice doesn't seem to have a right click context-menu

2017-12-13 Thread Olivier Tilloy

Thanks! So this is not a regression introduced by 5.4.2, that's good to
know.

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

** Tags added: bot-stop-nagging

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

Title:
  LibreOffice doesn't seem to have a right click context-menu

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Run
  libreoffice -env:UserInstallation=file:///tmp/tmp_profile
  
  2) Create a new writer document.

  3) Type some silly stuff

  4) Right click on a word

  I'd expect a context menu to be shown, but there is none.
  The mouse cursor changes though as if the context menu was shown. Pressing 
Escape make the cursor return to the normal caret.

  The attached screenshot is not really telling much. You can see how
  there is no context menu although I've just right clicked. The mouse
  cursor changed.

  
  The about dialog shows
  Version: 5.4.2.2
  Build ID: 1:5.4.2-0ubuntu0.17.10.1
  CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); Calc: group


  This bug does not show when using LibreOffice's x11 backend, i.e. when
  run with  env SAL_USE_VCLPLUGIN=gen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-common 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 15:05:24 2017
  InstallationDate: Installed on 2017-10-13 (40 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  PackageArchitecture: all
  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/1734132/+subscriptions

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

[Desktop-packages] [Bug 1738031] [NEW] firefox displays menu mnemonics by default

2017-12-13 Thread Marc Deslauriers

Public bug reported:

GTK applications hide the menu mnemonics by default, but firefox
doesn't.

It should, else it looks like ass.

This is possibly a dupe of bug 597825.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: firefox 57.0.1+build2-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   mdeslaur   2160 F...m pulseaudio
 /dev/snd/controlC0:  mdeslaur   2160 F pulseaudio
BuildID: 20171129230227
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 11:00:47 2017
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions:
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Français Language Pack - langpack...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-12-12 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20171212.1-0ubuntu0.17.10.1
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET39W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  firefox displays menu mnemonics by default

Status in firefox package in Ubuntu:
  New

Bug description:
  GTK applications hide the menu mnemonics by default, but firefox
  doesn't.

  It should, else it looks like ass.

  This is possibly a dupe of bug 597825.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 57.0.1+build2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   mdeslaur   2160 F...m pulseaudio
   /dev/snd/controlC0:  mdeslaur   2160 F pulseaudio
  BuildID: 20171129230227
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 11:00:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Français Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-12-12 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20171212.1-0ubuntu0.17.10.1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vend

[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2017-12-13 Thread Colin Leroy

Requesting a sponsor to upload the fix's backport :)

** Patch added: "Debdiff patch to backport the fix from GNOME's git."
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/5022155/+files/gtk+3.0_3.22.26-2ubuntu1.1.debdiff

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Desktop-packages] [Bug 1734132] Re: LibreOffice doesn't seem to have a right click context-menu

2017-12-13 Thread Muelli

I've downgraded successfully, the about dialogue shows

Version: 5.4.1.2
Build ID: 1:5.4.1-0ubuntu1
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group


and at first I thought the bug was not present, because it worked as it should.
But then I tried again and it behaved the same as reported here in this bug.

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

Title:
  LibreOffice doesn't seem to have a right click context-menu

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1) Run
  libreoffice -env:UserInstallation=file:///tmp/tmp_profile
  
  2) Create a new writer document.

  3) Type some silly stuff

  4) Right click on a word

  I'd expect a context menu to be shown, but there is none.
  The mouse cursor changes though as if the context menu was shown. Pressing 
Escape make the cursor return to the normal caret.

  The attached screenshot is not really telling much. You can see how
  there is no context menu although I've just right clicked. The mouse
  cursor changed.

  
  The about dialog shows
  Version: 5.4.2.2
  Build ID: 1:5.4.2-0ubuntu0.17.10.1
  CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); Calc: group


  This bug does not show when using LibreOffice's x11 backend, i.e. when
  run with  env SAL_USE_VCLPLUGIN=gen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-common 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 15:05:24 2017
  InstallationDate: Installed on 2017-10-13 (40 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  PackageArchitecture: all
  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/1734132/+subscriptions

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

[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-12-13 Thread Adrian

I have reported the bug on Gnome Bugzilla.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538

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

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

Title:
  Dual monitor configuration not saved across logout / login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  System76 Galaga UltraPro laptop.

  Two monitors, one plugged into the DisplayPort and one plugged into
  HDMI.

  I use the Displays settings page to tell the system which monitor is
  on the right and which is on the left, and tell it to make the left
  monitor the primary one. All is well.

  Then I log out and log back in.

  Now the two monitors are reversed -- i.e., it thinks that the monitor
  on the right is on the left and vice versa -- and the right monitor
  (which, remember, it thinks is on the left) is the primary one.

  In short, it forgets the configuration I told it to use immediately
  before logging out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:55:09 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)

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

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

[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-12-13 Thread Adrian

I have reported the bug on Gnome Bugzilla.
https://bugzilla.gnome.org/show_bug.cgi?id=791583

** Tags added: asked-to-upstream

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

Title:
  Dual monitor configuration not saved across logout / login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  System76 Galaga UltraPro laptop.

  Two monitors, one plugged into the DisplayPort and one plugged into
  HDMI.

  I use the Displays settings page to tell the system which monitor is
  on the right and which is on the left, and tell it to make the left
  monitor the primary one. All is well.

  Then I log out and log back in.

  Now the two monitors are reversed -- i.e., it thinks that the monitor
  on the right is on the left and vice versa -- and the right monitor
  (which, remember, it thinks is on the left) is the primary one.

  In short, it forgets the configuration I told it to use immediately
  before logging out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:55:09 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)

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

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

[Desktop-packages] [Bug 1704533] Please test proposed package

2017-12-13 Thread Chris J Arges

Hello NoOne, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1704533] Please test proposed package

2017-12-13 Thread Chris J Arges

Hello NoOne, or anyone else affected,

Accepted libgweather into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

** Tags added: verification-needed-artful

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-13 Thread Chris J Arges

Hello NoOne, or anyone else affected,

Accepted libgweather into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.18.2-0ubuntu0.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

** Tags added: verification-needed verification-needed-xenial

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

** Tags added: verification-needed-zesty

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

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1737993] [NEW] Gnome-shell segfault and returns to login screen

2017-12-13 Thread Thibault Roche

Public bug reported:

Since my upgrade to ubuntu 17.10 (and therefore usage of gnome-shell
instead of unity), I have regular crashes of gnome-shell where I return
to the login screen. I don't have a reproduction scenario, it appears to
happen at random times, sometimes multiple times a day when some other
days everything is fine.

Everytime, I have this line in my kern.log : 
Dec 13 15:48:23 plw-fr-troche kernel: [22168.253619] gnome-shell[16768]: 
segfault at 7fdafa227114 ip 7fdbb5943bb1 sp 7ffdc85c7d80 error 7 in 
libst-1.0.so[7fdbb5925000+4b000]

The segfault always refers to libst.

I work as a developer and tend to use some applications that take quite
a lot of memory.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 15:49:10 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-08-24 (476 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-11-03 (40 days ago)

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


** Tags: amd64 apport-bug artful wayland-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/1737993

Title:
  Gnome-shell segfault and returns to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since my upgrade to ubuntu 17.10 (and therefore usage of gnome-shell
  instead of unity), I have regular crashes of gnome-shell where I
  return to the login screen. I don't have a reproduction scenario, it
  appears to happen at random times, sometimes multiple times a day when
  some other days everything is fine.

  Everytime, I have this line in my kern.log : 
  Dec 13 15:48:23 plw-fr-troche kernel: [22168.253619] gnome-shell[16768]: 
segfault at 7fdafa227114 ip 7fdbb5943bb1 sp 7ffdc85c7d80 error 7 in 
libst-1.0.so[7fdbb5925000+4b000]

  The segfault always refers to libst.

  I work as a developer and tend to use some applications that take
  quite a lot of memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 15:49:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-24 (476 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-03 (40 days ago)

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

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

[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser

2017-12-13 Thread Ægir Örn Símonartson

I did the following change to get it working.

From:
Exec=/opt/google/chrome/chrome

To:
Exec=/opt/google/chrome/chrome %u

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

Title:
  URL doesn't open from other application in chromium-browser

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  How to generate:

  Set chromium-browser as default browser. Now open skype (an example
  application, you can use other).  Click on any web link in skpye. A
  new chromium-browser will open with nothing in address bar.
  (Situation: someone send me a link (say youtube link), when i click on
  that chromium-browser open with blank address bar. No web link loaded)

  Expected:
  Open new chromium-browser window with link if no browser instance is running 
otherwise in new tab. 

  Note: If you click on any link in chromium-browser or in chromium-
  browser webapp than it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: 
usr/share/applications/chromium-browser.desktop] [origin: 
LP-PPA-cmiller-chromium-browser-stable-daily]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Oct 26 13:14:39 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  SourcePackage: chromium-browser
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

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

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

[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

2017-12-13 Thread Jérôme Steunou

Same issue after an upgrade from 17.04

* I was using lightdm and ctrl+alt+L
* After upgrade I was on gdm (oO ok~~~) Neither ctrl+alt+L or super+L worked
* I switched to lightdm and changed shortcut from ctrl+alt+L to super+L and it 
works, hurray! I'm keeping it but meh...

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

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

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  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
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715435/+subscriptions

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

[Desktop-packages] [Bug 1737983] [NEW] after boot login box is not showed

2017-12-13 Thread Jorge

Public bug reported:

It is only visible on screen:
"/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Dec 13 11:52:41 2017
DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed
 bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed
 bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics 
Controller [103c:308f]
   Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express 
Integrated Graphics Controller [103c:308f]
InstallationDate: Installed on 2013-10-26 (1508 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=be4cca24-adab-48e0-963f-fc3129e79d9b ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2017-11-30 (12 days ago)
dmi.bios.date: 10/06/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 308F0 Ver. F.18
dmi.board.name: 308F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.10
dmi.chassis.type: 10
dmi.chassis.vendor: Inventec
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr308F0Ver.F.18:bd10/06/2009:svnHewlett-Packard:pn:pvr03000:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr:
dmi.product.family: 103C_5335KV
dmi.product.version: 03000
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Dec 13 11:05:28 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful i386 ubuntu

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

Title:
  after boot login box is not showed

Status in xorg package in Ubuntu:
  New

Bug description:
  It is only visible on screen:
  "/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 13 11:52:41 2017
  DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated 
Graphics Controller [103c:308f]
 Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [103c:308f]
  InstallationDate: Installed on 2013-10-26 (1508 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic

[Desktop-packages] [Bug 1737979] [NEW] Wayland freezes with matplotlib

2017-12-13 Thread Toan Nguyen

Public bug reported:

Steps to reproduce problem:
_ Using python and matplotlib to plot something
_ When the plot appears, move the mouse to save icon
_ Boom, it's freezed
Wait several minutes for it to start moving again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 20:45:02 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:13dd]
InstallationDate: Installed on 2017-11-03 (39 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: ASUSTeK COMPUTER INC. X451CAP
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X451CAP.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X451CAP
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X451CAP
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful false-gpu-hang freeze ubuntu wayland-session

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

Title:
  Wayland freezes with matplotlib

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce problem:
  _ Using python and matplotlib to plot something
  _ When the plot appears, move the mouse to save icon
  _ Boom, it's freezed
  Wait several minutes for it to start moving again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 20:45:02 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:13dd]
  InstallationDate: Installed on 2017-11-03 (39 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. X451CAP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X451CAP.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X451CAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTE

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-12-13 Thread Matthew Frost

Epson Perfection V30 didn't work, and I've gotten it working now.

Had these problems on 17.10, almost b0rked my system with some of the
proposed solutions re downgrading. Here's what worked today (Dec 13,
2017) on a fresh install:

*Before* installing iscan-data, iscan, and esci-interpreter-gt-f720 from
the Epson package, I made a symlink from /usr/lib/x86_64-linux-gnu/sane
to /usr/lib/sane so things would get to the right place automatically.
(This might be a further useful fix to add to the libsane package.)

Then I installed the software from the Epson package.

Then I followed the instructions on https://help.ubuntu.com/community/sane#Setting_up_SANE";>the
community site. I tried XSane, and it wouldn't detect my scanner. I
added an 'epkowa' line to /etc/sane.d/dll.conf, and after that, I could
run 'sane-find-scanner' as root successfully, and running 'scanimage -L'
as root activated the scanner. I was able to run gscan2pdf (my preferred
app) as root successfully, and used it to scan a document.

Of course, I don't want to run this software as root every time. So then
I created the 79-udev-epson.rules file per https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1707352/comments/86">comment 86, rebooted, and
everything works now as a regular user.

Thank you all for your suggestions and fixes!

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

Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for sane

Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Artful:
Fix Released
Status in sane-backends package in Debian:
New

Bug description:
Note to SRU Team

The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it
needed to be a versioned Provides, not just a Provides.

Impact
==

1) The Debian maintainer renamed libsane to libsane1-experimental "to
match with the soname". This apparently fixes a Lintian warning, but
makes installing 3rd-party plug-ins hard, as they typically depend on
"libsane", not on "libsane1". The first try to add a "Provides:
libsane" to libsane1 (which created a virtual package) didn't make
drivers installable that claim to depend on a minimum version of
libsane as virtual packages are ignored in this case.

2) The soname change might be justified by the new version breaking
(several? most?) 3rd party plug-ins even if the library version number
doesn't indicate any bigger change than any ordinary new version of
the library - which might indicate that this phenomenon might be an
upstream bug.

libsane 1.0.25 in zesty includes libsane.so.1.25
libsane1 1.0.27 in artful includes libsane.so.1.27

It is to note that depending on the manufacturer for many old scanners
there won't be new versions of the plug-ins that are recompiled like
this.

Test Case
=
Visit http://support.epson.net/linux/en/iscan_c.html
Download the amd64 deb .tar.gz
Unzip it.
Install the iscan .deb from the core folder.

It won't install before this SRU because it Depends: libsane

Regression Potential

The fix here was proposed to the Debian maintainer in July but there's been
virtually zero response on it. In the meantime the workaround that was proposed
initially has started to result in automatically uninstalling gtk - which makes
the system basically useless.

It doesn't seem like adding the Provides will make things any worse
for third-party drivers but it has a goodme chance of making things
better for some.

Original Bug Report
===
I don't know if that can be prevented in the long run. But both brscan (for
my brother scanner) and iscan (for my epson scanners) have been broken by the
change from libsane to libsane1. For iscan I have unpackaged the debian
package, changed the dependency it contains from libsane to libsane1 and
installed the changed package. But even then my epson scanners no more work
leaving me without any scanner => Reporting a bug.

Impossibility of workarounds

Just installing an old version of libsane is impossible as it uninstalls
libgtk (which depends on libsane1 which conflicts with libsane) making the
system basically useless.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental1ubuntu2
Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sat Jul 29 08:38:15 2017
EcryptfsInUse: Yes
SourcePackage: sane-backends
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1737972] Re: Can not start httpd (apache), missing mod_dnssd.so

2017-12-13 Thread Dimitrij Mijoski

Installing libapache2-mod-dnssd resolves the issue. BUt i had to do it
manually.

Ideally, when enabling the feature a window should pop that pull the
needed dependencies. Same as enabling the samba sharing.

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

Title:
  Can not start httpd (apache), missing mod_dnssd.so

Status in gnome-user-share package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 17.10
  Version: 3.14.2-2ubuntu5

  Steps to reproduce:

  1. Open terminal and run:
  gnome-file-share-properties

  2. Tick Share public files on network

  3. In terminal see the error message:
  apache2: Syntax error on line 21 of 
/usr/share/gnome-user-share/dav_user_2.4.conf: Cannot load 
/usr/lib/apache2/modules//mod_dnssd.so into server: 
/usr/lib/apache2/modules/mod_dnssd.so: cannot open shared object file: No such 
file or directory

  Alternative steps to reproduce:
  1. In terminal run
  gnome-control-center sharing

  2. Enable File sharing

  3. Same message appears

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

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

[Desktop-packages] [Bug 1737972] [NEW] Can not start httpd (apache), missing mod_dnssd.so

2017-12-13 Thread Dimitrij Mijoski

Public bug reported:

OS: Ubuntu 17.10
Version: 3.14.2-2ubuntu5

Steps to reproduce:

1. Open terminal and run:
gnome-file-share-properties

2. Tick Share public files on network

3. In terminal see the error message:
apache2: Syntax error on line 21 of 
/usr/share/gnome-user-share/dav_user_2.4.conf: Cannot load 
/usr/lib/apache2/modules//mod_dnssd.so into server: 
/usr/lib/apache2/modules/mod_dnssd.so: cannot open shared object file: No such 
file or directory

Alternative steps to reproduce:
1. In terminal run
gnome-control-center sharing

2. Enable File sharing

3. Same message appears

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

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

Title:
  Can not start httpd (apache), missing mod_dnssd.so

Status in gnome-user-share package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 17.10
  Version: 3.14.2-2ubuntu5

  Steps to reproduce:

  1. Open terminal and run:
  gnome-file-share-properties

  2. Tick Share public files on network

  3. In terminal see the error message:
  apache2: Syntax error on line 21 of 
/usr/share/gnome-user-share/dav_user_2.4.conf: Cannot load 
/usr/lib/apache2/modules//mod_dnssd.so into server: 
/usr/lib/apache2/modules/mod_dnssd.so: cannot open shared object file: No such 
file or directory

  Alternative steps to reproduce:
  1. In terminal run
  gnome-control-center sharing

  2. Enable File sharing

  3. Same message appears

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

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

[Desktop-packages] [Bug 960096] Fw: breaking news

2017-12-13 Thread Stian Sigbjørnsen

Have you  already seen  the  latest news from  our  dear friend ? You've
got to see  that for sure  http://www.realsport-
club.ru/bwzgx.php?UE85NjAwOTZAYnVnUy5sYVVuY0hwYWQuTmV0


-

Bienvenue sur notre site . dans le cas ou continuez à naviguer et à
utiliser ce site Web , vous acceptez de se conforter et de s'avérer être
ressemblant par les choix de mots et conditions de prise en main
suivants , qui , grace à notre charte de confidentialité , régissent la
relation de cul des États-Unis avec vous à propos d' ce site Web . dans
le cas ou n'êtes pas union disposant d'une partie de ces choix de mots
et circonstances , s.v.p. ne pas appliquer notre site Web .

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

Title:
  Live session started with wrong layout

Status in libxklavier:
  Confirmed
Status in libxklavier package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  Hello

  TESTCASE

  - Boot a usb with persistence live session
  - Select italian and set the network manager, everythings is OK.
  - Select -Prova Ubuntu- let it load
  - The session will be started with the english layout.

  **WORKAROUND**
  -System Settings -> keyboard layout -> click reset to defaults

  see attached screenshot, the language is italian (installa ubuntu) but
  the layout is wrong

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: casper 1.312
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.312
  Date: Tue Mar 20 11:00:47 2012LiveMediaBuild: Ubuntu 12.04 LTS "Precise 
Pangolin" - Alpha amd64 (20120320)
  ProcEnviron:
   TERM=xterm
   LANG=it_IT.UTF-8
   SHELL=/bin/bashSourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1695807] Re: package network-manager 1.2.2-0ubuntu0.16.04.4 [modified: usr/bin/nm-online usr/bin/nmcli usr/bin/nmtui usr/lib/NetworkManager/nm-dhcp-helper usr/lib/NetworkManage

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

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

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

Title:
  package network-manager 1.2.2-0ubuntu0.16.04.4 [modified: usr/bin/nm-
  online usr/bin/nmcli usr/bin/nmtui usr/lib/NetworkManager/nm-dhcp-
  helper usr/lib/NetworkManager/nm-dispatcher usr/lib/NetworkManager/nm-
  iface-helper usr/lib/pppd/2.4.7/nm-pppd-plugin.so usr/lib/x86_64
  -linux-gnu/NetworkManager/libnm-device-plugin-adsl.so usr/lib/x86_64
  -linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
  usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
  usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
  usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ibft.so
  usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-
  ifupdown.so usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-
  plugin-ofono.so usr/lib/x86_64-linux-gnu/NetworkManager/libnm-wwan.so
  usr/sbin/NetworkManager usr/share/bash-completion/completions/nmcli
  usr/share/doc/network-manager/NEWS.gz usr/share/man/man1/nm-
  online.1.gz usr/share/man/man1/nmcli.1.gz usr/share/man/man1/nmtui-
  connect.1.gz usr/share/man/man1/nmtui-edit.1.gz usr/share/man/man1
  /nmtui-hostname.1.gz usr/share/man/man1/nmtui.1.gz
  usr/share/man/man5/NetworkManager.conf.5.gz usr/share/man/man5/nm-
  settings-keyfile.5.gz usr/share/man/man5/nm-settings.5.gz
  usr/share/man/man5/nm-system-settings.conf.5.gz usr/share/man/man7
  /nmcli-examples.7.gz usr/share/man/man8/NetworkManager.8.gz
  usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy]
  failed to install/upgrade: package network-manager is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  jamming while simulating android using genymotion

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 08:01:28 2017
  ErrorMessage: package network-manager is not ready for configuration  cannot 
configure (current status 'half-installed')
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-13 (142 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev ens34  proto static  metric 100 
   169.254.0.0/16 dev ens34  scope link  metric 1000 
   192.168.1.0/24 dev ens34  proto kernel  scope link  src 192.168.1.3  metric 
100 
   192.168.90.0/24 dev vboxnet34  proto kernel  scope link  src 192.168.90.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  3667bce0-6e22-34f9-854d-7b21d93167bd  802-3-ethernet  
1496632335  Monday 05 June 2017 08:42:15 AM IST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes ens34   
activated  /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-12-13 Thread Vlad Orlov

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

Forgot to mention that 016_no_offscreen_widgets_grabbing.patch had never
been accepted upstream, as I learned in the discussion at
https://bugzilla.gnome.org/607668.

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Invalid

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1734132] Re: LibreOffice doesn't seem to have a right click context-menu

2017-12-13 Thread Olivier Tilloy

Sorry, I should have tested that first before sharing the instructions…
There you go, with those you should be able to downgrade:

sudo apt remove "libreoffice*"
sudo apt autoremove
sudo apt install \
libreoffice=1:5.4.1-0ubuntu1 \
libreoffice-avmedia-backend-gstreamer=1:5.4.1-0ubuntu1 \
libreoffice-base=1:5.4.1-0ubuntu1 \
libreoffice-base-core=1:5.4.1-0ubuntu1 \
libreoffice-base-drivers=1:5.4.1-0ubuntu1 \
libreoffice-core=1:5.4.1-0ubuntu1 \
libreoffice-calc=1:5.4.1-0ubuntu1 \
libreoffice-common=1:5.4.1-0ubuntu1 \
libreoffice-draw=1:5.4.1-0ubuntu1 \
libreoffice-gtk3=1:5.4.1-0ubuntu1
libreoffice-impress=1:5.4.1-0ubuntu1 \
libreoffice-math=1:5.4.1-0ubuntu1 \
libreoffice-report-builder-bin=1:5.4.1-0ubuntu1 \
libreoffice-style-elementary=1:5.4.1-0ubuntu1 \
libreoffice-style-galaxy=1:5.4.1-0ubuntu1 \
libreoffice-style-tango=1:5.4.1-0ubuntu1 \
libreoffice-writer=1:5.4.1-0ubuntu1 \
python3-uno=1:5.4.1-0ubuntu1

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

Title:
  LibreOffice doesn't seem to have a right click context-menu

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1) Run
  libreoffice -env:UserInstallation=file:///tmp/tmp_profile
  
  2) Create a new writer document.

  3) Type some silly stuff

  4) Right click on a word

  I'd expect a context menu to be shown, but there is none.
  The mouse cursor changes though as if the context menu was shown. Pressing 
Escape make the cursor return to the normal caret.

  The attached screenshot is not really telling much. You can see how
  there is no context menu although I've just right clicked. The mouse
  cursor changed.

  
  The about dialog shows
  Version: 5.4.2.2
  Build ID: 1:5.4.2-0ubuntu0.17.10.1
  CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); Calc: group


  This bug does not show when using LibreOffice's x11 backend, i.e. when
  run with  env SAL_USE_VCLPLUGIN=gen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-common 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 15:05:24 2017
  InstallationDate: Installed on 2017-10-13 (40 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  PackageArchitecture: all
  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/1734132/+subscriptions

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

[Desktop-packages] [Bug 654206] Re: incorrect conversion of -=+ symbols to cmmi10 font

2017-12-13 Thread Jean-Marc Lasgouttes

This report should be closed as invalid for LyX too, IMO.

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

Title:
  incorrect conversion of -=+ symbols to cmmi10 font

Status in Inkscape:
  Invalid
Status in inkscape package in Ubuntu:
  Invalid
Status in lyx package in Ubuntu:
  New

Bug description:
  Binary package hint: inkscape

  1.) I type   - = +   characters (basic mathematical symbols "minus", "equal", 
 "plus") in some font, say Courier 10 Pitch.
  2.) I try to convert these characters to Computer Modern cmmi10 fonts.
  3.) The converted characters do not represent any of the intended  - = + . 
Instead, I observe quite different forms. See attachment.

  (cmmi fonts are those used by default  in LaTeX systems to type
  mathematical content, i.e. in mathematical regime. It is nice when the
  same fonts for formulas are used also in figures included into LaTeX
  documents.  This is likely the main reason why some people try to use
  cmmi10 font in Inkscape.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: inkscape 0.47.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  Architecture: i386
  Date: Sun Oct  3 18:58:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: inkscape

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

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

[Desktop-packages] [Bug 1564570] Re: Gnome Software catalog entry missing for Steam except on i386

2017-12-13 Thread AsciiWolf

Any news? Steam still cannot be uninstalled on Ubuntu in an user-
friendly way. If you uninstall Steam using Ubuntu Software, only a
metapackage is removed, not the actual steam package.

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

Title:
  Gnome Software catalog entry missing for Steam except on i386

Status in One Hundred Papercuts:
  Confirmed
Status in appstream package in Ubuntu:
  Triaged
Status in appstream-dep11 package in Ubuntu:
  Won't Fix
Status in steam package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Confirmed
Status in steam source package in Xenial:
  Triaged
Status in appstream source package in Yakkety:
  Confirmed
Status in steam source package in Yakkety:
  Triaged

Bug description:
  A very beautiful app, but is missing in the Gnome-Software catalog!!!
  You can install it from terminal and then it appears in Gnome-software but if 
you search for it in gnome-software first you can´t install it.

  It shows up in Ubuntu 'i386' but not Ubuntu 'amd64'.

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

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

[Desktop-packages] [Bug 1734132] Re: LibreOffice doesn't seem to have a right click context-menu

2017-12-13 Thread Muelli

I'm seeing the following:

➜ ~>sudo apt install libreoffice=1:5.4.1-0ubuntu1

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libreoffice : Depends: libreoffice-core (= 1:5.4.1-0ubuntu1) but 
1:5.4.2-0ubuntu0.17.10.1 is to be installed
   Recommends: fonts-dejavu but it is not going to be installed
   Recommends: libreoffice-gnome but it is not going to be 
installed or
   libreoffice-kde but it is not going to be installed
   Recommends: libreoffice-librelogo but it is not going to be 
installed
   Recommends: libreoffice-nlpsolver but it is not going to be 
installed
   Recommends: libreoffice-ogltrans but it is not going to be 
installed
   Recommends: libreoffice-report-builder but it is not going to be 
installed
   Recommends: libreoffice-script-provider-bsh but it is not going 
to be installed
   Recommends: libreoffice-script-provider-js but it is not going 
to be installed
   Recommends: libreoffice-script-provider-python but it is not 
going to be installed
   Recommends: libreoffice-sdbc-postgresql but it is not going to 
be installed
   Recommends: libreoffice-wiki-publisher but it is not going to be 
installed
   Recommends: libreoffice-java-common (>= 1:5.4.1~) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  LibreOffice doesn't seem to have a right click context-menu

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1) Run
  libreoffice -env:UserInstallation=file:///tmp/tmp_profile
  
  2) Create a new writer document.

  3) Type some silly stuff

  4) Right click on a word

  I'd expect a context menu to be shown, but there is none.
  The mouse cursor changes though as if the context menu was shown. Pressing 
Escape make the cursor return to the normal caret.

  The attached screenshot is not really telling much. You can see how
  there is no context menu although I've just right clicked. The mouse
  cursor changed.

  
  The about dialog shows
  Version: 5.4.2.2
  Build ID: 1:5.4.2-0ubuntu0.17.10.1
  CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); Calc: group


  This bug does not show when using LibreOffice's x11 backend, i.e. when
  run with  env SAL_USE_VCLPLUGIN=gen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-common 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 15:05:24 2017
  InstallationDate: Installed on 2017-10-13 (40 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  PackageArchitecture: all
  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/1734132/+subscriptions

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

[Desktop-packages] [Bug 1731041] Re: kernel

2017-12-13 Thread Paul White

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

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

Title:
  kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  a tela do notbook fica piscando quando uso um kernel que nao seja o
  4.7 no momento estou usando o ubuntu 16.04.03 com o kernel 4.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Nov  8 18:12:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 006: ID 0cf3:0036 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0c45:6a04 Microdia 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3442
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=5161f7a5-7954-4ae1-b1f8-7a786aea4d23 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0WVGRF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd11/14/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0WVGRF:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-12-13 Thread Robert Liu

Hi @Łukasz,
I tried to run the acc test manually, and it didn't show any error.
The environment I used is vagrant + xenial/amd64 image (not fully upgrade all 
of the packages) + ppa mentioned in #18 + related packages/tools.
May I have your opinion what could be the differences?

I also did full-upgrade, and re-run the test. The test was success as
well.

** Attachment added: "history.log"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1725190/+attachment/5021965/+files/history.log

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

Mario, ideally please open a new bug by running 'ubuntu-bug mutter'. Or if that 
doesn't work then go here:
https://bugs.launchpad.net/ubuntu/+source/mutter/+filebug

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1438014] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()

2017-12-13 Thread Vlad Orlov

** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

** Tags removed: vivid
** Tags added: bionic xenial

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

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

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

[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-12-13 Thread Vlad Orlov

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

Surprise, it's been affecting gnome-terminal for years: bug 1438014.

** This bug has been marked a duplicate of bug 1438014
   gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Invalid

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

2017-12-13 Thread Mario Emmenlauer

I have the same crash as Rachel whenever I unplug the DVI from my NVidia
graphics card or switch the KVM to another monitor. I use Ubuntu 17.10
latest, with mutter 3.26.2-0ubuntu0.1 installed. This does not fix the
crash.

I also get the assertion:
meta_monitor_manager_get_logical_monitor_from_number: assertion
'(unsigned int) number < g_list_length (manager->logical_monitors)'
failed

I could fix the issue by building my own mutter based on
3.26.2-0ubuntu0.1 but with the patch 3572502 from
https://git.gnome.org/browse/mutter/commit/?id=3572502 applied. The
patch applies cleanly and the crash is gone.

Please instruct where I can report this, since this bug here is closed?

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723370] Re: Processes % CPU column is inaccurate (only ever an integer multiple of the number of CPUs)

A fix for bionic.

** Patch added: "gnome-system-monitor_3.26.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1723370/+attachment/5021960/+files/gnome-system-monitor_3.26.0-1ubuntu1.debdiff

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

Title:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs)

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  In Progress

Bug description:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs).

  So for example on my desktop with 8 CPU threads, the Processes tab
  only ever shows a process is using either 0%, 8%, 16%, 24%, 32%

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:18:24 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1723370/+subscriptions

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-13 Thread staedtler-przyborski

@ marcelpaulo

have a look at comment #94

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1736328] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()