[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Kai-Heng Feng]

So it didn't work.

Apparently someone found ways to workaround this issue:
https://github.com/kuba-moo/mt7601u/issues/64

** Bug watch added: github.com/kuba-moo/mt7601u/issues #64
   https://github.com/kuba-moo/mt7601u/issues/64

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] 

[Desktop-packages] [Bug 1730900] [NEW] "Login Screen" button not present in Region & Language

[Gunnar Hjalmarsson]

Public bug reported:

On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
Region & Language window includes a "Login Screen" button at the top
right, which allows me to set language, format and input sources also
system wide, i.e. affecting the login screen. The Ask Ubuntu answer
 shows its location.

However, on an (almost) fresh install of Ubuntu 17.10, that button is
not present.

I don't know what the intended design is in this respect.

* If the button is supposed to be there, some dependency necessary for
it to function might be missing.

* If the button is not supposed to be there, is there some other GUI way
to control those settings system wide?

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

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

Title:
  "Login Screen" button not present in Region & Language

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

Bug description:
  On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
  Region & Language window includes a "Login Screen" button at the top
  right, which allows me to set language, format and input sources also
  system wide, i.e. affecting the login screen. The Ask Ubuntu answer
   shows its location.

  However, on an (almost) fresh install of Ubuntu 17.10, that button is
  not present.

  I don't know what the intended design is in this respect.

  * If the button is supposed to be there, some dependency necessary for
  it to function might be missing.

  * If the button is not supposed to be there, is there some other GUI
  way to control those settings system wide?

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[luca.mg]

Hy all, just here to write that after exchanging a bunch of useless
emails with a kind chap from Brother customer support, he finally
redirected me to the "lab technicians", who wrote to me "read the faq,
or check over internet if there are solutions from the community".

-- 
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 1727628] Re: Please fix PLUGIN_FALLBACK_LOCATION variable in installer/pluginhandler.py with respect of new website

[zdohnal]

Till,

variable, which you are looking for, is in installer/pluginhandler.py on
line 46. But I don't know new link too.

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

Title:
  Please fix PLUGIN_FALLBACK_LOCATION variable in
  installer/pluginhandler.py with respect of new website

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  In Progress

Bug description:
  Hi,

  moving to new website https://developers.hp.com/ makes hp plugin non-
  downloadable - this breaks installing any printer where hp plugin is
  needed - please fix it immediately. I cannot find hp plugin on your
  new website, so I cannot even create a temporary patch, which could
  fix it. Patch would be changing fallback url in
  installer/pluginhandler.py to the newest url, where we can find hp
  plugin.

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

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[abautu]

The backup completed succesfully (while running automatically) after I
changed in /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop from

Exec=sh -c "ulimit -v 100; exec /usr/lib/x86_64-linux-gnu/deja-dup
/deja-dup-monitor"

to

Exec=sh -c "ulimit -v 100; ulimit -n 4096; exec /usr/lib/x86_64
-linux-gnu/deja-dup/deja-dup-monitor"

Limits file of process under /proc still shows 
Max open files1024 1048576  files

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  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: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730888] [NEW] package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

[Amit Ashok]

Public bug reported:

system on start gives the error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov  1 19:15:23 2017
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-06-17 (508 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8  metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: network-manager
Title: package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-08-01 (463 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Prakashs9a348811-d4b8-4ee7-a31e-1f8f002daa2c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
   ----
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

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


** Tags: amd64 apport-package xenial

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

Title:
  package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in network-manager package in Ubuntu:
  New

Bug description:
  system on start gives the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  1 19:15:23 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-06-17 (508 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: network-manager
  Title: package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (463 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Prakashs9a348811-d4b8-4ee7-a31e-1f8f002daa2c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI 

[Desktop-packages] [Bug 1730888] Re: package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in network-manager package in Ubuntu:
  New

Bug description:
  system on start gives the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  1 19:15:23 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-06-17 (508 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: network-manager
  Title: package libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (463 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Prakashs9a348811-d4b8-4ee7-a31e-1f8f002daa2c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  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/1730888/+subscriptions

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

[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Thomas P.]

Thanks for all your efforts.

$ uname -a
Linux video-box 4.13.0-17-generic #20~lp1716301+corequirks SMP Mon Nov 6 
04:37:44 EST 2017 x86_64 x86_64 x86_64 GNU/Linux
$ dmesg > dmesg_4.13.0-17.20~lp1716301+corequirks.txt

** Attachment added: "dmesg_4.13.0-17.20~lp1716301+corequirks.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/5005678/+files/dmesg_4.13.0-17.20~lp1716301+corequirks.txt

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor 

[Desktop-packages] [Bug 1730871] Re: Close lid action missing in Ubuntu 17.10

[Gunnar Hjalmarsson]

There is such a switch in Tweaks in the Power section, but you need to
install the gnome-tweaks-tool package to make Tweaks available.

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

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

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

Title:
  Close lid action missing in Ubuntu 17.10

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

Bug description:
  I tried to set my laptop not to suspend when closing the lid, I want it to 
download some files and not have the lid open, but it seemed to be impossible, 
there is no option  for that. I have no idea why not, all OS have this and it 
is a basic function for a laptop many change it depending on the temporary 
needs.
  A simple select option in Power should exist.


  I already filed a Gnome bug here:
  https://bugzilla.gnome.org/show_bug.cgi?id=790043

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 06:33:12 2017
  InstallationDate: Installed on 2017-10-21 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730871] [NEW] Close lid action missing in Ubuntu 17.10

[florin]

Public bug reported:

I tried to set my laptop not to suspend when closing the lid, I want it to 
download some files and not have the lid open, but it seemed to be impossible, 
there is no option  for that. I have no idea why not, all OS have this and it 
is a basic function for a laptop many change it depending on the temporary 
needs.
A simple select option in Power should exist.


I already filed a Gnome bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=790043

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.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 06:33:12 2017
InstallationDate: Installed on 2017-10-21 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Close lid action missing in Ubuntu 17.10

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

Bug description:
  I tried to set my laptop not to suspend when closing the lid, I want it to 
download some files and not have the lid open, but it seemed to be impossible, 
there is no option  for that. I have no idea why not, all OS have this and it 
is a basic function for a laptop many change it depending on the temporary 
needs.
  A simple select option in Power should exist.


  I already filed a Gnome bug here:
  https://bugzilla.gnome.org/show_bug.cgi?id=790043

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 06:33:12 2017
  InstallationDate: Installed on 2017-10-21 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 40872] Re: Desktop icons are allowed to overlap

[florin]

This is my last report:
https://gitlab.gnome.org/GNOME/nautilus/issues/108

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

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

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

[Desktop-packages] [Bug 40872] Re: Desktop icons are allowed to overlap

[florin]

Yes, @giannione that is the link. I will report a bug, too. At least to
annoy Gnome people, I have so little expectations of them to actually be
helpful.

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

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

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

[Desktop-packages] [Bug 1727742] Re: "peek" hangs gnome-shell Wayland sessions (but not Xorg)

[Daniel van Vugt]

** Summary changed:

- "peek" hangs Wayland display server
+ "peek" hangs gnome-shell Wayland sessions (but not Xorg)

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

Title:
  "peek" hangs gnome-shell Wayland sessions (but not Xorg)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have "peek" installed from its PPA repository as described at
  https://github.com/phw/peek#ubuntu .

  When I attempt to record a GIF with peek under Wayland, it counts down
  and then my display hangs. I can't even switch VTs, so the only thing
  I can do at this point is power-cycle my laptop. I know it's just the
  display hanging, not everything, because the music I'm listening to
  continues to play.

  This occurs whether or not I set GDK_BACKEND to x11 before launching
  peek.

  Peek works fine when I use it under Xorg instead of Xwayland.

  See also https://github.com/phw/peek/issues/202 , the bug I filed with
  the peek developers about this, but regardless of whether peek is
  doing something wrong, it shouldn't be able to cause the display
  server to hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:09:23 2017
  DistUpgraded: 2017-10-20 10:34:09,954 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics 
Controller [1558:7410]
  InstallationDate: Installed on 2017-05-19 (159 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System76, Inc. Galago UltraPro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, 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

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

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

[Desktop-packages] [Bug 1730478] Re: using shift key to wake up display causes invalid password

[Daniel van Vugt]

Yes, sounds like this might be a feature rather than a bug. Tapping
Shift repeatedly has special meaning :)

Scott, please check if you have Sticky Keys enabled:
https://help.gnome.org/users/gnome-help/stable/a11y-stickykeys.html.en

** 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/1730478

Title:
  using shift key to wake up display causes invalid password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Summary: hitting 'shift' before typing your password can get "stuck" down and
  cause you to not be able to log in.

  I have a habit of using the shift key wake the display of my system
  after i've been away from it for a while, and then typing my password.

  I started having trouble logging in, as if my fingers weren't typing the
  right password.  It took me a while to figure out what was going on, but i
  thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing
  the issue.  So I hit it again, and then logged in successfully.

  However, upon login I found that caps-lock was enabled.

  So to reproduce:
   a.) let the screen lock or lock it manually.
   b.) hit shift key (i hit left shift)
   c.) type password correctly: watch fail to login
   d.) note that you can hit caps-lock and then successfully login
   e.) note that after login, caps lock is set, that you didn't make this all 
up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 13:12:29 2017
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2015-07-23 (837 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  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/1730478/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

Rocko,

Sorry to hear about this problem. However with a large number of open
bugs with similar symptoms we can't pin down the exact cause of this one
without more information.

If you can then please try logging into the machine remotely (e.g. via
SSH), and run 'journalctl -f' before reproducing the bug. Do you see any
log messages that are helpful? How about from 'dmesg'?

Also while logged in remotely, after reproducing the problem please
check if the gnome-shell process is still running. And if so then please
run 'kill -ABRT' on it to generate a crash file which you can later
upload with 'ubuntu-bug' or 'apport-cli'.

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

** 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/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 103571] ✉Re: wow new catalogue

[etabeta]

Hey,


I found the last catalogue of your selected stuff, you can read it here 
http://www.trapeza.shop/cook.php?UE8xMDM1NzFAYnVncy5sYXVuY2hwYWQubmV0


Faithfully, Pietro Marchionda


From: Bug 103571 [mailto:103...@bugs.launchpad.net]
Sent: Tuesday, November 07, 2017 8:57 PM
To: tel...@iol.it
Subject: What a party!

Well,  that's a ton  of picture messaging, and a ton of pictures/videos.
That's for sure. Tap on photos and it'll break  it down  by camera roll,
photo  stream, and pictures transferred  from  a computer.

The  next thought is: how many  apps are actually  listed in that
screen that aren't built in, because every app takes  space to some
degree, and five 200mb apps  make up 1gb.


Sent from Mail for Windows 10

** Attachment added: "62DBCA456C36F170.jpg"
   
https://bugs.launchpad.net/bugs/103571/+attachment/5005622/+files/62DBCA456C36F170.jpg

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

Title:
  Cover art plugin regression: sidebar resizing results in bad image
  quality

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  I reported this upstream but they don't seem to think it's likely a
  problem on their end because "The cover art code was virtually
  unchanged between 0.9.8 and 0.10.0."


  This worked fine in 0.9.8 but is a regression in 0.10.0.

  Steps to reproduce:
  1. Make sure the cover art display area in the sidebar is small (or extremely 
tiny, to notice the issue easier)
  2. Start playing a track which you have a higher-resolution (than the size of 
the cover art area) cover.png image file
  in the directory for
  3. Resize the sidebar bigger, increasing the size of the cover art display 
area

  
  Actual results:
  A pixelated image, it resizes the small version of the cover art file it has
  made larger

  Expected results:
  A good quality cover art image, like in 0.9.8. Switching to a track with a
  different cover art image and back without changing the sidebar's size results
  in the good quality cover art image being used, as does disabling the cover 
art
  plugin and re-enabling it

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

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

[Desktop-packages] [Bug 1730700] Re: Mouse stopped working on my laptopt screen

[Daniel van Vugt]

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

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


** Tags added: noclick

** Summary changed:

- Mouse stopped working on my laptopt screen
+ Mouse stopped working on my laptop screen

** This bug has been marked a duplicate of bug 1181666
   gnome-shell randomly blocks mouse clicks from working in app windows

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

Title:
  Mouse stopped working on my laptop screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I can only hoover around my laptop screen, I can use the sidebar and
  external laptop. So far i haven't found a reasonable solution. Turning
  off laptop monitor just moved the problem to external monitor. I have
  Lenovo E470 with NVIDIA and i7, I'm using Ubuntu 16.04 lts

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

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

[Desktop-packages] [Bug 1730748] Re: gnome-shell froze and crashed

[Daniel van Vugt]

This looks like it:

Nov 07 20:13:10 hostname gnome-session-binary[7876]: WARNING:
Application 'org.gnome.Shell.desktop' killed by signal 11

...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

After the new bug report with a crash file has been created, please
comment here telling us the new bug ID. Please do not manually attach
any crash files to bugs - only use ubuntu-bug (or apport-cli).

** 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/1730748

Title:
  gnome-shell froze and crashed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Cannot say much except that I had opened gnome-terminal and suddenly
  the session just froze and crashed. I lost Wayland session and had to
  login again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 20:15:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-21 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1730748/+subscriptions

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

[Desktop-packages] [Bug 1730093] Re: Gnome suspends or blanks external monitor when laptop is docked

[Daniel van Vugt]

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

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


** Tags added: multimonitor suspend

** This bug has been marked a duplicate of bug 1722725
   GNOME Shell disabling wrong screen when docking laptop

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

Title:
  Gnome suspends or blanks external monitor when laptop is docked

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the default configuration, resuming my T440s on the Lenovo
  ultradock results in not detecting the external monitor followed by a
  suspend.

  If I open the lid while on the dock, gnome detects the external
  monitor and blanks the laptop display.  Then, closing the lid results
  in suspend.

  As a work around, using tweak tool (or UPower) to ignore the lid, does
  prevent the suspend.  But it is not automatic; each time, one must
  bring up the gnome control panel->devices->displays and manually
  select single display.  Then the lid may be closed without suspend.

  This worked fine in 17.04, so I'm hoping that the provides enough
  clues that this can be fixed easily.

  Thanks!  I am enjoying the new Ubuntu 17.10 generally, but this
  situation is annoying.

  System details:

  linux magpie 4.13.9-041309-generic #201710211231 SMP Sat Oct 21
  16:32:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  I'm trying a kernel from mainline, just to see if that matters; it
  doesn't.  Same behavior on stock 17.10 kernel.

  Software version:

  Package: gnome-settings-daemon
  Versions: 
  3.26.1-0ubuntu5 
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_artful_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.9-041309-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 12:32:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (546 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)

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

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

[Desktop-packages] [Bug 1730796] Re: Ubuntu 17.10 graphical login and desktop unreadable (no hsync, tearing) on AMD Epyc servers

[Daniel van Vugt]

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

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

Title:
  Ubuntu 17.10 graphical login and desktop unreadable (no hsync,
  tearing) on AMD Epyc servers

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

Bug description:
  Seen on both SuperMicro and Dell AMD Epyc based servers (that's right,
  I installed the desktop version of 17.10 on a server):

  Dell:
  $ lspci | grep VGA
  83:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Device 
0536 (rev 04)
  $ lspci -s 83:00 -n
  83:00.0 0300: 102b:0536 (rev 04)

  SuperMicro:
  $ lspci | grep VGA
  02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics 
Family (rev 41)
  $ lspci -s 02:00 -n
  02:00.0 0300: 1a03:2000 (rev 41)

  The Xwayland default is not a good one here, editing
  /etc/gdm3/custom.conf and removing the comment in front of
  WaylandEnable=false has fixed every system that has failed.

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

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

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

[Daniel van Vugt]

** Attachment removed: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/+attachment/4981563/+files/_usr_bin_gnome-shell.1000.crash

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

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

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

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1727232] Re: Default color profile looks very dull

[Daniel van Vugt]

It has to be a *correct* colour profile (i.e. one you made with a
colorimeter) or none at all. Seems the default one is a bit broken.

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

Title:
  Default color profile looks very dull

Status in chromium-browser package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Using the default Gnome color profile, everything looks very dull in
  Chromium. Just look at the colours of the lettering on www.google.com.

  To fix this I have to set:

Settings > Devices > Color > (my monitor) = OFF

  now restart Chromium and the color is correct and much more vibrant.

  So is it Chromium handling the color profile wrong, or Gnome providing
  a bad default profile that should never have been enabled by default?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
  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
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 1280x1024 1152x864 1280x720 
1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x480 720x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Oct 25 16:20:34 2017
  Desktop-Session:
   'None'
   'None'
   
'/home/dan/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-05-03 (175 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Wed Oct 18 21:05:32 2017)
  Load-Avg-1min: 0.18
  Load-Processes-Running-Percent:   0.2%
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1446940d-616b-4f78-926f-05ddb67580b8 ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

[Gunnar Hjalmarsson]

On 2017-11-08 01:27, Jung-Kyu Park wrote:
> @leejh76 , Hi Jong Hoon, It doesn't seem to quite related to this
> font issue.
> It seems a bug of input methods, I think , It would be better for you
> file a bug to Libreoffice team, or those input methods developers.

I agree with Jung-Kyu Park. I'd suggest that you file a separate bug
against the fcitx package to start with.

https://bugs.launchpad.net/ubuntu/+source/fcitx/+filebug

> @gunnarhj
> It works well for me in Ubuntu 17.10 under VB on macOS, If I can have
> a chance to test in machine, I would test more of it in Ubuntu 17.10
> and 18.04 (if it is possible)

Thanks for letting us know, and yes, of course it's possible to keep
testing. Actually there is no real deadline for this. Whenever an issue
is reported, we'll fix it if possible.

At this time it seems to me as if we'll likely complete the switch to
Noto as default fonts for Japanese and Korean in 18.04, so I will soon
propose the related changes to the seed branches.

However, I have one question as regards the Korean fonts: Up to Ubuntu
17.10, besides fonts-nanum and fonts-nanum-coding, also the fonts-
unfonts-core package has been installed by default for Korean users.

https://packages.ubuntu.com/artful/all/fonts-unfonts-core/filelist

If we switch to Noto, is it motivated to keep installing fonts-unfonts-
core by default?

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

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

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

[Desktop-packages] [Bug 1702082] Re: /usr/bin/nautilus:ERROR:nautilus-bookmark.c:351:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

[Bug Watch Updater]

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

** Changed in: nautilus
   Importance: Unknown => Medium

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

Title:
  /usr/bin/nautilus:ERROR:nautilus-
  bookmark.c:351:nautilus_bookmark_connect_file: assertion failed:
  (!nautilus_file_is_gone (bookmark->details->file))

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.20.4-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bf809b6dff6ba5f9da90cc650449a4b862e1d00f 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1730253] Re: Clamshell mode only works immediately after changing display settings

[Daniel van Vugt]

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

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


** Tags added: multimonitor

** This bug has been marked a duplicate of bug 1722725
   GNOME Shell disabling wrong screen when docking laptop

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

Title:
  Clamshell mode only works immediately after changing display settings

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

Bug description:
  I have just upgraded to Ubuntu 17.10 (and so switched from Unity to
  Gnome 3).

  I have a laptop and I sometimes use an external monitor with the
  laptop closed (clamshell mode), and I sometimes use the laptop monitor
  with no external monitor.

  If I change my display settings, eg if I change from mirrored display
  mode to extended desktop, or vice versa, it doesn't which direction I
  change it, the point is that I change it, then after that change, I
  can close my laptop lid, and the laptop will switch to just displaying
  on the external monitor, ie, it will work in clamshell mode.

  If I then unplug the external monitor, open the laptop and start using
  it with its own monitor, and then later I plug the monitor back in (at
  this time the monitor turns back on and displays according to whatever
  I had the settings at), and then close the laptop lid again, the
  laptop suspends, the external monitor turns off, ie clamshell mode
  doesn't work.

  The thing that seems to trigger to make clamshell mode work again is
  that I have to change the display settings, from mirrored to extended
  desktop or vice versa, doesn't matter which direction I change it in,
  as long as I change it, that seems to tell the laptop that it's
  allowed to go into clamshell mode when I close the lid.

  So it seems that unplugging the monitor (or maybe plugging it in)
  resets whatever prevents the laptop from suspending when the lid is
  closed, and reconfiguring the display settings turns it back on.

  I've Googled for solutions, most recommend configuring the laptop to
  not suspend when the lid is closed, but that's not an acceptable
  solution - I don't want the laptop to stay on when I unplug it and put
  it in my bag.

  Everything worked as expected with Ubuntu 17.04. The laptop suspended
  when I expected it to (I'm actually not sure if suspending was caused
  by unplugging the external monitor while the lid was closed, or
  unplugging the power while the lid was closed, I expect the latter),
  while closing the lid while an external monitor was connected didn't
  suspend (and again, perhaps this was actually closing the lid when
  power was connected that caused it to stay on, not sure).

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

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

[Desktop-packages] [Bug 1730796] [NEW] Ubuntu 17.10 graphical login and desktop unreadable (no hsync, tearing) on AMD Epyc servers

[Duane Voth]

Public bug reported:

Seen on both SuperMicro and Dell AMD Epyc based servers (that's right, I
installed the desktop version of 17.10 on a server):

Dell:
$ lspci | grep VGA
83:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Device 0536 
(rev 04)
$ lspci -s 83:00 -n
83:00.0 0300: 102b:0536 (rev 04)

SuperMicro:
$ lspci | grep VGA
02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics 
Family (rev 41)
$ lspci -s 02:00 -n
02:00.0 0300: 1a03:2000 (rev 41)

The Xwayland default is not a good one here, editing
/etc/gdm3/custom.conf and removing the comment in front of
WaylandEnable=false has fixed every system that has failed.

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

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

Title:
  Ubuntu 17.10 graphical login and desktop unreadable (no hsync,
  tearing) on AMD Epyc servers

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Seen on both SuperMicro and Dell AMD Epyc based servers (that's right,
  I installed the desktop version of 17.10 on a server):

  Dell:
  $ lspci | grep VGA
  83:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Device 
0536 (rev 04)
  $ lspci -s 83:00 -n
  83:00.0 0300: 102b:0536 (rev 04)

  SuperMicro:
  $ lspci | grep VGA
  02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics 
Family (rev 41)
  $ lspci -s 02:00 -n
  02:00.0 0300: 1a03:2000 (rev 41)

  The Xwayland default is not a good one here, editing
  /etc/gdm3/custom.conf and removing the comment in front of
  WaylandEnable=false has fixed every system that has failed.

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

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

[Desktop-packages] [Bug 1730072] Re: Gnome Night Light doesn't work

[HadiM]

The location setting was turned off and I just turned it on now. I try
to reboot but it still doesn't work.

My screen configuration is standard: I am using the screen of my laptop
(ASUS UX301L) without any external monitor.

Yes, the feature used to work before the official Ubuntu release (but I
can't remember exactly when it stopped working).

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

Title:
  Gnome Night Light doesn't work

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

Bug description:
  I have a similar issue as this bug
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1676131. But I am reopening according to what it is said
  in the last post of the above bug ticket.

  Gnome Night Light doesn't work on my system: Asus UX301L Notebook
  using Ubuntu 17.10 with the latest updates.

  It used to work and suddenly stopped working but I can't remember at
  what period exactly. I think it was before the official release...

  If you need more information, tell me.

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

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

[Desktop-packages] [Bug 1730093] Re: Gnome suspends or blanks external monitor when laptop is docked

[Martin D. Weinberg]

I refiled the bug at bugzilla.gnome.org as bug 790040.

The link is:  https://bugzilla.gnome.org/show_bug.cgi?id=790040

I'm really surprised that there are not more complaints about this.  To
be fair, the dock+external monitor setup has NOT worked perfectly in any
release Ubuntu release, including 16.04.  Although, before 17.10,
trouble only arose when moving the laptop between docks with different
monitors, so it was tolerable.

I sure hope this can be fixed.  I suppose I could cook up some sort of
udev script to handle dock changes for my situation but that is horrible
kludge, not a fix.

On 11/07/2017 05:13 PM, Sebastien Bacher wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> ** Package changed: gnome-settings-daemon (Ubuntu) => gnome-shell
> (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
>Importance: Undecided => Low
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039



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

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

Title:
  Gnome suspends or blanks external monitor when laptop is docked

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the default configuration, resuming my T440s on the Lenovo
  ultradock results in not detecting the external monitor followed by a
  suspend.

  If I open the lid while on the dock, gnome detects the external
  monitor and blanks the laptop display.  Then, closing the lid results
  in suspend.

  As a work around, using tweak tool (or UPower) to ignore the lid, does
  prevent the suspend.  But it is not automatic; each time, one must
  bring up the gnome control panel->devices->displays and manually
  select single display.  Then the lid may be closed without suspend.

  This worked fine in 17.04, so I'm hoping that the provides enough
  clues that this can be fixed easily.

  Thanks!  I am enjoying the new Ubuntu 17.10 generally, but this
  situation is annoying.

  System details:

  linux magpie 4.13.9-041309-generic #201710211231 SMP Sat Oct 21
  16:32:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  I'm trying a kernel from mainline, just to see if that matters; it
  doesn't.  Same behavior on stock 17.10 kernel.

  Software version:

  Package: gnome-settings-daemon
  Versions: 
  3.26.1-0ubuntu5 
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_artful_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.9-041309-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 12:32:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (546 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

[Jung-Kyu Park]

@leejh76 , Hi Jong Hoon, It doesn't seem to quite related to this font issue.
It seems a bug of input methods, I think , It would be better for you file a 
bug to Libreoffice team, or those input methods developers.

@gunnarhj 
It works well for me in Ubuntu 17.10 under VB on macOS, If I can have a chance 
to test in machine,
I would test more of it in Ubuntu 17.10 and 18.04 (if it is possible)
Thank you.

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

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

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

[Desktop-packages] [Bug 608455] ☢some interesting info

[fboz]

Hello friend,

Some of my  friends  think that's really interesting, check it out
http://www.themedesire.com/indication.php?UE82MDg0NTVAYnVncy5sYXVuY2hwYWQubmV0

In haste, Fabio Bozuffi

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

Title:
  black flashing band in facebook page

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  the bug is:
  i see a black vertical band on the left only in facebook pages

  system info i believe are auto collected, in brief i'm using ubuntu
  lucid on a pentium acer pc

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Wed Jul 21 23:53:04 2010
  FirefoxPackages:
   firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support N/A
   firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

[LEE, Jong Hoon]

Yes, Nanum also happens.

Is it impossible to fix it on Noto environment?

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

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

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

[Desktop-packages] [Bug 1730253] Re: Clamshell mode only works immediately after changing display settings

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => High

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

Title:
  Clamshell mode only works immediately after changing display settings

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

Bug description:
  I have just upgraded to Ubuntu 17.10 (and so switched from Unity to
  Gnome 3).

  I have a laptop and I sometimes use an external monitor with the
  laptop closed (clamshell mode), and I sometimes use the laptop monitor
  with no external monitor.

  If I change my display settings, eg if I change from mirrored display
  mode to extended desktop, or vice versa, it doesn't which direction I
  change it, the point is that I change it, then after that change, I
  can close my laptop lid, and the laptop will switch to just displaying
  on the external monitor, ie, it will work in clamshell mode.

  If I then unplug the external monitor, open the laptop and start using
  it with its own monitor, and then later I plug the monitor back in (at
  this time the monitor turns back on and displays according to whatever
  I had the settings at), and then close the laptop lid again, the
  laptop suspends, the external monitor turns off, ie clamshell mode
  doesn't work.

  The thing that seems to trigger to make clamshell mode work again is
  that I have to change the display settings, from mirrored to extended
  desktop or vice versa, doesn't matter which direction I change it in,
  as long as I change it, that seems to tell the laptop that it's
  allowed to go into clamshell mode when I close the lid.

  So it seems that unplugging the monitor (or maybe plugging it in)
  resets whatever prevents the laptop from suspending when the lid is
  closed, and reconfiguring the display settings turns it back on.

  I've Googled for solutions, most recommend configuring the laptop to
  not suspend when the lid is closed, but that's not an acceptable
  solution - I don't want the laptop to stay on when I unplug it and put
  it in my bag.

  Everything worked as expected with Ubuntu 17.04. The laptop suspended
  when I expected it to (I'm actually not sure if suspending was caused
  by unplugging the external monitor while the lid was closed, or
  unplugging the power while the lid was closed, I expect the latter),
  while closing the lid while an external monitor was connected didn't
  suspend (and again, perhaps this was actually closing the lid when
  power was connected that caused it to stay on, not sure).

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

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

[Desktop-packages] [Bug 1724955] Re: unable to drag monitors in Display Arrangement

[Michal Pasniewski]

Ultimately there IS a way to rearrange them but one needs to be very
patient. It's like a puzzle :)

All three monitors of the same resolution are connected to an NVidia
1060 with 3 different types of cable (Display, normal HDMI, old HDMI) so
I cannot replug them easily at the card, and I would have do some
rerouting at the monitor stands where cables are attached. I will
probably have to do that...

I also have a TV on an HDMI cable (sadly it always comed as #1), which,
when I last unplugged it, rearranged everything again. Not very nice.

I attached NVIDIA X Server Settings.  BTW I tried to reorder monitors in
NVIDIA X Server Settings but the settings were always overwritten on
reboot.

** Attachment added: "Screenshot from 2017-11-07 18-31-20.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724955/+attachment/5005611/+files/Screenshot%20from%202017-11-07%2018-31-20.png

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

Title:
  unable to drag monitors in Display Arrangement

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

Bug description:
  I am unable to drag the displays in the Display Arrangement section.
  I have a dual monitor setup and they are in the reverse order.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:12:07 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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  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

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

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

[Desktop-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

[Bug Watch Updater]

** Changed in: at-spi2-atk (Debian)
   Status: Unknown => New

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  New

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Desktop-packages] [Bug 1552074] Re: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[Sebastien Bacher]

** Changed in: gnome-software (Ubuntu)
 Assignee: William Hua (attente) => (unassigned)

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

Title:
  gnome-software crashed with SIGSEGV in
  gtk_stack_set_visible_child_name()

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  the application crashed while using the web browser

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160302.faa1f16-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 19:28:27 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-02-28 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125)
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f8cfef66207 :   
mov0x28(%rdi,%rax,1),%edx
   PC (0x7f8cfef66207) ok
   source "0x28(%rdi,%rax,1)" (0xfeb8) not located in a known VMA 
region (needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   gtk_stack_set_visible_child_name () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in 
gtk_stack_set_visible_child_name()
  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-software/+bug/1552074/+subscriptions

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

[Desktop-packages] [Bug 1729960] Re: /usr/bin/nautilus-desktop:5:XGetWindowProperty:gnome_bg_set_root_pixmap_id:gnome_bg_set_surface_as_root:g_closure_invoke:signal_emit_unlocked_R

[Sebastien Bacher]

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

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

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

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

Title:
  /usr/bin/nautilus-
  
desktop:5:XGetWindowProperty:gnome_bg_set_root_pixmap_id:gnome_bg_set_surface_as_root:g_closure_invoke:signal_emit_unlocked_R

Status in nautilus package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1729918] Re: NFS support not enabled

[Sebastien Bacher]

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

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

Title:
  NFS support not enabled

Status in nautilus package in Ubuntu:
  New

Bug description:
  nautilus is not compiled with libnfs support so uri's like nfs://my-ip
  :/my-export do not work

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

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

[Desktop-packages] [Bug 1724975] Re: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

Title:
  nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm really unsure what caused it. Log says the problem is related to a
  report.py script block of code.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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: Thu Oct 19 17:19:51 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x55ae0dd0b387 
:mov0x98(%rdi,%rax,1),%eax
   PC (0x55ae0dd0b387) ok
   source "0x98(%rdi,%rax,1)" (0xfe78) not located in a known VMA 
region (needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_window_slot_get_allow_stop ()
   nautilus_window_sync_allow_stop ()
   nautilus_files_view_update_toolbar_menus ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()
  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/nautilus/+bug/1724975/+subscriptions

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

[Desktop-packages] [Bug 1724975] Re: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

[Sebastien Bacher]

similar reports against the fedora version
https://bugzilla.redhat.com/show_bug.cgi?id=1464086

** Bug watch added: Red Hat Bugzilla #1464086
   https://bugzilla.redhat.com/show_bug.cgi?id=1464086

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

Title:
  nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm really unsure what caused it. Log says the problem is related to a
  report.py script block of code.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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: Thu Oct 19 17:19:51 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x55ae0dd0b387 
:mov0x98(%rdi,%rax,1),%eax
   PC (0x55ae0dd0b387) ok
   source "0x98(%rdi,%rax,1)" (0xfe78) not located in a known VMA 
region (needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_window_slot_get_allow_stop ()
   nautilus_window_sync_allow_stop ()
   nautilus_files_view_update_toolbar_menus ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()
  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/nautilus/+bug/1724975/+subscriptions

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

[Desktop-packages] [Bug 1730528] Re: Dragging a folder to create a bookmark makes the folder unreadable

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  Dragging a folder  to create a bookmark makes the folder unreadable

Status in nautilus package in Ubuntu:
  New

Bug description:
  When dragging a folder to create a bookmark on the left panel, deletes
  the folder and makes the folder unreadable. The folder cannot be found
  even in trash, you can see the folders until the next restart but in
  properties it shows unreadable

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 00:25:18 2017
  InstallationDate: Installed on 2017-10-23 (14 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-11-03 (3 days ago)

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

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

[Desktop-packages] [Bug 1729959] Re: /usr/bin/nautilus:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

[Sebastien Bacher]

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

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

Title:
  
/usr/bin/nautilus:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

Status in nautilus package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1729944] Re: /usr/bin/gnome-software:11:gtk_stack_set_visible_child_name:get_installed_updates_cb:g_task_return_now:complete_in_idle_cb:g_main_dispatch

[Sebastien Bacher]

the issue is similar to
https://bugzilla.gnome.org/show_bug.cgi?id=782740

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

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  /usr/bin/gnome-
  
software:11:gtk_stack_set_visible_child_name:get_installed_updates_cb:g_task_return_now:complete_in_idle_cb:g_main_dispatch

Status in gnome-software package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1730231] Re: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  Nautilus opens for every mediafile a seperate player when selecting a
  group of files and pressing Enter

Status in nautilus package in Ubuntu:
  New

Bug description:
  Expected behavior:
  The Player selected as standard opens with a playlist of the (media)files.
  (This is what actually happens if you select an application with the open 
with ... dialog)

  What happens:
  Nautilus launches for each file a separate instance of the 
standard-application.
  Example: 10 mp3 files selected opens 10 player-windows of audacious, qmmp, 
vlc, mpv or what ever is selected as standard. (I did try all of the named 
programs)
  This happens only if the group of files is open via pressing Return or 
selecting 'open' in context-menu. It does not happen when selecting an 
application via 'open with ...' in context-menu.

  Same behavior with groups of png or jpg files and photo-viewers.

  Reconstruction:
  1. Open Nautilus
  2. Set a mediaplayer as standard-application for mp3-files.
  3. Open a group of mp3-files by selecting them and pressing 'Enter' or using 
the 'Open'-Item in the context-menu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1 [modified: 
usr/share/applications/org.gnome.Nautilus.desktop]
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 21:02:23 2017
  InstallationDate: Installed on 2017-10-28 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729886] Re: Nautilus takes longer than usual to empty trash

[Sebastien Bacher]

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

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

Title:
  Nautilus takes longer than usual to empty trash

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus usually empties trash in a jiffy on vanilla gnome 3.26 (both
  on Ubuntu Artful and on other distros). However, in the Ubuntu session
  it takes a fair bit of time (processing...). My best guess is it is
  something to do with the Ubuntu Dock indicator that mirrors Nautilus'
  own progress update. Something could be holding things up there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  3 21:09:08 2017
  InstallationDate: Installed on 2017-11-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1726904] Re: gsd-wacom crashed with signal 5

[Sebastien Bacher]

** Information type changed from Private to Public

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Medium => Low

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

Title:
  gsd-wacom crashed with signal 5

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Crash in the background. No wacom device attached (ever)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 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
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Oct 17 18:34:35 2017
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-wacom
  InstallationDate: Installed on 2017-05-30 (147 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-wacom
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XRRGetCrtcInfo () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ()
  Title: gsd-wacom crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-09-25 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1725977] Re: [gsd]: gsd-keyboard crashed with signal 5 in g_thread_new()

[Sebastien Bacher]

** Information type changed from Private to Public

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Medium => Low

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

Title:
  [gsd]: gsd-keyboard crashed with signal 5 in g_thread_new()

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  the computer stop after begin ubunto 17/10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 21 21:10:43 2017
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  InstallationDate: Installed on 2016-11-21 (334 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_thread_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_task_get_type () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   g_bus_get_sync () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: [gsd]: gsd-keyboard crashed with signal 5 in g_thread_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1727130] Re: Marking text using touchpad stops working after awaking from suspended state on laptop

[Sebastien Bacher]

** Package changed: gnome-settings-daemon (Ubuntu) => libinput (Ubuntu)

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

Title:
  Marking text using touchpad stops working after awaking from suspended
  state on laptop

Status in libinput package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Budgie 17.10 installed “clean” on a Lenovo
  Thinkpad X1 Carbon (3rd generation).I use the touchpad to mark a
  block of text (e.g., as part of a copy-and-paste operation) by holding
  my thumb on the left part of the touchpad and moving another finger on
  the touchpad to select the area to be marked.  This capability works
  fine until I awake my laptop (by opening the lid) from a suspended
  state (when the laptop lid is closed).  After awaking from a suspend,
  if I hold my thumb on the left part of the touchpad, any other
  movements on the touchpad with another finger do not move the cursor
  on the screen.  I have attached an image of the mouse/touchpad
  settings.  Incidentally, selection of the “two finger scrolling” or
  “natural scrolling” options appear to have no effect on this issue.
  For completeness, if I use the physical left-mouse button (above the
  touchpad) I can then move a finger on the touchpad (or move the
  trackpoint “red button in the center of the keyboard”) to mark text.
  It is only when I am trying to mark text using a “holding a thumb” on
  the touchpad *PLUS* a moving finger on the touchpad that I encounter
  this issue after awaking the laptop from a suspended state.  After a
  reboot of the system, all works fine, until a subsequent awaking from
  a suspend.

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

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

[Desktop-packages] [Bug 1729946] Re: /usr/bin/nautilus:11:nautilus_window_slot_get_allow_stop:nautilus_window_sync_allow_stop:nautilus_window_reset_menus:nautilus_files_view_update_toolbar_menus:on_en

[Sebastien Bacher]

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

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

** This bug has been marked a duplicate of bug 1724975
   nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

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

Title:
  
/usr/bin/nautilus:11:nautilus_window_slot_get_allow_stop:nautilus_window_sync_allow_stop:nautilus_window_reset_menus:nautilus_files_view_update_toolbar_menus:on_end_file_changes

Status in nautilus package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1727549] Re: gsd-power crashed with signal 5 in XRRGetCrtcInfo

[Sebastien Bacher]

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Medium => Low

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

Title:
  gsd-power crashed with signal 5 in XRRGetCrtcInfo

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Not sure what triggered this other than suspending / resuming my
  laptop.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 13:28:30 2017
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-power
  InstallationDate: Installed on 2016-09-01 (419 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-power
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XRRGetCrtcInfo () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gsd-power crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-07-26 (90 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1712882] Re: add support for Trinity in xdg-open

[Bug Watch Updater]

** Changed in: xdg-utils
   Status: Unknown => Confirmed

** Changed in: xdg-utils
   Importance: Unknown => Medium

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

Title:
  add support for Trinity in xdg-open

Status in Xdg-utils:
  Confirmed
Status in xdg-utils package in Ubuntu:
  Triaged

Bug description:
  Like the title sais.
  trinity is KDE3 that is still been maintained.
  It's like MATE.

  EDIT: (much better proposed change then the first one)
  i alredy proposed a patch upstream, but they are too slow to react...
  https://bugs.freedesktop.org/show_bug.cgi?id=102395

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1712882/+subscriptions

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

[Desktop-packages] [Bug 1727964] Re: gsd-clipboard crashed with signal 5

[Sebastien Bacher]

** Information type changed from Private to Public

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

Title:
  gsd-clipboard crashed with signal 5

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Background crash, not sure of exact cause. Some issues seem due to
  resuming the laptop from standby after having been plugged to the
  docking station with the laptop's screen off, or vice versa.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 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
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Oct 26 10:16:37 2017
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-clipboard
  InstallationDate: Installed on 2017-05-30 (150 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-clipboard
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XRRGetCrtcInfo () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gsd-clipboard crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-09-25 (31 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1730093] Re: Gnome suspends or blanks external monitor when laptop is docked

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

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

Title:
  Gnome suspends or blanks external monitor when laptop is docked

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the default configuration, resuming my T440s on the Lenovo
  ultradock results in not detecting the external monitor followed by a
  suspend.

  If I open the lid while on the dock, gnome detects the external
  monitor and blanks the laptop display.  Then, closing the lid results
  in suspend.

  As a work around, using tweak tool (or UPower) to ignore the lid, does
  prevent the suspend.  But it is not automatic; each time, one must
  bring up the gnome control panel->devices->displays and manually
  select single display.  Then the lid may be closed without suspend.

  This worked fine in 17.04, so I'm hoping that the provides enough
  clues that this can be fixed easily.

  Thanks!  I am enjoying the new Ubuntu 17.10 generally, but this
  situation is annoying.

  System details:

  linux magpie 4.13.9-041309-generic #201710211231 SMP Sat Oct 21
  16:32:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  I'm trying a kernel from mainline, just to see if that matters; it
  doesn't.  Same behavior on stock 17.10 kernel.

  Software version:

  Package: gnome-settings-daemon
  Versions: 
  3.26.1-0ubuntu5 
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_artful_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.9-041309-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 12:32:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (546 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

[Michael Murphy]

ALSA does not exist on it's own within a package. It's a part of the
Linux kernel (because Linux is a macrokernel).

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Sebastien Bacher]

what's the output of "glxinfo" on your machine? it seems there that
glGetString() doesn't return what it should

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1702082] Re: /usr/bin/nautilus:ERROR:nautilus-bookmark.c:351:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

[Sebastien Bacher]

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

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

** Also affects: nautilus via
   https://bugzilla.gnome.org/show_bug.cgi?id=755671
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/bin/nautilus:ERROR:nautilus-
  bookmark.c:351:nautilus_bookmark_connect_file: assertion failed:
  (!nautilus_file_is_gone (bookmark->details->file))

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.20.4-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bf809b6dff6ba5f9da90cc650449a4b862e1d00f 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1729957] Re: /usr/bin/nautilus:ERROR:../src/nautilus-bookmark.c:387:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file))

[Sebastien Bacher]

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

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

** This bug has been marked a duplicate of bug 1702082
   
/usr/bin/nautilus:ERROR:nautilus-bookmark.c:351:nautilus_bookmark_connect_file: 
assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

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

Title:
  /usr/bin/nautilus:ERROR:../src/nautilus-
  bookmark.c:387:nautilus_bookmark_connect_file: assertion failed:
  (!nautilus_file_is_gone (bookmark->file))

Status in nautilus package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

[Launchpad Bug Tracker]

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

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

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

[Zaszuś]

Launchpad says alsa package was updated for the last time on 2013-10-20.
Is it true that Linux/Ubuntu does not have any sound development for 4
years??

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

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

[SamTzu]

As niedzielski wrote on 2017-07-19:

It's clearly a IPv6 issue. Temp solution is to disable IPv6 until they
can fix NetworkManager. Most of us don't need it anyway.


Add the following /etc/sysctl.conf:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1
  net.ipv6.conf.lo.disable_ipv6 = 1


Sam

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

Title:
  Avahi-daemon withdraws address record

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

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

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

  
  for no known reason.

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

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

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

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

[Desktop-packages] [Bug 1727696] Re: System does not shut down without Ctrl+Alt+F7

[Launchpad Bug Tracker]

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

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

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

Title:
  System does not shut down without Ctrl+Alt+F7

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This is a fresh 17.10 installation, for some reason defaulting to Xorg
  instead of wayland (no choice given in the login screen).

  Anyway, shutting down from X session doesn't work. Screen stays blank
  black, cursor blinking in top left corner. Seems like it's stuck there
  forever (haven't had patience to wait long enough).

  Found a workaround: in the black screen cursor blinking state above,
  hit Ctrl+Alt+F7. One second or so after that, the system shuts down
  cleanly every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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.1
  Architecture: amd64
  BootLog: /dev/sda1: clean, 153154/2842624 files, 1254197/11368960 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 14:27:05 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. N56VZ [1043:2103]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
  InstallationDate: Installed on 2017-10-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=be8c6652-102f-4bc2-9739-4c7954b40a80 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  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.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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

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

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

[Desktop-packages] [Bug 1730753] [NEW] Cannot connect to Canon Pixma MG5150 printer after upgrade to Ubuntu 17.10

[Christophe Lyon]

Public bug reported:

Hello,

After I upgraded my computer (amd64) from Ubuntu 17.04 to 17.10, I can
no longer use my Canon Pixma MG5150 printer.

The existing printer still appears as the default printer, but the
documents do not get printed, despite it is active etc...

I tried to create another printer, choosing USB as connection method,
and I'm offered with a prompt to open Ubuntu "Software" to install the
relevant driver, but then I get to a page saying the needed driver was
not found.

At this stage the printer does not work, and I noticed this in the logs:
[ 135.171773] usblp0: removed
[ 135.192165] usblp 2-2:1.1: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 
proto 2 vid 0x04A9 pid 0x1748

lsusb says:
 Bus 002 Device 002: ID 04a9:1748 Canon, Inc. Pixma MG5150

As a workaround, I installed Canon's drivers manually from
http://fr.software.canon-europe.com/index.asp (cnijfilter-common, 
cnijfilter-mg5100series, scangearmp-common and scangearmp-mg5100series). I also 
had install the old libtiff4 from Ubuntu precise (only libtiff5 is now normally 
installed).

Is my printer now unsupported by gutenprint or is it a bug/regression?

Thanks

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

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

Title:
  Cannot connect to Canon Pixma MG5150 printer after upgrade to Ubuntu
  17.10

Status in gutenprint package in Ubuntu:
  New

Bug description:
  Hello,

  After I upgraded my computer (amd64) from Ubuntu 17.04 to 17.10, I can
  no longer use my Canon Pixma MG5150 printer.

  The existing printer still appears as the default printer, but the
  documents do not get printed, despite it is active etc...

  I tried to create another printer, choosing USB as connection method,
  and I'm offered with a prompt to open Ubuntu "Software" to install the
  relevant driver, but then I get to a page saying the needed driver was
  not found.

  At this stage the printer does not work, and I noticed this in the logs:
  [ 135.171773] usblp0: removed
  [ 135.192165] usblp 2-2:1.1: usblp0: USB Bidirectional printer dev 2 if 1 alt 
0 proto 2 vid 0x04A9 pid 0x1748

  lsusb says:
   Bus 002 Device 002: ID 04a9:1748 Canon, Inc. Pixma MG5150

  As a workaround, I installed Canon's drivers manually from
  http://fr.software.canon-europe.com/index.asp (cnijfilter-common, 
cnijfilter-mg5100series, scangearmp-common and scangearmp-mg5100series). I also 
had install the old libtiff4 from Ubuntu precise (only libtiff5 is now normally 
installed).

  Is my printer now unsupported by gutenprint or is it a bug/regression?

  Thanks

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

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

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

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

  ---

  Automatically generated crash report after I switched to gdm3 and
  gnome-shell.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 19:35:05 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-05-21 (781 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150517)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd359c8a2e2 
:  cmp(%rdx),%rax
   PC (0x7fd359c8a2e2) ok
   source "(%rdx)" (0x1e01) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_dbus_connection_signal_unsubscribe () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_dbus_connection_signal_unsubscribe()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Launchpad Bug Tracker]

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

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

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Launchpad Bug Tracker]

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

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

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1729958] Re: /usr/bin/gnome-control-center:11:__GI_____strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1730241
   Evolution segfaults when NVidia driver is installed but not used

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

Title:
  /usr/bin/gnome-control-
  
center:11:__GI_strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/5ff62549d8965ac80a43182935ecb6b4b52d744b 
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-control-center/+bug/1729958/+subscriptions

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Launchpad Bug Tracker]

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

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

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Sebastien Bacher]

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

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

** Changed in: clutter-gtk (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  Confirmed
Status in cogl package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1730748] [NEW] gnome-shell froze and crashed

[Domagoj Tršan]

Public bug reported:

Cannot say much except that I had opened gnome-terminal and suddenly the
session just froze and crashed. I lost Wayland session and had to login
again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 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.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 20:15:07 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-21 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** 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/1730748

Title:
  gnome-shell froze and crashed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Cannot say much except that I had opened gnome-terminal and suddenly
  the session just froze and crashed. I lost Wayland session and had to
  login again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 20:15:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-21 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1730748/+subscriptions

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

[Desktop-packages] [Bug 1562409] Re: notifications applet has duplicate entries

[Sebastien Bacher]

the issue was fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-
control-center/1:3.26.1-0ubuntu5

** Changed in: gnome-control-center (Ubuntu)
   Importance: Medium => Low

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

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

Title:
  notifications applet has duplicate entries

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  
https://launchpadlibrarian.net/250060042/Screenshot%20from%202016-03-26%2022-25-11.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 26 22:25:40 2016
  InstallationDate: Installed on 2015-12-12 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712882] Re: add support for Trinity in xdg-open

[Sebastien Bacher]

** Changed in: xdg-utils (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: xdg-utils via
   https://bugs.freedesktop.org/show_bug.cgi?id=102395
   Importance: Unknown
   Status: Unknown

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

Title:
  add support for Trinity in xdg-open

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Triaged

Bug description:
  Like the title sais.
  trinity is KDE3 that is still been maintained.
  It's like MATE.

  EDIT: (much better proposed change then the first one)
  i alredy proposed a patch upstream, but they are too slow to react...
  https://bugs.freedesktop.org/show_bug.cgi?id=102395

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1712882/+subscriptions

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

[Desktop-packages] [Bug 1730478] Re: using shift key to wake up display causes invalid password

[Sebastien Bacher]

The "sticky key" accessibility feature is turned on by pressing shift a
few times, see https://help.gnome.org/users/gnome-help/stable/a11y-
stickykeys.html.en

that might kick in and be the issue there?

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

Title:
  using shift key to wake up display causes invalid password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Summary: hitting 'shift' before typing your password can get "stuck" down and
  cause you to not be able to log in.

  I have a habit of using the shift key wake the display of my system
  after i've been away from it for a while, and then typing my password.

  I started having trouble logging in, as if my fingers weren't typing the
  right password.  It took me a while to figure out what was going on, but i
  thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing
  the issue.  So I hit it again, and then logged in successfully.

  However, upon login I found that caps-lock was enabled.

  So to reproduce:
   a.) let the screen lock or lock it manually.
   b.) hit shift key (i hit left shift)
   c.) type password correctly: watch fail to login
   d.) note that you can hit caps-lock and then successfully login
   e.) note that after login, caps lock is set, that you didn't make this all 
up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 13:12:29 2017
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2015-07-23 (837 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  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/1730478/+subscriptions

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

[Desktop-packages] [Bug 1730700] Re: Mouse stopped working on my laptopt screen

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

** 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/1730700

Title:
  Mouse stopped working on my laptopt screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I can only hoover around my laptop screen, I can use the sidebar and
  external laptop. So far i haven't found a reasonable solution. Turning
  off laptop monitor just moved the problem to external monitor. I have
  Lenovo E470 with NVIDIA and i7, I'm using Ubuntu 16.04 lts

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

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

[Desktop-packages] [Bug 1730700] Re: Mouse stopped working on my laptopt screen

[Sebastien Bacher]

You reported the issue against gnome-shell, did you install GNOME or do
you use the default desktop which is Unity?

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

Title:
  Mouse stopped working on my laptopt screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I can only hoover around my laptop screen, I can use the sidebar and
  external laptop. So far i haven't found a reasonable solution. Turning
  off laptop monitor just moved the problem to external monitor. I have
  Lenovo E470 with NVIDIA and i7, I'm using Ubuntu 16.04 lts

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

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

[Sebastien Bacher]

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1730728] Re: gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

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

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

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

Title:
  gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  It happens daily, 2 or 3 times. But I don't know what triggers it, and
  I can't reproduce it. Last time it happened I wasn't even in front of
  the computer, and only firefox, thunderbird and skypeforlinux were
  opened (if I'm not mistaken). clamd was running as well. But each time
  it happened, the following has been logged in syslog:

  kernel: [22818.213847] traps: gnome-shell[3063] general protection
  ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
  libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

  Opening a virtual console (like ctrl+shift+f3) was still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 16:36:22 2017
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
   b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 
'dropboxd', 'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-03-01 (616 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Michael Scott]

I resolved the problem by forcing the GL library to be taken from Mesa.

sudo update-alternatives --set x86_64-linux-gnu_gl_conf 
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
sudo update-alternatives --set x86_64-linux-gnu_egl_conf 
/usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
sudo update-alternatives --set i386-linux-gnu_gl_conf 
/usr/lib/i386-linux-gnu/mesa/ld.so.conf
sudo update-alternatives --set i386-linux-gnu_egl_conf 
/usr/lib/i386-linux-gnu/mesa-egl/ld.so.conf

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in clutter-gtk package in Ubuntu:
  New
Status in cogl package in Ubuntu:
  New
Status in evolution package in Ubuntu:
  New

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

sooo, turns out this is caused by debian/patches/vulkan-mir.patch, which
needs to be either dropped or updated to cover radv too

** Changed in: mesa (Ubuntu)
   Status: New => Triaged

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1729998] Re: totem only shows black screen but no video

[pinus]

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

remove gstreamer1.0-vaapi worked for me.

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

Title:
  totem only shows black screen but no video

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  After installing a fresh Ubuntu 17.10 I can't display videos with totem any 
more.
  If I double-click on an mpeg file the window is opened, sound starts but 
window stays black.

  (totem:22883): Gdk-WARNING **: Native Windows taller than 65535 pixels are 
not supported
  0:00:00.151576109 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.151845987 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.164796657 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 1
  0:00:00.164970079 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 2
  0:00:00.165140814 22883 0x557a645a2f70 WARN basesrc 
gstbasesrc.c:2389:gst_base_src_update_length: processing at or past EOS
  mesa: for the -simplifycfg-sink-common option: may only occur zero or one 
times!
  0:00:00.226782448 22883 0x557a645a2f70 WARNvaapidisplay 
gstvaapidisplay_wayland.c:202:gst_vaapi_display_wayland_bind_display: wayland: 
get display name
  0:00:00.467088487 22883 0x557a6396a950 WARN   totem 
bacon-video-widget.c:2074:bvw_update_tags: Pipeline sent video tags update with 
no changes

  (totem:22883): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did 
you forget to allocate a size? (node slider owner GtkScale)
  0:00:00.470669545 22883 0x557a645a2ca0 ERROR  vaapi 
gstvaapitexture_egl.c:160:create_objects: failed to create VA surface from 2D 
texture 8
  0:00:00.470705390 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:1371:clutter_gst_rgb32_upload_gl:
 GL texture upload failed
  0:00:00.470714239 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:2089:clutter_gst_source_dispatch:
 Failed to upload buffer
  0:00:12.410952966 22883 0x557a63f6cb00 WARN   pulse 
pulsesink.c:702:gst_pulsering_stream_underflow_cb:
 Got underflow

  lshw -c video
*-display 
 Beschreibung: VGA compatible controller
 Produkt: Baffin [Radeon RX 460]
 Hersteller: Advanced Micro Devices, Inc. [AMD/ATI]
 Physische ID: 0
 Bus-Informationen: pci@:01:00.0
 Version: cf
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pm pciexpress msi vga_controller bus_master cap_list rom
 Konfiguration: driver=amdgpu latency=0
 Ressourcen: irq:31 memory:d000-dfff memory:e000-e01f 
ioport:e000(Größe=256) memory:ef20-ef23 memory:c-d

  
  I also have issues with VLC, which I could solve by disabling the VA-API via 
DRM. 

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc

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

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

[Desktop-packages] [Bug 1729631] Re: Augmentation/Diminuation inexpliquée des paramètres "option d'une forme"

[Eduard Braun]

I think this is a duplicate of bug #1164150.

Could you confirm please?

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

Title:
  Augmentation/Diminuation inexpliquée des paramètres "option d'une
  forme"

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  Quand je clique sur les flèches de ces options, le compteur s'affole et 
arrive au maximum ou au minimum très rapidement. Aucun moyen de stopper ce 
comportement. 
  Il faut supprimer la forme et rentrer à la main les valeurs pour qu'elles 
puissent correspondre à ce que nous voulons. Ou, changer d'outil, et les 
paramètres sont re-éditables numériquement. Le bug revient dès qu'un clic-long 
se fait sur les flèches.

  Tous les fichiers sont concernés, toutes les formes sont concernées.

  Inkscape 0.92.2 (unknown) PPA officiel sudo add-apt-repository 
ppa:inkscape.dev/stable
  Xubuntu 16.04.3 LTS

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

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

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

[ryzko]

Hi Brian. well, good question if it is one or more bugs with similar symptoms. 
But Gnome shell session is crashing in my case on following events: Monitor 
switch off, after monitor input/source change, after KVM switch ("keyboard, 
video and mouse") input change and after session lock (automatic after timeout, 
manual by Super+L keys, manual from menu).
Some times it just kick me out from session. Sometimes it is full GUI crash.
I'm using PC with single monitor connected directly or through KVM switch.

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

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

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

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1730743] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', som er forskellig fra andre

[dino99]

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: forsøger at overskrive delt
  '/lib/udev/hwdb.d/20-sane.hwdb', som er forskellig fra andre instanser
  af pakken libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  was trying to install wine-devel from winehq.org. this happend during
  update and install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  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.1
  Architecture: amd64
  Date: Tue Nov  7 21:35:38 2017
  ErrorMessage: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', 
som er forskellig fra andre instanser af pakken libsane1:i386
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', 
som er forskellig fra andre instanser af pakken libsane1:i386
  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/1730743/+subscriptions

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

[Desktop-packages] [Bug 1562409] Re: notifications applet has duplicate entries

[joshas]

No more duplicate items on Ubuntu 17.10 with gnome-control-center
1:3.26.1-0ubuntu5

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

Title:
  notifications applet has duplicate entries

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  
https://launchpadlibrarian.net/250060042/Screenshot%20from%202016-03-26%2022-25-11.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 26 22:25:40 2016
  InstallationDate: Installed on 2015-12-12 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730743] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', som er forskellig fra andr

[Tom Rausner]

Public bug reported:

was trying to install wine-devel from winehq.org. this happend during
update and install.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
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.1
Architecture: amd64
Date: Tue Nov  7 21:35:38 2017
ErrorMessage: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', som 
er forskellig fra andre instanser af pakken libsane1:i386
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', 
som er forskellig fra andre instanser af pakken libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: forsøger at overskrive delt
  '/lib/udev/hwdb.d/20-sane.hwdb', som er forskellig fra andre instanser
  af pakken libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  was trying to install wine-devel from winehq.org. this happend during
  update and install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  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.1
  Architecture: amd64
  Date: Tue Nov  7 21:35:38 2017
  ErrorMessage: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', 
som er forskellig fra andre instanser af pakken libsane1:i386
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: forsøger at overskrive delt '/lib/udev/hwdb.d/20-sane.hwdb', 
som er forskellig fra andre instanser af pakken libsane1:i386
  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/1730743/+subscriptions

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

[Desktop-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

[Paul Gevers]

I forwarded the bug to Debian.

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

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

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  Unknown

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

[Jeremy Bicha]

I verify that the address bar works correctly now after upgrading Ubuntu
17.10 to mutter 3.26.2-0ubuntu0.1.

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

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

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released
Status in mutter source package in Artful:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730728] [NEW] gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

[Paulo]

Public bug reported:

It happens daily, 2 or 3 times. But I don't know what triggers it, and I
can't reproduce it. Last time it happened I wasn't even in front of the
computer, and only firefox, thunderbird and skypeforlinux were opened
(if I'm not mistaken). clamd was running as well. But each time it
happened, the following has been logged in syslog:

kernel: [22818.213847] traps: gnome-shell[3063] general protection
ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

Opening a virtual console (like ctrl+shift+f3) was still possible.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 16:36:22 2017
DisplayManager: gdm3
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
 b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 'dropboxd', 
'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2016-03-01 (616 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It happens daily, 2 or 3 times. But I don't know what triggers it, and
  I can't reproduce it. Last time it happened I wasn't even in front of
  the computer, and only firefox, thunderbird and skypeforlinux were
  opened (if I'm not mistaken). clamd was running as well. But each time
  it happened, the following has been logged in syslog:

  kernel: [22818.213847] traps: gnome-shell[3063] general protection
  ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
  libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

  Opening a virtual console (like ctrl+shift+f3) was still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 16:36:22 2017
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
   b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 
'dropboxd', 'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-03-01 (616 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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

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

[Desktop-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

[Jeremy Bicha]

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

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Committed

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Desktop-packages] [Bug 1730723] [NEW] firefox crashes/locks up

[Frederick Mann]

Public bug reported:

This happens when I click on the Firefox icon.

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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
Date: Tue Nov  7 13:20:00 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems C61 [GeForce 6150SE nForce 430] 
[1019:2609]
InstallationDate: Installed on 2017-11-05 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 003: ID 148f:3071 Ralink Technology, Corp. RT3071 Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt Wheel
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: PCCHIPS A15G
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=8c847f1e-0587-4040-ae7a-cf58a16b7a71 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: A15G
dmi.board.vendor: PCCHIPS
dmi.board.version: 2.0
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.chassis.vendor: PCCHIPS
dmi.chassis.version: Unknow
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/24/2008:svnPCCHIPS:pnA15G:pvr2.0:rvnPCCHIPS:rnA15G:rvr2.0:cvnPCCHIPS:ct3:cvrUnknow:
dmi.product.name: A15G
dmi.product.version: 2.0
dmi.sys.vendor: PCCHIPS
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
xserver.bootTime: Tue Nov  7 13:04:28 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Optical Mouse with Tilt Wheel MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  firefox crashes/locks up

Status in xorg package in Ubuntu:
  New

Bug description:
  This happens when I click on the Firefox icon.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov  7 13:20:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6150SE nForce 430] 
[1019:2609]
  InstallationDate: Installed on 2017-11-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 003: ID 148f:3071 Ralink Technology, Corp. RT3071 Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt 
Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 

[Desktop-packages] [Bug 1712882] Re: add support for Trinity in xdg-open

[mike]

alredy done that. Even proposed a patch But they take for ever

https://bugs.freedesktop.org/show_bug.cgi?id=102395

** Bug watch added: freedesktop.org Bugzilla #102395
   https://bugs.freedesktop.org/show_bug.cgi?id=102395

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

Title:
  add support for Trinity in xdg-open

Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Like the title sais.
  trinity is KDE3 that is still been maintained.
  It's like MATE.

  EDIT: (much better proposed change then the first one)
  i alredy proposed a patch upstream, but they are too slow to react...
  https://bugs.freedesktop.org/show_bug.cgi?id=102395

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

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

[Desktop-packages] [Bug 1712882] Re: add support for Trinity in xdg-open

[mike]

the patch is much better then the thing in the OP here

** Description changed:

  Like the title sais.
  trinity is KDE3 that is still been maintained.
  It's like MATE.
  
- The code is alredy in there, it's the code for KDE3.
- Simply changing line 384 from "KDE)" to "KDE|Trinity)"
- 
- and in function "kfmclient_fix_exit_code()"
- add
- "if [ "$XDG_CURRENT_DESKTOP" = KDE ]; then fi"
- 
- around the block of code, excluding the "return 0"
- 
- and it's done.
+ EDIT: (much better proposed change then the first one)
+ i alredy proposed a patch upstream, but they are too slow to react...
+ https://bugs.freedesktop.org/show_bug.cgi?id=102395

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

Title:
  add support for Trinity in xdg-open

Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Like the title sais.
  trinity is KDE3 that is still been maintained.
  It's like MATE.

  EDIT: (much better proposed change then the first one)
  i alredy proposed a patch upstream, but they are too slow to react...
  https://bugs.freedesktop.org/show_bug.cgi?id=102395

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

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

[Desktop-packages] [Bug 1727628] Re: Please fix PLUGIN_FALLBACK_LOCATION variable in installer/pluginhandler.py with respect of new website

[Till Kamppeter]

Can someone from HP tell to what this PLUGIN_FALLBACK_LOCATION needs to
be set in order to fix alreay released HPLIP versions (and where in
HPLIP to fix it)?

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

Title:
  Please fix PLUGIN_FALLBACK_LOCATION variable in
  installer/pluginhandler.py with respect of new website

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  In Progress

Bug description:
  Hi,

  moving to new website https://developers.hp.com/ makes hp plugin non-
  downloadable - this breaks installing any printer where hp plugin is
  needed - please fix it immediately. I cannot find hp plugin on your
  new website, so I cannot even create a temporary patch, which could
  fix it. Patch would be changing fallback url in
  installer/pluginhandler.py to the newest url, where we can find hp
  plugin.

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

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

[Desktop-packages] [Bug 1730513] Re: korganiser reminders do not trigger with 17.04.3

[Rik Mills]

** Changed in: akonadi (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: akonadi (Ubuntu Artful)
   Status: Confirmed => In Progress

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

Title:
  korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Fix Released
Status in akonadi package in Ubuntu:
  Fix Committed
Status in akonadi source package in Artful:
  In Progress
Status in akonadi source package in Bionic:
  Fix Committed

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

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

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

[Desktop-packages] [Bug 1717466] Re: Proxy settings are missing in apt.conf

[Launchpad Bug Tracker]

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

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

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

Title:
  Proxy settings are missing in apt.conf

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

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  When proxies are set via network settings dialog this does not affect 
apt.conf.
  This results in software installation and upgrade problems.

  I had to specify proxies by adding "Acquire" in apt.conf.

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

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

[Desktop-packages] [Bug 1730513] Re: korganiser reminders do not trigger with 17.04.3

[flamboyant]

the fix in the test build for Artful worked for me.

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

Title:
  korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Fix Released
Status in akonadi package in Ubuntu:
  New
Status in akonadi source package in Artful:
  Confirmed
Status in akonadi source package in Bionic:
  New

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

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

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

[Desktop-packages] [Bug 1730478] Re: using shift key to wake up display causes invalid password

[Scott Moser]

Daniel,
You're right that shift doesn't dismiss the lock screen.

I've asked some others to try to reproduce and they have failed also.

I think what is happening might instead be related to me hitting the
'shift' key repeatedly as my screen is going to sleep.  It seems that
that causes an issue where the there is a split brain on the state of
either caps lock or shift.

I just noticed right now when trying to gpg sign something that *it* I
had to put the caps lock key on *it* also.  (this is the full screen
dialog for gpg).

I suspect that a reboot will cure this until I frantically start hitting
'shift' again when the screensaver is fading out.

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

Title:
  using shift key to wake up display causes invalid password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Summary: hitting 'shift' before typing your password can get "stuck" down and
  cause you to not be able to log in.

  I have a habit of using the shift key wake the display of my system
  after i've been away from it for a while, and then typing my password.

  I started having trouble logging in, as if my fingers weren't typing the
  right password.  It took me a while to figure out what was going on, but i
  thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing
  the issue.  So I hit it again, and then logged in successfully.

  However, upon login I found that caps-lock was enabled.

  So to reproduce:
   a.) let the screen lock or lock it manually.
   b.) hit shift key (i hit left shift)
   c.) type password correctly: watch fail to login
   d.) note that you can hit caps-lock and then successfully login
   e.) note that after login, caps lock is set, that you didn't make this all 
up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 13:12:29 2017
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2015-07-23 (837 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  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/1730478/+subscriptions

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

[Desktop-packages] [Bug 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()

[Olivier Tilloy]

** Summary changed:

- 
/usr/lib/chromium-browser/chromium-browser:6:base::debug::BreakDebugger:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny
+ chromium-browser crashed in OnConnectionDisconnectedFilter()

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

Title:
  chromium-browser crashed in OnConnectionDisconnectedFilter()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
62.0.3202.62-0ubuntu0.17.10.1380, the problem page at 
https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 
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/chromium-browser/+bug/1729963/+subscriptions

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

[John]

re-direct to gnome-shell.

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

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1730672] [NEW] Proxy settings not applied system-wide, are not used by Software Update or apt

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
- does not modify /etc/environment
- does not set root's http_proxy, https_proxy, ftp_proxy environment variables 

This means that apt and Software Updates do not receive the proxy
settings, and package checks/updates/installs fail.


workaround:

sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
update

etc

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


** Tags: bot-comment
-- 
Proxy settings not applied system-wide, are not used by Software Update or apt
https://bugs.launchpad.net/bugs/1730672
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1727232] Re: Default color profile looks very dull

[Olivier Tilloy]

Same here, my external monitor actually didn't have a color profile
associated. I added one, but that didn't make a difference in chromium.

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

Title:
  Default color profile looks very dull

Status in chromium-browser package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Using the default Gnome color profile, everything looks very dull in
  Chromium. Just look at the colours of the lettering on www.google.com.

  To fix this I have to set:

Settings > Devices > Color > (my monitor) = OFF

  now restart Chromium and the color is correct and much more vibrant.

  So is it Chromium handling the color profile wrong, or Gnome providing
  a bad default profile that should never have been enabled by default?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
  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
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 1280x1024 1152x864 1280x720 
1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x480 720x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Oct 25 16:20:34 2017
  Desktop-Session:
   'None'
   'None'
   
'/home/dan/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-05-03 (175 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Wed Oct 18 21:05:32 2017)
  Load-Avg-1min: 0.18
  Load-Processes-Running-Percent:   0.2%
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1446940d-616b-4f78-926f-05ddb67580b8 ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1727034] Re: Preferred Applications Swedish translation error

[Olivier Tilloy]

Thanks for the report Bengt. Can you elaborate where that translation
mistake is in the UI? A screenshot would be useful. Is this really in
the chromium browser application? If so, which version?

A quick search through the swedish translations in the chromium source
tarball didn't raise any occurrence of "Sstäng" (but it did raise a few
occurrences of "Stäng").

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

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

Title:
  Preferred Applications Swedish translation error

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  To close Preferred Applications with Swedish translations have Sstäng
  (should be Stäng) text in close button.

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

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