[Desktop-packages] [Bug 1695068] Re: evolution 3.22.6-1ubuntu1 should conflict with evolution-indicator 0.2.20-0ubuntu28

2017-08-01 Thread Launchpad Bug Tracker
[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  evolution 3.22.6-1ubuntu1 should conflict with evolution-indicator
  0.2.20-0ubuntu28

Status in evolution package in Ubuntu:
  Expired

Bug description:
  Hi,

  since the update to Ubuntu 17.04 evolution crashes most times having
  fetched new mail (segfault). Evolution also crashes trying to disable
  the plugin evolution-indicator. After uninstalling the package
  evolution-indicator everything's back to normal.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  evolution 3.22.6-1ubuntu1
  evolution-indicator 0.2.20-0ubuntu28

  3) What you expected to happen
  I expect the package evolution to force deinstall of evolution-indicator upon 
upgrade to 17.04.

  4) What happened instead
  Both were installed on my system.

  Best regards,
  Christoph

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

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


[Desktop-packages] [Bug 1703229] Re: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2017-08-01 Thread Olaf Jensen
sadd

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

Title:
  package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  mhgkhg

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libasound2-plugins:i386 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  9 15:33:02 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2017-05-25 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1707810] Re: regression on udev rules for HUAWEI mobile broadband?

2017-08-01 Thread Kai-Heng Feng
The post mentioned it was fixed here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=751271

** Bug watch added: Debian Bug tracker #751271
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751271

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

Title:
  regression on udev rules for HUAWEI mobile broadband?

Status in linux package in Ubuntu:
  Incomplete
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  I found several bug reports about mobile broadband USB sticks not
  working on Ubuntu 16.04. It seems that all the low level support is in
  place but the udev rules are incomplete, in what could be a regression
  from previous versions.

  --- 16.04 -

  
  ATTRS{idVendor}=="12d1", ATTRS{manufacturer}!="Android", 
ATTR{bInterfaceNumber}=="00", ATTR{bInterfaceClass}=="08", RUN+="usb_modeswitch 
'%b/%k'"
  ATTR{idVendor}=="12d1", ATTR{idProduct}=="1573", RUN+="usb_modeswitch '%b/%k'"

  
  --- 12.04 -

  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1003", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1009", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="101e", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1030", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1031", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1414", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1449", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14ad", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b7", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c4", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14d1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14fe", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1505", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1520", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1521", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1523", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1553", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1557", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1c0b", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1d50", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1da1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1f01", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="380b", RUN+="usb_modeswitch 
'%b/%k'"

  For example the HUAWEI device with vendor:product pair 12d1:1f01 (see
  #1527914 ) worked fine (plug and play) on Ubuntu 12.04 but appears as
  as mass storage device on Ubuntu 16.04.

  The missing rule is simply:

  ATTRS{idVendor}=="12d1", ATTR{idProduct}=="1f01", RUN+="usb_modeswitch
  '%b/%k'"

  References: #1431179 #1527914 #1514231

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

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


[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2017-08-01 Thread Alex Tu
@Sebastien
The final backported package in #17 has been landed to oem image. Do you have 
comment for also land it to Xenial?

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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


[Desktop-packages] [Bug 1707611] Re: Sound does not automatically play on new audio device

2017-08-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1702794 ***
https://bugs.launchpad.net/bugs/1702794

The fix only exists in Ubuntu 17.10 right now. Since it's a "feature"
more than a bugfix (according to PulseAudio developers) it might not get
backported to 16.04 at all.

If you are committed though, and have some basic Unix skills, then you
can apply the fix from bug 1702794 on your own system. Just edit a
config file.

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

Title:
  Sound does not automatically play on new audio device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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


[Desktop-packages] [Bug 1707966] Re: Inconsistent sample name used for x11-bell

2017-08-01 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Inconsistent sample name used for x11-bell

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  A startup script is being patched to load module-x11-bell with a given
  sample name:

  debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@
  load-module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" >
  /dev/null

  yet in the default example:
  src/daemon/default.pa.in:#load-sample-lazy x11-bell 
/usr/share/sounds/freedesktop/stereo/bell.oga

  As this is an example, no such sample gets loaded, but the patched
  script does not use either of the desired sample name or the matching
  file extension.

  I recommend updating the script to load the module using
  "sample=x11-bell" to be consistent with upstream and the fact that the
  sample name is not specific to a given format.

  This was discovered while trying to figure out how to set the bell
  sound on XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kjotte 1626 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug  1 12:43:03 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-12-09 (2061 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (427 days ago)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono

2017-08-01 Thread Daniel van Vugt
David, we have done a lot of work improving Bluetooth audio support recently. 
But most of the work only exists in Ubuntu 17.10 right now. Please also try 
booting up a live image of 17.10 (no need to install it) and see if that solves 
your problem:
  http://cdimage.ubuntu.com/daily-live/current/

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

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

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


[Desktop-packages] [Bug 1705691] Re: sane-backends 1.0.27 has several RC bugs

2017-08-01 Thread Bug Watch Updater
** Changed in: sane-backends (Debian)
   Status: New => Fix Released

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

Title:
  sane-backends 1.0.27 has several RC bugs

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  See these Debian bugs

  https://bugs.debian.org/868307 library package ships libtools .la files
  https://bugs.debian.org/868308 file conflict with libsane
  https://bugs.debian.org/868312 libsane1 package no longer ships a 
60-libsane.rules file

  This one has already been worked around in Ubuntu:
  https://bugs.debian.org/868309 src:sane-backends] FTBFS on various 
architectures due to missing symbols 9wo

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

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


[Desktop-packages] [Bug 1707796] Re: RM: obsolete product

2017-08-01 Thread Steve Langasek
Removing packages from artful:
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful amd64
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful arm64
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful armhf
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful i386
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful ppc64el
unity-scope-gdocs 0.9+16.04.20151125-0ubuntu1 in artful s390x
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful amd64
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful arm64
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful armhf
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful i386
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful ppc64el
unity-scope-gdrive 0.9+16.04.20151125-0ubuntu1 in artful s390x
Comment: part of Unity8 stack, no longer shipping; LP: #1707796
1 package successfully removed.


** Changed in: unity-scope-gdrive (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete product

Status in unity-scope-gdrive package in Ubuntu:
  Fix Released

Bug description:
  unity-scope-gdrive was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:unity-scope-gdrive
  No reverse dependencies found

  $ reverse-depends -b src:unity-scope-gdrive
  No reverse dependencies found

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

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


[Desktop-packages] [Bug 502642] Re: .ts files always get recognized as application/x-linguist and never as video/mp2t (mpeg transport stream)

2017-08-01 Thread simon place
for the record; ubuntu 16.04 LTS shows ".ts2" binary files as
"text/vnd.trolltech.linguist"

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

Title:
  .ts files always get recognized as application/x-linguist and never as
  video/mp2t (mpeg transport stream)

Status in shared-mime-info:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in Baltix:
  New

Bug description:
  Binary package hint: shared-mime-info

  I checked Hardy, Jaunty and Karmic: *.ts files are always mapped to
  application/x-linguist by
  /usr/share/mime/packages/freedesktop.org.xml. But there are several
  Linux-based settop boxes that record videos in *.ts-files. So if
  application/x-linguist is obsolete then it should simply be replaced
  by video/mpeg. Otherwise the mime framework has to distinguish such
  files by inspecting their headers. If someone knows more about
  x-linguist files, please add a comment!

  The problem has already been reported upstream two month ago (see
  freedesktop.org above). But for 10.04 LTS we should fix it by a patch,
  if it is not fixed upstream by then.

  As a workaround copy the attached file to 
~/.local/share/mime/packages/mpeg-ts.xml and update your mime-database with:
  $ update-mime-database ~/.local/share/mime

  To trigger the regeneration of failed thumbnails just delete them:
  $ rm ~/.thumbnails/fail/gnome-thumbnail-factory/*.png

  ProblemType: Bug
  Architecture: i386
  Date: Sun Jan  3 17:47:29 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: shared-mime-info 0.70-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: shared-mime-info
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/502642/+subscriptions

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


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

2017-08-01 Thread David
I'm affected by this same bug on my desktop and laptop - both running
Ubuntu 16.04.2 (64-bit).

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

Title:
  Automatically switch audio devices on connection

Status in pulseaudio package in Ubuntu:
  Fix Released

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

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

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

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

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

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


[Desktop-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-08-01 Thread FFab
Upstream kernel test - kernel 4.13-rc3

Installation, on which upstream kernel was installed:

ubuntu 16.04.2, kernel4.10.0-28, updated 2017-08-01

booting without any workaround parameters:
boot-time 45sec (message sound),
black screen
remote-login (ssh) o.k.

** Tags removed: kernel-bug-exists-upstream-4.12
** Tags added: kernel-bug-exists-upstream-4.13-rc3

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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


[Desktop-packages] [Bug 1708019] [NEW] Random screen lockup with hardware acceleration in 16.04

2017-08-01 Thread Ambrose Li
Public bug reported:

Since about a week ago, X started locking up randomly (about twice a
day). I don’t know what kind of details are relevant but here are some
observations:

- When it locks up the screen is always garbled.

- The keyboard would initially work, but if I don’t kill X or reboot
right away the keyboard would also stop working after a short time, at
which point the system would appear to be locked up hard.

- However, ssh would still work.

- Within the ssh session, any action on the framebuffer would hang. For
example, chvt would hang (but can still be suspended).

- Sometimes Xorg can be killed. If Xorg is killed the screen (and
keyboard) would appear to return to normal.

- The lockups started around the time hardware acceleration started
working on my hardware (NVidia GeForce 9400M) so the problem seems to be
related to hardware acceleration.

- The number of simultaneous hardware-accelerated apps using the
framebuffer seems to determine whether a lockup will occur. For example,
playing the same hardware-accelerated game (in Chrome) would eventually
cause an lockup, but playing the same game in only one Chrome window
seems to be safe.

- Before a lockup happens, messages similar to the following would
appear on the tty where the hardware-accelerated app (e.g., Chrome) is
started:

nouveau:0x20391200
nouveau:0x00087080
nouveau:0x
nouveau:0x203912cf
nouveau:0x000c6910
nouveau:0x2034
nouveau:0x
nouveau:0x20391224
nouveau:0x00087088
nouveau:0x
nouveau:0x203912cf
nouveau:0x000475dc
nouveau:0x0004
nouveau:0x000475ec
nouveau:0x0006
nouveau:0x000375f0
nouveau:0x0003
nouveau: ch4: psh 000c 000d00 000d0c
nouveau:0x0002
nouveau:0x0003
nouveau:0x00010003
nouveau: ch4: psh  06945c 069480
nouveau:0x000475ec
nouveau:0x
nouveau:0x000475e0
nouveau:0x
nouveau:0x00107b00
nouveau:0x
nouveau:0x20217000
nouveau:0x002f32a4
nouveau:0x1000f010


This might be the same bug as Bug #1675777, but the symptoms seem to be 
slightly different: 

- In Bug #1675777 the "nouveau" log messages appear in the system log, but in 
my case it appears on the terminal.
- Also, Bug #1675777 is filed against Ubuntu 17.04, but this is on an Ubuntu 
16.04.2 LTS.

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "apport.xserver-xorg-video-nouveau.tqo_6lsr.apport.gz"
   
https://bugs.launchpad.net/bugs/1708019/+attachment/4925493/+files/apport.xserver-xorg-video-nouveau.tqo_6lsr.apport.gz

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

Title:
  Random screen lockup with hardware acceleration in 16.04

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Since about a week ago, X started locking up randomly (about twice a
  day). I don’t know what kind of details are relevant but here are some
  observations:

  - When it locks up the screen is always garbled.

  - The keyboard would initially work, but if I don’t kill X or reboot
  right away the keyboard would also stop working after a short time, at
  which point the system would appear to be locked up hard.

  - However, ssh would still work.

  - Within the ssh session, any action on the framebuffer would hang.
  For example, chvt would hang (but can still be suspended).

  - Sometimes Xorg can be killed. If Xorg is killed the screen (and
  keyboard) would appear to return to normal.

  - The lockups started around the time hardware acceleration started
  working on my hardware (NVidia GeForce 9400M) so the problem seems to
  be related to hardware acceleration.

  - The number of simultaneous hardware-accelerated apps using the
  framebuffer seems to determine whether a lockup will occur. For
  example, playing the same hardware-accelerated game (in Chrome) would
  eventually cause an lockup, but playing the same game in only one
  Chrome window seems to be safe.

  - Before a lockup happens, messages similar to the following would
  appear on the tty where the hardware-accelerated app (e.g., Chrome) is
  started:

  nouveau:0x20391200
  nouveau:0x00087080
  nouveau:0x
  nouveau:0x203912cf
  nouveau:0x000c6910
  nouveau:0x2034
  nouveau:0x
  nouveau:0x20391224
  nouveau:0x00087088
  nouveau:0x
  nouveau:0x203912cf
  nouveau:0x000475dc
  nouveau:0x0004
  nouveau:0x000475ec
  nouveau:0x0006
  nouveau:0x000375f0
  nouveau:0x0003
  nouveau: ch4: psh 

[Desktop-packages] [Bug 1707897] Re: Não consigo atualizar o Ubuntu completamente. Falha na atualização...

2017-08-01 Thread Ubuntu Foundations Team Bug Bot
The attachment "/boot" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Não consigo atualizar o Ubuntu completamente. Falha na atualização...

Status in xorg package in Ubuntu:
  New

Bug description:
  Necessidade de restaurar o GRUB (Boot). Diversos erros na
  inicialização... Atualização em risco...ás vezes a conexão com o
  repositório apresenta instabilidade...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76
  Uname: Linux 4.4.0-88-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 Aug  1 08:56:21 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-07-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-88-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug  1 07:58:32 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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


[Desktop-packages] [Bug 1708011] [NEW] package libvdpau1 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/vdpau_wrapper.cfg », qui est différent d'autres instances du paq

2017-08-01 Thread Neophile76
Public bug reported:

while install mpv on ubuntu mate 16 lts

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvdpau1 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-27-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug  1 22:15:23 2017
ErrorMessage: tentative de remplacement de « /etc/vdpau_wrapper.cfg », qui est 
différent d'autres instances du paquet libvdpau1:amd64
InstallationDate: Installed on 2017-07-22 (10 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libvdpau
Title: package libvdpau1 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/vdpau_wrapper.cfg », qui est différent d'autres 
instances du paquet libvdpau1:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libvdpau (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 libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1708011

Title:
  package libvdpau1 (not installed) failed to install/upgrade: tentative
  de remplacement de « /etc/vdpau_wrapper.cfg », qui est différent
  d'autres instances du paquet libvdpau1:amd64

Status in libvdpau package in Ubuntu:
  New

Bug description:
  while install mpv on ubuntu mate 16 lts

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvdpau1 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 22:15:23 2017
  ErrorMessage: tentative de remplacement de « /etc/vdpau_wrapper.cfg », qui 
est différent d'autres instances du paquet libvdpau1:amd64
  InstallationDate: Installed on 2017-07-22 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libvdpau
  Title: package libvdpau1 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/vdpau_wrapper.cfg », qui est différent d'autres 
instances du paquet libvdpau1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1706916] Re: 'new document' option missing on right click

2017-08-01 Thread corrado venturini
same problem also installing from the daily dated 20170731.
let me know if i can send some other data (syslog, installer syslog ...)
I have installed from daily dated 20170731 and than nothing done to have a 
clean situation. 

this is the home folder as installed from ISO Ubuntu 17.10 "Artful
Aardvark" - Alpha amd64 (20170725)

corrado@corrado-HP-aa-0725:~$ ls -a
.  .bashrc  examples.desktop  .mozilla
.. .cache   .gnupg.profile
.bash_history  .config  .ICEauthority .ssh
.bash_logout   Desktop  .local.sudo_as_admin_successful
corrado@corrado-HP-aa-0725:~$ ls .config -a
.   dconfeoggeditgnome-session  gtk-3.0  nautilus
..  enchant  evolution  gnome-games  goa-1.0ibus pulse
corrado@corrado-HP-aa-0725:~$

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

Title:
  'new document' option missing on right click

Status in nautilus package in Ubuntu:
  New

Bug description:
  right click on window of a folder does not show 'new document' also if 
/home/templates is populated. .config/user-dirs.dirs does not exist.
  also other files/folders are missing in /home.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 27 11:44:10 2017
  InstallationDate: Installed on 2017-07-18 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  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/1706916/+subscriptions

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


[Desktop-packages] [Bug 1706916] Re: 'new document' option missing in partition window

2017-08-01 Thread corrado venturini
** Description changed:

- right click on window of a folder in a mounted partition does not show
- 'new document' also if /home/templates is populated. right click on
- window of a local folder works fine.
+ right click on window of a folder does not show 'new document' also if 
/home/templates is populated. .config/user-dirs.dirs does not exist.
+ also other files/folders are missing in /home.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 27 11:44:10 2017
  InstallationDate: Installed on 2017-07-18 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- 'new document' option missing in partition window
+ 'new document' option missing on right click

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

Title:
  'new document' option missing on right click

Status in nautilus package in Ubuntu:
  New

Bug description:
  right click on window of a folder does not show 'new document' also if 
/home/templates is populated. .config/user-dirs.dirs does not exist.
  also other files/folders are missing in /home.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 27 11:44:10 2017
  InstallationDate: Installed on 2017-07-18 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  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/1706916/+subscriptions

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


[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

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

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

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr: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/ubuntu/+source/udisks2/+bug/1707451/+subscriptions

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


[Desktop-packages] [Bug 1707897] Re: Não consigo atualizar o Ubuntu completamente. Falha na atualização...

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

** Information type changed from Private Security to Public

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

Title:
  Não consigo atualizar o Ubuntu completamente. Falha na atualização...

Status in xorg package in Ubuntu:
  New

Bug description:
  Necessidade de restaurar o GRUB (Boot). Diversos erros na
  inicialização... Atualização em risco...ás vezes a conexão com o
  repositório apresenta instabilidade...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76
  Uname: Linux 4.4.0-88-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 Aug  1 08:56:21 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-07-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-88-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug  1 07:58:32 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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


[Desktop-packages] [Bug 1707986] [NEW] Web Content spent more cycles on NULL pointer

2017-08-01 Thread asu
Public bug reported:

For this test run kernel 4.6.2 modiffied.
1.Run from terminal sudo perf record -ag when firefox running on youtube
2. Stop perf process and read the result, result is belllow:

Samples: 26K of event 'cycles:p', Event count (approx.): 9427386496 
 
  Children  Self  Command  Shared Object   Symbol   
 
+9.06% 0.00%  Web Content  [unknown]   [.] 

+5.29% 0.00%  Web Content  [unknown]   [.] 
0x00841f0f
+3.86% 0.00%  Web Content  libxul.so   [.] 
0x80a98562dc70
+3.03% 0.00%  Web Content  libxul.so   [.] 
0x80a9855affd0

On most time access on NULL pointer  or unknown symbol.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox (not installed)
Uname: Linux 4.6.2+ x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Aug  1 21:07:17 2017
InstallationDate: Installed on 2016-04-29 (459 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Web Content spent more cycles on NULL pointer

Status in firefox package in Ubuntu:
  New

Bug description:
  For this test run kernel 4.6.2 modiffied.
  1.Run from terminal sudo perf record -ag when firefox running on youtube
  2. Stop perf process and read the result, result is belllow:

  Samples: 26K of event 'cycles:p', Event count (approx.): 9427386496   
   
Children  Self  Command  Shared Object   Symbol 
   
  +9.06% 0.00%  Web Content  [unknown]   [.] 

  +5.29% 0.00%  Web Content  [unknown]   [.] 
0x00841f0f
  +3.86% 0.00%  Web Content  libxul.so   [.] 
0x80a98562dc70
  +3.03% 0.00%  Web Content  libxul.so   [.] 
0x80a9855affd0

  On most time access on NULL pointer  or unknown symbol.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox (not installed)
  Uname: Linux 4.6.2+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug  1 21:07:17 2017
  InstallationDate: Installed on 2016-04-29 (459 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono

2017-08-01 Thread David
I have already tried that. When I go into the sound GUI options (by
clicking on the speaker icon in the top-right, then "Sound
Settings..."), the option for "Hi fidelity" is there, but often times it
does not let me choose it. Sometimes it will let me choose it then
instantly jump back to "mono".

A few times I've been lucky and been able to select "hi fidelity" and it
works, but this setting never gets remembered.

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

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

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


[Desktop-packages] [Bug 1707810] Re: regression on udev rules for HUAWEI mobile broadband?

2017-08-01 Thread ghomem
Strange as this sounds I went to try the solution above on a different
computer with the same Ubuntu version (16.04) and didn't work - device
appeared as mass storage. The line that worked was this one:

ATTR{idVendor}=="12d1", ATTR{idProduct}=="1f01",
RUN+="/usr/sbin/usb_modeswitch -v 12d1 -p 1f01 -J"

which bypasses the udev modeswitch wrapper and has the parameters
hardcoded. [1]

There is a related bug on the Debian bug tracker:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754348

[1]
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2562

** Bug watch added: Debian Bug tracker #754348
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754348

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

Title:
  regression on udev rules for HUAWEI mobile broadband?

Status in linux package in Ubuntu:
  Incomplete
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  I found several bug reports about mobile broadband USB sticks not
  working on Ubuntu 16.04. It seems that all the low level support is in
  place but the udev rules are incomplete, in what could be a regression
  from previous versions.

  --- 16.04 -

  
  ATTRS{idVendor}=="12d1", ATTRS{manufacturer}!="Android", 
ATTR{bInterfaceNumber}=="00", ATTR{bInterfaceClass}=="08", RUN+="usb_modeswitch 
'%b/%k'"
  ATTR{idVendor}=="12d1", ATTR{idProduct}=="1573", RUN+="usb_modeswitch '%b/%k'"

  
  --- 12.04 -

  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1003", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1009", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="101e", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1030", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1031", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1414", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1449", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14ad", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b7", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c4", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14d1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14fe", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1505", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1520", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1521", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1523", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1553", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1557", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1c0b", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1d50", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1da1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1f01", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="380b", RUN+="usb_modeswitch 
'%b/%k'"

  For example the HUAWEI device with vendor:product pair 12d1:1f01 (see
  #1527914 ) worked fine (plug and play) on Ubuntu 12.04 but appears as
  as mass storage device on Ubuntu 16.04.

  The missing rule is simply:

  ATTRS{idVendor}=="12d1", ATTR{idProduct}=="1f01", RUN+="usb_modeswitch
  '%b/%k'"

  References: #1431179 #1527914 #1514231

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

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


[Desktop-packages] [Bug 1707611] Re: Sound does not automatically play on new audio device

2017-08-01 Thread David
*** This bug is a duplicate of bug 1702794 ***
https://bugs.launchpad.net/bugs/1702794

I have all the updates installed, but still the same problem. Is the fix
downloaded separately?

"And to avoid this extra step in future you might want to log future
bugs using the command:

  ubuntu-bug pulseaudio"

Sorry, I'm not familiar with writing bug reports.

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

Title:
  Sound does not automatically play on new audio device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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


[Desktop-packages] [Bug 1707611] Re: Sound does not automatically play on new audio device

2017-08-01 Thread David
*** This bug is a duplicate of bug 1702794 ***
https://bugs.launchpad.net/bugs/1702794

Tried running apport-collect 1707611, then got this message:

You are not the reporter or subscriber of this problem report, or the
report is a duplicate or already closed.

Please create a new report using "apport-bug".

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

Title:
  Sound does not automatically play on new audio device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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


[Desktop-packages] [Bug 1707966] [NEW] Inconsistent sample name used for x11-bell

2017-08-01 Thread Kevin Otte
Public bug reported:

A startup script is being patched to load module-x11-bell with a given
sample name:

debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@ load-
module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" > /dev/null

yet in the default example:
src/daemon/default.pa.in:#load-sample-lazy x11-bell 
/usr/share/sounds/freedesktop/stereo/bell.oga

As this is an example, no such sample gets loaded, but the patched
script does not use either of the desired sample name or the matching
file extension.

I recommend updating the script to load the module using
"sample=x11-bell" to be consistent with upstream and the fact that the
sample name is not specific to a given format.

This was discovered while trying to figure out how to set the bell sound
on XFCE.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kjotte 1626 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Aug  1 12:43:03 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-12-09 (2061 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-05-31 (427 days ago)
dmi.bios.date: 10/12/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET73WW (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4286CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4286CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  Inconsistent sample name used for x11-bell

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A startup script is being patched to load module-x11-bell with a given
  sample name:

  debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@
  load-module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" >
  /dev/null

  yet in the default example:
  src/daemon/default.pa.in:#load-sample-lazy x11-bell 
/usr/share/sounds/freedesktop/stereo/bell.oga

  As this is an example, no such sample gets loaded, but the patched
  script does not use either of the desired sample name or the matching
  file extension.

  I recommend updating the script to load the module using
  "sample=x11-bell" to be consistent with upstream and the fact that the
  sample name is not specific to a given format.

  This was discovered while trying to figure out how to set the bell
  sound on XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kjotte 1626 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug  1 12:43:03 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-12-09 (2061 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (427 days ago)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device

2017-08-01 Thread Jeff Lambert
Comment #40 (the two killall commands) did it for me on 14.04.5 64-bits
desktop with a Samsung Note 3. THANKS!

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

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
 Found 1 device(s):
 Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

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

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


[Desktop-packages] [Bug 1707945] Re: keyring location is not documented and differs between installations

2017-08-01 Thread H.-Dirk Schmitt
The undocumented location is implemented in the file pkcs11/gkm/gkm-
util.c


gkm_util_locate_keyrings_directory (void)
{
[…]
old_directory = g_build_filename (g_get_home_dir (), ".gnome2", 
"keyrings", NULL);
new_directory = g_build_filename (g_get_user_data_dir (), "keyrings", 
NULL);

/*
 * If the new XDG directory doesn't exist, and the old one does,
 * use the old one, otherwise create/use the new XDG location.
 */

[…]}

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

Title:
  keyring location is not documented and differs between installations

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  I found keyrings on different locations.
  Sometime below ~/.gnome2/keyrings, sometimes below ~/.local/share/keyrings/, 
sometimes in both locations.

  The README.Debian is only mentioning:  .gnome2/keyrings
  The man page for gnome-keyring-daemon doesn't document any location.

  The problem for me is that I want to consolidates of the login.keyring
  between several installations.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 17:32:26 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.gnome-keyring-ssh.log: grep: 
/home/hs/.config/autostart/gnome-keyring-ssh.desktop: Datei oder Verzeichnis 
nicht gefunden

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

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


[Desktop-packages] [Bug 1690006] Re: Firefox fails acid3.acidtests.org

2017-08-01 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Invalid

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

Title:
  Firefox fails acid3.acidtests.org

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

Bug description:
  Compliance test at http://acid3.acidtests.org/ is failing since a few 
releases, now.
  The reported failure says:

  Test 35 failed: expected '0' but got '1' - root element, with no
  parent node, claims to be a :first-child

  Previous versions used to pass 100 tests out of 100.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 53.0+build6-0ubuntu0.16.04.1
  Uname: Linux 4.11.0-041100-lowlatency x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  enzo   2238 F pulseaudio
  BuildID: 20170418123315
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu May 11 08:54:48 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.255.254 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.255.0/24 dev enp2s0  proto kernel  scope link  src 192.168.255.42  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=53.0/20170418123315 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.01
  dmi.board.asset.tag: CZC3523T17
  dmi.board.name: 18EB
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3523T17
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 490 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1707952] [NEW] Routes from DHCP not respected

2017-08-01 Thread Michał Sawicz
Public bug reported:

After upgrading to artful a while ago, my system no longer respects
routes given out by my DHCP:

 tail -f /var/log/syslog | grep -i dhcp
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0380] 
dhcp4 (enx0123456789ab): activation: beginning transaction (timeout in 45 
seconds)
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0446] 
dhcp4 (enx0123456789ab): dhclient started with pid 23633
Aug  1 17:07:43 user-laptop dhclient[23633]: DHCPREQUEST of 10.2.0.5 on 
enx0123456789ab to 255.255.255.255 port 67 (xid=0x13152178)
Aug  1 17:07:43 user-laptop dhclient[23633]: DHCPACK of 10.2.0.5 from 10.2.0.1
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   address 10.2.0.5
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   plen 24 (255.255.255.0)
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   classless static route 10.0.0.0/13 gw 10.2.0.1
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   gateway 10.2.0.253
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   lease time 86400
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   hostname 'user-laptop'
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   nameserver '10.2.0.1'
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   domain name 'user.domain'
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp (enx0123456789ab):   domain search 'user.domain.'
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp (enx0123456789ab):   domain search 'domain.'
Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab): state changed unknown -> bound
^C
 ip route
default via 10.2.0.253 dev enx0123456789ab proto static metric 100 
10.2.0.0/24 dev enx0123456789ab proto kernel scope link src 10.2.0.5 metric 102

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug  1 17:08:24 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-06 (451 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to artful on 2017-07-19 (13 days ago)
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
disabled  enabled  enabled

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


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

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

Title:
  Routes from DHCP not respected

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to artful a while ago, my system no longer respects
  routes given out by my DHCP:

   tail -f /var/log/syslog | grep -i dhcp
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0380] 
dhcp4 (enx0123456789ab): activation: beginning transaction (timeout in 45 
seconds)
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0446] 
dhcp4 (enx0123456789ab): dhclient started with pid 23633
  Aug  1 17:07:43 user-laptop dhclient[23633]: DHCPREQUEST of 10.2.0.5 on 
enx0123456789ab to 255.255.255.255 port 67 (xid=0x13152178)
  Aug  1 17:07:43 user-laptop dhclient[23633]: DHCPACK of 10.2.0.5 from 10.2.0.1
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   address 10.2.0.5
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   plen 24 (255.255.255.0)
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0805] 
dhcp4 (enx0123456789ab):   classless static route 10.0.0.0/13 gw 10.2.0.1
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 
dhcp4 (enx0123456789ab):   gateway 10.2.0.253
  Aug  1 17:07:43 user-laptop NetworkManager[2627]:   [1501600063.0806] 

[Desktop-packages] [Bug 1707929] Re: Revert blacklisting of Indic layouts

2017-08-01 Thread Bug Watch Updater
** Changed in: xkeyboard-config (Debian)
   Status: Unknown => Fix Released

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

Title:
  Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Triaged
Status in xkeyboard-config package in Debian:
  Fix Released

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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


[Desktop-packages] [Bug 1707944] [NEW] Desktop Sharing cannot be accessed from Windows 10

2017-08-01 Thread Jeb E.
Public bug reported:

When trying to connect to my Ubuntu PC on the same subnet, any VNC
client I try fails at Authentication, either by not being able to read
the next byte or not being compatible with RFB 3.3.

I thought this was a resolved issue from way back in 2011, but apparently not.
Please fix!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vino 3.8.1-0ubuntu9.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug  1 11:34:21 2017
InstallationDate: Installed on 2017-08-01 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: vino
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug julyshakedown remote vino xenial

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

Title:
  Desktop Sharing cannot be accessed from Windows 10

Status in vino package in Ubuntu:
  New

Bug description:
  When trying to connect to my Ubuntu PC on the same subnet, any VNC
  client I try fails at Authentication, either by not being able to read
  the next byte or not being compatible with RFB 3.3.

  I thought this was a resolved issue from way back in 2011, but apparently not.
  Please fix!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vino 3.8.1-0ubuntu9.2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 11:34:21 2017
  InstallationDate: Installed on 2017-08-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vino
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1707945] [NEW] keyring location is not documented and differs between installations

2017-08-01 Thread H.-Dirk Schmitt
Public bug reported:

I found keyrings on different locations.
Sometime below ~/.gnome2/keyrings, sometimes below ~/.local/share/keyrings/, 
sometimes in both locations.

The README.Debian is only mentioning:  .gnome2/keyrings
The man page for gnome-keyring-daemon doesn't document any location.

The problem for me is that I want to consolidates of the login.keyring
between several installations.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-keyring 3.18.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug  1 17:32:26 2017
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.gnome-keyring-ssh.log: grep: 
/home/hs/.config/autostart/gnome-keyring-ssh.desktop: Datei oder Verzeichnis 
nicht gefunden

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


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

** Summary changed:

- keyring location is not documented and differs beetween installations
+ keyring location is not documented and differs between installations

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

Title:
  keyring location is not documented and differs between installations

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  I found keyrings on different locations.
  Sometime below ~/.gnome2/keyrings, sometimes below ~/.local/share/keyrings/, 
sometimes in both locations.

  The README.Debian is only mentioning:  .gnome2/keyrings
  The man page for gnome-keyring-daemon doesn't document any location.

  The problem for me is that I want to consolidates of the login.keyring
  between several installations.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 17:32:26 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.gnome-keyring-ssh.log: grep: 
/home/hs/.config/autostart/gnome-keyring-ssh.desktop: Datei oder Verzeichnis 
nicht gefunden

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

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


[Desktop-packages] [Bug 1706916] Re: 'new document' option missing in partition window

2017-08-01 Thread Carlo Lobrano
Could you update problem description so that it reflects the right
issue?

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

Title:
  'new document' option missing in partition window

Status in nautilus package in Ubuntu:
  New

Bug description:
  right click on window of a folder in a mounted partition does not show
  'new document' also if /home/templates is populated. right click on
  window of a local folder works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 27 11:44:10 2017
  InstallationDate: Installed on 2017-07-18 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  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/1706916/+subscriptions

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


[Desktop-packages] [Bug 1549653] Re: Disks utility doesn't remove previous record in /etc/fstab

2017-08-01 Thread Vlad Orlov
** Tags added: xenial

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

Title:
  Disks utility doesn't remove previous record in /etc/fstab

Status in GNOME Disks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  How to reproduce:
  1. delete an NTFS partition on secondary disk (rewrite with zeroes).
  2. put there EXT4 partition instead.
  3. reboot computer
  => ubuntu doesn't boot, allows only single-user mode.

  By checking system log, I found out system was trying to mount the old
  NTFS partition and hanged on it, even though that is not at all a
  necessary partition. Then I checked /etc/fstab and found out the GUI
  tool did NOT remove the original record, when it deleted the partition
  on the drive.

  By commenting it out I was able to get into the GUI again.

  Ubuntu 15.10
  pkg: gnome-disk-utility 3.16.2-0ubuntu2 0

  The original line, that was left behind:
  UUID=52D09468D09453D7 /backup ntfsdefaults,umask=007,gid=46 0 
  0

  The new line that the tool created:
  /dev/disk/by-uuid/414e95a1-fb40-45a6-9b90-487a45337fdd /extdata auto 
nosuid,nodev,nofail,x-gvfs-show 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-disk-utility 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 25 08:34:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1549653/+subscriptions

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


[Desktop-packages] [Bug 1687694] Re: Disk partition not removed from fstab after deleting partition

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1549653 ***
https://bugs.launchpad.net/bugs/1549653

** Project changed: linuxmint => gnome-disk-utility (Ubuntu)

** This bug has been marked a duplicate of bug 1549653
   Disks utility doesn't remove previous record in /etc/fstab

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

Title:
  Disk partition not removed from fstab after deleting partition

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  One of the disks in my machine had two partitions on it. A test
  install of MINT on ext4 and a swap partition (machine was original
  dual botted).

  The ext4 partition was mounted via /etc/fstab on startup. I deleted
  both partitions and re-partitioned the disk with a single ext4
  partition using the GUI tool:

  gnome-disk-utility 3.18.3.1
  UDisks 2.1.7 (built against 2.1.6)

  When I rebooted the machine it failed to boot complaining of TOCBLOCK
  database corrupt. All I could get was a command line.

  Took me a few hours to work out the problem was that the partition was
  mentioned in /etc/fstab.

  I'd have expected that the disk utility would have tidied that up when
  the original partition was deleted.

  This does kind of relate to #1458474. Although the cause is different
  (and in my case I'd argue the utility should handle it) the mitigation
  is probably the same, allow the machine to Skip the mount of not found
  or problem disks.

  Running Mint 18.1, cinnamon 64 bit.

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

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


[Desktop-packages] [Bug 1707929] Re: Revert blacklisting of Indic layouts

2017-08-01 Thread Bug Watch Updater
** Changed in: xkeyboard-config
   Status: Unknown => Fix Released

** Changed in: xkeyboard-config
   Importance: Unknown => Critical

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

Title:
  Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Triaged
Status in xkeyboard-config package in Debian:
  Unknown

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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


[Desktop-packages] [Bug 1707932] [NEW] chromium browser flickering at different frequencies

2017-08-01 Thread marvin
Public bug reported:

similar to before in ubuntu 16 now in ubuntu 17.04 (LENOVO 20frs2m600
/X1 carbon olded) unity 8. Major flickering of screen

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity8
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-DP-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAwrkBBADEZAQSlHxJ46kSBr1A+tSMOUFQBAQEBAQEBAQEBAQEBAQEBm14AoKCgLFAwIDYANq8QAAAam14AoKCgLFAwIDYANq8QAAAaDwD/CTz/CTwegABMgwAA/gBBVE5BNDBKVTAxLTAgAKk=
 modes: 2560x1440
Date: Tue Aug  1 16:32:29 2017
Desktop-Session:
 'unity8'
 '/etc/xdg/xdg-unity8:/etc/xdg'
 '/usr/share/unity8:/usr/local/share:/usr/share'
Env:
 'None'
 'None'
InstallationDate: Installed on 2016-09-13 (322 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
Load-Avg-1min: 0.30
Load-Processes-Running-Percent:   0.2%
MachineType: LENOVO 20FRS2M600
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=499d3889-fb60-45bc-bfd2-6fd10cd7f6e0 ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to zesty on 2017-05-03 (90 days ago)
dmi.bios.date: 06/23/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET41W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FRS2M600
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: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FRS2M600
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-bug zesty

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

Title:
  chromium browser flickering at different frequencies

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  similar to before in ubuntu 16 now in ubuntu 17.04 (LENOVO 20frs2m600
  /X1 carbon olded) unity 8. Major flickering of screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: chromium-browser 59.0.3071.109-0ubuntu0.17.04.1360
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAwrkBBADEZAQSlHxJ46kSBr1A+tSMOUFQBAQEBAQEBAQEBAQEBAQEBm14AoKCgLFAwIDYANq8QAAAam14AoKCgLFAwIDYANq8QAAAaDwD/CTz/CTwegABMgwAA/gBBVE5BNDBKVTAxLTAgAKk=
   modes: 2560x1440
  Date: Tue Aug  1 16:32:29 2017
  Desktop-Session:
   'unity8'
   '/etc/xdg/xdg-unity8:/etc/xdg'
   '/usr/share/unity8:/usr/local/share:/usr/share'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-09-13 (322 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Load-Avg-1min: 0.30
  Load-Processes-Running-Percent:   0.2%
  MachineType: LENOVO 20FRS2M600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=499d3889-fb60-45bc-bfd2-6fd10cd7f6e0 ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to zesty on 2017-05-03 (90 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  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: None
  dmi.modalias: 

[Desktop-packages] [Bug 1687694] [NEW] Disk partition not removed from fstab after deleting partition

2017-08-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

One of the disks in my machine had two partitions on it. A test install
of MINT on ext4 and a swap partition (machine was original dual botted).

The ext4 partition was mounted via /etc/fstab on startup. I deleted both
partitions and re-partitioned the disk with a single ext4 partition
using the GUI tool:

gnome-disk-utility 3.18.3.1
UDisks 2.1.7 (built against 2.1.6)

When I rebooted the machine it failed to boot complaining of TOCBLOCK
database corrupt. All I could get was a command line.

Took me a few hours to work out the problem was that the partition was
mentioned in /etc/fstab.

I'd have expected that the disk utility would have tidied that up when
the original partition was deleted.

This does kind of relate to #1458474. Although the cause is different
(and in my case I'd argue the utility should handle it) the mitigation
is probably the same, allow the machine to Skip the mount of not found
or problem disks.

Running Mint 18.1, cinnamon 64 bit.

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

-- 
Disk partition not removed from fstab after deleting partition
https://bugs.launchpad.net/bugs/1687694
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-disk-utility 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 1707929] [NEW] Revert blacklisting of Indic layouts

2017-08-01 Thread Gunnar Hjalmarsson
Public bug reported:

In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved to
"extras".

https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

The measure has been criticized and has been reverted afterwards at both
freedesktop.org and Debian. We should make sure it's reverted in Ubuntu
17.10 as well.

** Affects: xkeyboard-config
 Importance: Unknown
 Status: Unknown

** Affects: xkeyboard-config (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: xkeyboard-config (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: freedesktop.org Bugzilla #101532
   https://bugs.freedesktop.org/show_bug.cgi?id=101532

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=101532
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #865316
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865316

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

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

Title:
  Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Triaged
Status in xkeyboard-config package in Debian:
  Unknown

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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


[Desktop-packages] [Bug 1707922] Re: Broken fridge url in default install

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

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

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

Title:
  Broken fridge url in default install

Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  The out of the box install of xscreensaver on Xenial currently shows
  error messages (see screenshot/photo).

  The .xscreensaver on xenial ships with:-

  90_ubuntu-branding.patch:+*textURL:
  http://fridge.ubuntu.com/node/feed

  Which is a broken link. Later releases of Ubuntu fix this url to:-
  http://feeds.feedburner.com/ubuntu-news

  Can we please get the same URL fixed in Xenial?

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

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


[Desktop-packages] [Bug 1707922] Re: Broken fridge url in default install

2017-08-01 Thread Alan Pope  濾
** Attachment added: "IMG_20170801_150141.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1707922/+attachment/4925252/+files/IMG_20170801_150141.jpg

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

Title:
  Broken fridge url in default install

Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  The out of the box install of xscreensaver on Xenial currently shows
  error messages (see screenshot/photo).

  The .xscreensaver on xenial ships with:-

  90_ubuntu-branding.patch:+*textURL:
  http://fridge.ubuntu.com/node/feed

  Which is a broken link. Later releases of Ubuntu fix this url to:-
  http://feeds.feedburner.com/ubuntu-news

  Can we please get the same URL fixed in Xenial?

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

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


[Desktop-packages] [Bug 1641912] Re: Please backport two recent-manager patches

2017-08-01 Thread Łukasz Zemczak
Hello! Thank you for preparing and uploading the fix for our stable releases. 
For us to be able to properly review your SRU we would need some more 
information included in this bug. Please update the bug description to include 
the SRU template as found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

We need to know what impact this bug has (how much the fixes better the
current situation?), a reliable test case and a quick analysis of
possible regression scenarios after the fix has been applied (looking at
the changes and thinking: what could possibly go wrong in the worst
scenario?).

Thank you!

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

Title:
  Please backport two recent-manager patches

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  In Progress
Status in gtk+2.0 source package in Yakkety:
  Won't Fix
Status in gtk+2.0 source package in Zesty:
  In Progress
Status in gtk+2.0 source package in Artful:
  Fix Released

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca

  Please apply/backport these two patches from the 2.24 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

  For the GTK3 version of this bug, see bug 1641914
  Note that MATE is GTK2 only for Ubuntu 16.04 LTS.

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

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


[Desktop-packages] [Bug 1707922] [NEW] Broken fridge url in default install

2017-08-01 Thread Alan Pope  濾
Public bug reported:

The out of the box install of xscreensaver on Xenial currently shows
error messages (see screenshot/photo).

The .xscreensaver on xenial ships with:-

90_ubuntu-branding.patch:+*textURL:
http://fridge.ubuntu.com/node/feed

Which is a broken link. Later releases of Ubuntu fix this url to:-
http://feeds.feedburner.com/ubuntu-news

Can we please get the same URL fixed in Xenial?

** Affects: xscreensaver (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Broken fridge url in default install

Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  The out of the box install of xscreensaver on Xenial currently shows
  error messages (see screenshot/photo).

  The .xscreensaver on xenial ships with:-

  90_ubuntu-branding.patch:+*textURL:
  http://fridge.ubuntu.com/node/feed

  Which is a broken link. Later releases of Ubuntu fix this url to:-
  http://feeds.feedburner.com/ubuntu-news

  Can we please get the same URL fixed in Xenial?

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

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


[Desktop-packages] [Bug 1568135] Re: gnome-disks failed when trying to restore a boot drive to a storage drive

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks failed when trying to restore a boot drive to a storage
  drive

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  This is an automatically prompted bug, but it is related to bug
  #1549603, usb-creator-gtk.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CasperVersion: 1.372
  CurrentDesktop: LXDE
  Date: Fri Apr  8 20:28:38 2016
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160408)
  ProcCmdline: gnome-disks
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-disk-utility
  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-disk-utility/+bug/1568135/+subscriptions

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


[Desktop-packages] [Bug 1544968] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  tring to format a disk with btrfs,crashed instead

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  Uname: Linux 4.1.17-040117-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 12 21:06:10 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-02-07 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160205)
  ProcCmdline: gnome-disks
  SegvAnalysis:
   Segfault happened at: 0x7f50d1c20b6f :   
mov(%rbx),%rdi
   PC (0x7f50d1c20b6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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-disk-utility/+bug/1544968/+subscriptions

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


[Desktop-packages] [Bug 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

2017-08-01 Thread Vlad Orlov
** Tags added: xenial

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

Title:
  /usr/bin/gnome-
  
disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

Status in GNOME Disks:
  Confirmed
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gnome-disk-utility.  This problem was most recently seen
  with version 3.16.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ec0e4eaf2490589696da7e6514c5fc0507946b0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1479710/+subscriptions

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


[Desktop-packages] [Bug 1558509] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  ubuntu 16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Mar 16 22:31:30 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-03-01 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160301)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f9212b4cbaf :   
mov(%rbx),%rdi
   PC (0x7f9212b4cbaf) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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-disk-utility/+bug/1558509/+subscriptions

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


[Desktop-packages] [Bug 1566908] Re: gnome-disks crashes when trying to create 3000 GB LUKS Ext4 partition

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashes when trying to create 3000 GB LUKS Ext4 partition

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I created a GPT volume on the disk, and tried to create a 3000 GB LUKS
  Ext4 partition, leaving 1 GB at the end of the disk empty (at least
  that is what the tool showed).

  After entering the details and clicking "Create", gnome-disks crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  6 16:58:08 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2015-02-05 (425 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205)
  ProcCmdline: gnome-disks
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0f721cbc9f :   
mov(%rbx),%rdi
   PC (0x7f0f721cbc9f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  UpgradeStatus: Upgraded to xenial on 2016-02-12 (54 days ago)
  UserGroups: adm autopilot cdrom dialout dip kvm libvirtd lpadmin plugdev 
sambashare sudo

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

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


[Desktop-packages] [Bug 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

2017-08-01 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1479710

** Tags added: iso-testing

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

Title:
  /usr/bin/gnome-
  
disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

Status in GNOME Disks:
  Confirmed
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gnome-disk-utility.  This problem was most recently seen
  with version 3.16.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ec0e4eaf2490589696da7e6514c5fc0507946b0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1479710/+subscriptions

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


[Desktop-packages] [Bug 1569733] Re: gnome-disks cannot restore a cloned boot pendrive to a storage pendrive

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks cannot restore a cloned boot pendrive to a storage
  pendrive

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  When isotesting I encountered this bug. Formatting did nothing but
  create a new partition table.

  Trying to make partition and FAT32 file system:

  - A partition was made.

  - No file system was made. Instead, gnome-disks crashed, and I was
  prompted to report this bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CasperVersion: 1.372
  CurrentDesktop: LXDE
  Date: Wed Apr 13 07:35:02 2016
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160412)
  ProcCmdline: gnome-disks
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-disk-utility
  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-disk-utility/+bug/1569733/+subscriptions

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


[Desktop-packages] [Bug 1574858] Re: gnome-disks crashed

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1575336 ***
https://bugs.launchpad.net/bugs/1575336

** This bug has been marked a duplicate of bug 1575336
   gnome-disks crashed

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

Title:
  gnome-disks crashed

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  application seems to have segfaulted?

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 25 14:14:36 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-06-19 (675 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: gnome-disks
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (31 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  crashed when making a usb fat32 and did not finish making a fat32 file
  system.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: hostname 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 01:10:08 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-02-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
  ProcCmdline: /usr/bin/gnome-disks --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: 0x7fa8b4a38b6f :   
mov(%rbx),%rdi
   PC (0x7fa8b4a38b6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/ubuntu/+source/gnome-disk-utility/+bug/1547340/+subscriptions

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


[Desktop-packages] [Bug 1545529] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Happened when trying to format a new partition on a 2TB disk, the
  partition is using full space and is using ext4 + LUKS for encrypting
  the partition.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Feb 14 17:47:51 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-01-15 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160107)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fce2ae4eb6f :   
mov(%rbx),%rdi
   PC (0x7fce2ae4eb6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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-disk-utility/+bug/1545529/+subscriptions

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


[Desktop-packages] [Bug 1552334] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Hello,

  gnome-disks just crashed.

  Thank you for your help.

  LGDN

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  2 17:45:02 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2013-12-13 (809 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131213)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f55802b2baf :   
mov(%rbx),%rdi
   PC (0x7f55802b2baf) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  UpgradeStatus: Upgraded to xenial on 2015-12-15 (78 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 1622174] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Crash after creating an extended MBR partition (the part that would hold 
logical partitions).
  gnome-disks can be restarted after the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Sep 10 13:42:14 2016
  ExecutablePath: /usr/bin/gnome-disks
  ProcCmdline: gnome-disks
  SegvAnalysis:
   Segfault happened at: 0x7fdc08286caf :   
mov(%rbx),%rdi
   PC (0x7fdc08286caf) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface (object=0x0, interface_name=0x7fdc0a17f9d3 
"org.freedesktop.UDisks2.Drive") at 
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gio/gdbusobject.c:149
   udisks_object_peek_drive () at /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ()
   g_task_return_now (task=0x19af0e0 [GTask]) at 
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gio/gtask.c:1107
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse kvm 
libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

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

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


[Desktop-packages] [Bug 1609418] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Aug  3 11:51:34 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-05-14 (80 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fdffabd5caf :   
mov(%rbx),%rdi
   PC (0x7fdffabd5caf) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  XsessionErrors:
   mate-session[3118]: WARNING: Unable to find provider '' of required 
component 'dock'
   (nm-applet:3465): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: 
assertion 'window->update_and_descendants_freeze_count > 0' failed
   (redshift-gtk:3453): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: 
assertion 'window->update_and_descendants_freeze_count > 0' failed
   (mate-panel:3273): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
   (mate-power-manager:3431): GLib-CRITICAL **: Source ID 197 was not found 
when attempting to remove it

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

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


[Desktop-packages] [Bug 1629639] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1479710 ***
https://bugs.launchpad.net/bugs/1479710

** This bug is no longer a duplicate of bug 1547340
   gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
** This bug has been marked a duplicate of bug 1479710
   
/usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Crashed while creating new partition table on dev/sda from live usb.
  Partition table not created.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-disk-utility 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: GNOME
  Date: Sun Oct  2 08:45:53 2016
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20161001)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f821dd8e7af :   
mov(%rbx),%rdi
   PC (0x7f821dd8e7af) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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-disk-utility/+bug/1629639/+subscriptions

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


[Desktop-packages] [Bug 1697232] Re: Disks tool crashes or times out when adding encrypted partition

2017-08-01 Thread Vlad Orlov
*** This bug is a duplicate of bug 1581294 ***
https://bugs.launchpad.net/bugs/1581294

** Project changed: linuxmint => gnome-disk-utility (Ubuntu)

** This bug has been marked a duplicate of bug 1581294
   ext4 + luks on 1TB crashes

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

Title:
  Disks tool crashes or times out when adding encrypted partition

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  When I try to add an encrypted partition to a 64GB SD or MicroSD card,
  the disks tool either times out or crashes. I have tested on both Mate
  and Cinnamon.

  This works correctly on LinuxMint 17.x, it is only a problem on 18.x.
  I have also tested this on both Mate and Cinnamon.

  To reproduce:

  Launch Disks
  Insert new 64GB SD card
  Delete exFat partition
  Add new encrypted partition:
  * Use full SD card (Free Space Following = 0)
  * Type = Encrypted, compatible with Linxux systems (LUKS + Ext4)

  Disks either times out or crashes. Crash happens every time with Micro
  SD.

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

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


[Desktop-packages] [Bug 1697232] [NEW] Disks tool crashes or times out when adding encrypted partition

2017-08-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I try to add an encrypted partition to a 64GB SD or MicroSD card,
the disks tool either times out or crashes. I have tested on both Mate
and Cinnamon.

This works correctly on LinuxMint 17.x, it is only a problem on 18.x. I
have also tested this on both Mate and Cinnamon.

To reproduce:

Launch Disks
Insert new 64GB SD card
Delete exFat partition
Add new encrypted partition:
* Use full SD card (Free Space Following = 0)
* Type = Encrypted, compatible with Linxux systems (LUKS + Ext4)

Disks either times out or crashes. Crash happens every time with Micro
SD.

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

-- 
Disks tool crashes or times out when adding encrypted partition
https://bugs.launchpad.net/bugs/1697232
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-disk-utility 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 1675369] Re: Metacity Not Sending ConfigureNotify events

2017-08-01 Thread Alberts Muktupāvels
** Changed in: metacity (Ubuntu Yakkety)
   Status: New => Invalid

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

Title:
  Metacity Not Sending ConfigureNotify events

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in metacity source package in Yakkety:
  Invalid

Bug description:
  # Impact
  When using seamless applications such as Rdesktop, the window manager needs 
to send ConfigureNotify events.  This is specified in ICCCM section 4.1.5.  
Without it, software will hang and wait for a response.

  This greatly impacts corporate and enterprise users that are trying to
  integrate Microsoft Windows applications using Rdesktop.

  # Proposed Fix
  A patch has been created here and should be merged:

  
https://git.gnome.org/browse/metacity/commit/?h=gnome-3-24=f09967fc0f1d65fc7b5057b362b9657154a86079

  Patch for 3.18 branch which was used for Xenial upload is here:

  
https://git.gnome.org/browse/metacity/commit/?h=gnome-3-18=64e95c2ec2a1669da2ddab6c29108d718f79dfff

  # Test Case
  Use rdesktop in seamless mode:
  rdesktop "%ProgramFiles%\ThinLinc\WTSTools\seamlessrdpshell.exe" -s "notepad" 
server_ip

  This requires server with windows that is setup for remote access. Also extra 
software is needed:
  https://www.cendio.com/thinlinc/download-register

  Opening multiple seamless windows and trying to switch between them
  should not cause any noticeable delays / hangs.

  # Regression Potential
  The reporter has verified the fix, and it works. It has also been in Zesty 
since Mar 20th and so far nobody complained.

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

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


[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

2017-08-01 Thread Forage
I have this same problem with an WiFi USB dongle:
Bus 005 Device 003: ID 13b1:0020 Linksys WUSB54GC v1 802.11g Adapter [Ralink 
RT73]

The provided work-around in comment #1 does the trick for me.

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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


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

2017-08-01 Thread Alberto Milone
yes, sorry but I have been busy with other work. I plan to take care of
this soon.

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

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

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

Bug description:
  SRU Request:

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

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

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

  2) Install the nvidia driver.

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

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

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

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

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

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

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

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

  Needed by LP: #1653592

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

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


[Desktop-packages] [Bug 1707891] [NEW] Disabling a wifi network adapter disables all wifi adapters

2017-08-01 Thread Jamie Bennett
Public bug reported:

Using the wifi toggle switch in Gnome Shell->Settings->Network on a wifi
adaptor, when more than one is present, turns off all wifi adaptors. The
toggle switch is visible per adaptor and gives the impression that you
can selectively turn off an adaptor which doesn't seem to be the case.

jamie@ubik:~$ uname -a
Linux ubik 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:03:41 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

jamie@ubik:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename:   artful

jamie@ubik:~$ nmcli --version 
nmcli tool, version 1.8.2

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

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

Title:
  Disabling a wifi network adapter disables all wifi adapters

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using the wifi toggle switch in Gnome Shell->Settings->Network on a
  wifi adaptor, when more than one is present, turns off all wifi
  adaptors. The toggle switch is visible per adaptor and gives the
  impression that you can selectively turn off an adaptor which doesn't
  seem to be the case.

  jamie@ubik:~$ uname -a
  Linux ubik 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:03:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  jamie@ubik:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  jamie@ubik:~$ nmcli --version 
  nmcli tool, version 1.8.2

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

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


[Desktop-packages] [Bug 1707691] Re: libxfont1-dev is missing fontutil.h

2017-08-01 Thread brian mullan
ok... I notified NeutrinoLabs about your recommendation and I assume
they will remedy the xorgxrdp build process to accommodate this

close the bug report

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

Title:
  libxfont1-dev is missing fontutil.h

Status in libxfont package in Ubuntu:
  Won't Fix

Bug description:
  /usr/include/xorg/dixfont.h includes X11/fonts/fontutil.h.

  fontutil.h is contained in libxfont1-dev package not libxfont-dev
  package (version 2.0.1).

  I am trying to build xorgxrdp and it fails because fontutil.h is
  missing.

  In Ubuntu, libxfont1-dev package is required however libxfont1-dev and
  libxfont-dev cannot be installed together. This is the problem.

  I looked at Debian, too. /usr/include/xorg/dixfont.h in Debian does
  NOT include X11/fonts/fontutil.h.

  This is the right state.

  Package info: Ubuntu 16.04

  $  dpkg -la | grep -e xserver-xorg-dev -e libxfont-dev
  ii  libxfont-dev   1:2.0.1-3~ubuntu16.04.1
amd64X11 font rasterisation library (development headers)
  ii  xserver-xorg-dev   2:1.18.4-0ubuntu0.3
amd64Xorg X server - development files

  brian

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

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


[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

2017-08-01 Thread redtux
** Also affects: kscreenlocker (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in kscreenlocker package in Ubuntu:
  New
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  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/ecryptfs/+bug/1085706/+subscriptions

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


[Desktop-packages] [Bug 1703110] Re: notes doesn't delete only if empty

2017-08-01 Thread Alberts Muktupāvels
Roland, you should not compile it yourself! You should install update
from proposed and test it, but... Please wait until new upload / version
will be accepted. New upload will also fix text selection. :)

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

Title:
  notes doesn't delete only if empty

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  Unnesessary work for the user as he is forced to clear the note from
  text in order to delete it. It makes it more difficult that selecting
  text isn't possible with mouse.

  [Test Case]

  - Write anything in a note
  - Try to select text in a note
  - Try to delete it with 'x' or with 'delete notes' menu item

  [Proposed Fix]

  The fix is a backport of three upstream commits:
  - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a 
“sticky-notes: make sure that notes are really saved”
  - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf 
“sticky-notes: fix path to resource file for delete dialog”
  - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8
  “sticky-notes: fix text selection”

  [Regression Potential]

  The fix definitely improves the Sticky Notes applet because without
  ability to save notes that applet is mostly unusable. It does not
  touch other applets so no regression expected there.

  [Other Info]

  System configuration:

   roland@roland-Lenovo-ideapad-110-15I
  `:+ss+:`   

    -+ssyy+- OS: Ubuntu 17.04 x86_64
  .ossdMMMNyo.   Model: 80T7 Lenovo ideapad 
110-15IBR
     /ssshdmmNNmmyNhss/  Kernel: 4.10.0-26-generic
    +shmydMMMNy+ Uptime: 4 hours, 45 mins
   /hNMMMyhhhmNMMMNh/Packages: 2360
  .dMMMNhsshNMMMd.   Shell: bash 4.4.7
  +hhhyNMMNyyNMMMysss+   Resolution: 1366x768
  ossyNMMMNyMMhsshmmmhssso   DE: GNOME-Flashback:GNOME
  ossyNMMMNyMMhsshmmmhssso   WM: Compiz
  +hhhyNMMNyyNMMMysss+   WM Theme: Adwaita
  .dMMMNhsshNMMMd.   Theme: Adwaita [GTK2/3]
   /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3]
    +sdmydy+ Terminal: gnome-terminal
     /ssshdmmyNhss/  CPU: Intel Pentium N3710 (4) @ 
2.5GH
  .ossdMMMNyo.   GPU: Intel HD Graphics 405
    -+syyy+- Memory: 1674MiB / 3862MiB
  `:+ss+:`
  .-/+oooo+/-.

  Stickynotes version: 3.22.0

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

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


[Desktop-packages] [Bug 1707865] Re: package libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 failed to install/upgrade: symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has changed from

2017-08-01 Thread CVSH
I suppose this not really a mesa bug as it occurs with many packages which I 
try to install, 
so I'm changing it to dpkg, since that seems to be where symlinks are checked 
for size

** Package changed: mesa (Ubuntu) => dpkg (Ubuntu)

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

Title:
  package libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 failed to
  install/upgrade: symbolic link '/usr/share/doc/libgl1-mesa-
  dri/changelog.Debian.gz' size has changed from 80 to 36

Status in dpkg package in Ubuntu:
  New

Bug description:
  Installing packages fails because symlinks have a different size than 
expected.
  What works is manually removing the links, but I suppose that dpkg should not 
worry about symlinks if they are working.
  As this error is summing up, I don't want to manually delete all links, 
  therefore I just start deleting all of them
  e.g.:
rm /usr/share/doc/*/changelog.*gz
rm /usr/share/doc/*/NEWS.*gz

  in a script.

  Here is a reinstallation call
  $ sudo apt-get install -f
  [sudo] password for User: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
  [...]
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libgl1-mesa-dri:i386
  The following packages will be upgraded:
libgl1-mesa-dri:i386
  1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/5.085 kB of archives.
  After this operation, 7.536 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 1693621 files and directories currently installed.)
  Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
  Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb 
(--unpack):
   symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has 
changed from 80 to 36
  Errors were encountered while processing:
   /var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb
  $

  
  and after removing the links:

  $ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
  [...]
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libgl1-mesa-dri:i386
  The following packages will be upgraded:
libgl1-mesa-dri:i386
  1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/5.085 kB of archives.
  After this operation, 7.536 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 1693621 files and directories currently installed.)
  Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
  Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
  Setting up libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) ...
  Installing new version of config file /etc/drirc ...
  Setting up libgl1-mesa-dri:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Setting up libegl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Setting up libwayland-egl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Processing triggers for libc-bin (2.23-0ubuntu9) ...
  $

  Regards

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-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: None
  Date: Tue Aug  1 10:52:58 2017
  DistUpgraded: 2016-08-24 16:49:18,141 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-87-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:17.0.7-0ubuntu0.16.04.1
   Unpacking imagemagick (8:6.8.9.9-7ubuntu5.9) over (8:6.8.9.9-7ubuntu5.8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/imagemagick_8%3a6.8.9.9-7ubuntu5.9_amd64.deb (--unpack):
symbolic link '/usr/share/doc/imagemagick/changelog.Debian.gz' size has 
changed from 88 to 40
  ErrorMessage: 

[Desktop-packages] [Bug 1707865] Re: package libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 failed to install/upgrade: symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has changed from

2017-08-01 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 failed to
  install/upgrade: symbolic link '/usr/share/doc/libgl1-mesa-
  dri/changelog.Debian.gz' size has changed from 80 to 36

Status in mesa package in Ubuntu:
  New

Bug description:
  Installing packages fails because symlinks have a different size than 
expected.
  What works is manually removing the links, but I suppose that dpkg should not 
worry about symlinks if they are working.
  As this error is summing up, I don't want to manually delete all links, 
  therefore I just start deleting all of them
  e.g.:
rm /usr/share/doc/*/changelog.*gz
rm /usr/share/doc/*/NEWS.*gz

  in a script.

  Here is a reinstallation call
  $ sudo apt-get install -f
  [sudo] password for User: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
  [...]
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libgl1-mesa-dri:i386
  The following packages will be upgraded:
libgl1-mesa-dri:i386
  1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/5.085 kB of archives.
  After this operation, 7.536 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 1693621 files and directories currently installed.)
  Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
  Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb 
(--unpack):
   symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has 
changed from 80 to 36
  Errors were encountered while processing:
   /var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb
  $

  
  and after removing the links:

  $ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
  [...]
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libgl1-mesa-dri:i386
  The following packages will be upgraded:
libgl1-mesa-dri:i386
  1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/5.085 kB of archives.
  After this operation, 7.536 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 1693621 files and directories currently installed.)
  Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
  Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
  Setting up libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) ...
  Installing new version of config file /etc/drirc ...
  Setting up libgl1-mesa-dri:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Setting up libegl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Setting up libwayland-egl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
  Processing triggers for libc-bin (2.23-0ubuntu9) ...
  $

  Regards

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-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: None
  Date: Tue Aug  1 10:52:58 2017
  DistUpgraded: 2016-08-24 16:49:18,141 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-87-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:17.0.7-0ubuntu0.16.04.1
   Unpacking imagemagick (8:6.8.9.9-7ubuntu5.9) over (8:6.8.9.9-7ubuntu5.8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/imagemagick_8%3a6.8.9.9-7ubuntu5.9_amd64.deb (--unpack):
symbolic link '/usr/share/doc/imagemagick/changelog.Debian.gz' size has 
changed from 88 to 40
  ErrorMessage: symbolic link 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has changed from 80 
to 36
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd 

[Desktop-packages] [Bug 1707865] [NEW] package libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 failed to install/upgrade: symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has changed fr

2017-08-01 Thread CVSH
Public bug reported:

Installing packages fails because symlinks have a different size than expected.
What works is manually removing the links, but I suppose that dpkg should not 
worry about symlinks if they are working.
As this error is summing up, I don't want to manually delete all links, 
therefore I just start deleting all of them
e.g.:
  rm /usr/share/doc/*/changelog.*gz
  rm /usr/share/doc/*/NEWS.*gz

in a script.

Here is a reinstallation call
$ sudo apt-get install -f
[sudo] password for User: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
[...]
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libgl1-mesa-dri:i386
The following packages will be upgraded:
  libgl1-mesa-dri:i386
1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
Need to get 0 B/5.085 kB of archives.
After this operation, 7.536 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 1693621 files and directories currently installed.)
Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb 
(--unpack):
 symbolic link '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has 
changed from 80 to 36
Errors were encountered while processing:
 /var/cache/apt/archives/libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb
$


and after removing the links:

$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
[...]
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libgl1-mesa-dri:i386
The following packages will be upgraded:
  libgl1-mesa-dri:i386
1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
Need to get 0 B/5.085 kB of archives.
After this operation, 7.536 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 1693621 files and directories currently installed.)
Preparing to unpack .../libgl1-mesa-dri_17.0.7-0ubuntu0.16.04.1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) over 
(12.0.6-0ubuntu0.16.04.1) ...
Setting up libgl1-mesa-dri:i386 (17.0.7-0ubuntu0.16.04.1) ...
Installing new version of config file /etc/drirc ...
Setting up libgl1-mesa-dri:amd64 (17.0.7-0ubuntu0.16.04.1) ...
Setting up libegl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
Setting up libwayland-egl1-mesa:amd64 (17.0.7-0ubuntu0.16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
$

Regards

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-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: None
Date: Tue Aug  1 10:52:58 2017
DistUpgraded: 2016-08-24 16:49:18,141 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-87-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-dri:17.0.7-0ubuntu0.16.04.1
 Unpacking imagemagick (8:6.8.9.9-7ubuntu5.9) over (8:6.8.9.9-7ubuntu5.8) ...
 dpkg: error processing archive 
/var/cache/apt/archives/imagemagick_8%3a6.8.9.9-7ubuntu5.9_amd64.deb (--unpack):
  symbolic link '/usr/share/doc/imagemagick/changelog.Debian.gz' size has 
changed from 88 to 40
ErrorMessage: symbolic link 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' size has changed from 80 
to 36
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0686]
 NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] GK107M [GeForce GT 650M] [1025:0686]
InstallationDate: Installed on 2014-06-21 (1136 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Acer Aspire V3-771
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 

[Desktop-packages] [Bug 332646] Re: sftp does not set timestamps

2017-08-01 Thread Julian Rüger
I posted a bounty for the underlying gvfs bug:

https://www.bountysource.com/issues/23459433-gvfs-should-set-file-
attributes-properly

If you want this fixed, please consider contributing.
Thanks and sorry for spam ;)

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

Title:
  sftp does not set timestamps

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gvfs

  when copying or moving files to a directory mounted over sftp, the
  time stamps are not preserved.

  this affects both hardy and intrepid (in hardy, it was tested with a
  patched version of nautilus hence that version used to forget
  timestamps on copy anyway). in both cases, i tested it locally and
  everything was preserved as it should be.

  moreover, when moving, nautilus first displays the correct time stamp
  and only on refreshing shows the wrong updated one.

  as timestamps can be considered considered important information, i
  suggest this bug be treated as "losing data without notice".

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

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


Re: [Desktop-packages] [Bug 1703110] Re: notes doesn't delete only if empty

2017-08-01 Thread Roland Boros
Hello Brian,


I'm very grateful for your work, but I can't compile it. Terminal says this 
after the "./configure" command: bash: ./configure: Engedély megtagadva

It means permission is denied.
I can't figure it out. But I hope one day it will work.


Thank you again,

Roland

2017. júl. 28., p 0.50-kor-kor, Brian Murray  írta:
Hello Roland, or anyone else affected, Accepted gnome-applets into 
zesty-proposed. The package will build now and be available at 
https://launchpad.net/ubuntu/+source/gnome- applets/3.22.0-2ubuntu0.1 in a few 
hours, and then in the -proposed repository. Please help us by testing this new 
package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation 
on how to enable and use -proposed.Your feedback will aid us getting this 
update out to other Ubuntu users. If this package fixes the bug for you, please 
add a comment to this bug, mentioning the version of the package you tested and 
change the tag from verification-needed-zesty to verification-done-zesty. If it 
does not fix the bug for you, please add a comment stating that, and change the 
tag to verification-failed-zesty. In either case, details of your testing will 
help us make a better decision. Further information regarding the verification 
process can be found at 
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in 
advance! ** Changed in: gnome-applets (Ubuntu Zesty) Status: Confirmed => Fix 
Committed ** Tags added: verification-needed verification-needed-zesty
--
You received this bug notification because you are subscribed to the bug 
report. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete 
only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in 
gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] 
Unnesessary work for the user as he is forced to clear the note from text in 
order to delete it. It makes it more difficult that selecting text isn't 
possible with mouse. [Test Case] Write anything in a note and it can't be 
deleted with 'x' or with 'delete notes' menu item. [Proposed Fix] The fix is a 
backport of two upstream commits: - 
https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a 
“sticky-notes: make sure that notes are really saved” - 
https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf 
“sticky-notes: fix path to resource file for delete dialog” [Regression 
Potential] The fix definitely improves the Sticky Notes applet because without 
ability to save notes that applet is mostly unusable. It does not touch other 
applets so no regression expected there. [Other Info] System configuration:  
roland@roland-Lenovo-ideapad-110-15I `:+ss+:` 
   -+ssyy+- OS: 
Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo 
ideapad 110-15IBR/ssshdmmNNmmyNhss/ Kernel: 
4.10.0-26-generic   +shmydMMMNy+ Uptime: 4 hours, 45 
mins  /hNMMMyhhhmNMMMNh/ Packages: 2360 
.dMMMNhsshNMMMd. Shell: bash 4.4.7 
+hhhyNMMNyyNMMMysss+ Resolution: 1366x768 
ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME 
ossyNMMMNyMMhsshmmmhssso WM: Compiz 
+hhhyNMMNyyNMMMysss+ WM Theme: Adwaita 
.dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3]  
/hNMMMyhhhdNMMMNh/ Icons: Ubuntu-mono-light [GTK2/3]   
+sdmydy+ Terminal: gnome-terminal
/ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH 
.ossdMMMNyo. GPU: Intel HD Graphics 405   
-+syyy+- Memory: 1674MiB / 3862MiB 
`:+ss+:` .-/+oooo+/-. Stickynotes version: 
3.22.0 To manage notifications about this bug go to: 
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+subscriptions

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

Title:
  notes doesn't delete only if empty

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  Unnesessary work for the user as he is forced to clear the note from
  text in order to delete it. It makes it more difficult that selecting
  text isn't possible with mouse.

  [Test Case]

  - Write anything in a note
  - Try to select text in a note
  - Try to delete it with 'x' or with 'delete notes' menu item

  [Proposed Fix]

  The fix is a backport of three upstream commits:
  - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a 
“sticky-notes: make sure that notes are really saved”
  - 

[Desktop-packages] [Bug 1707691] Re: libxfont1-dev is missing fontutil.h

2017-08-01 Thread Timo Aaltonen
I mean either you build with xserver-xorg-dev & libxfont1-dev, or
xserver-xorg-dev-hwe-16.04 & libxfont-dev. Can't mix the two. Fix your
pkg to match.

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

Title:
  libxfont1-dev is missing fontutil.h

Status in libxfont package in Ubuntu:
  Won't Fix

Bug description:
  /usr/include/xorg/dixfont.h includes X11/fonts/fontutil.h.

  fontutil.h is contained in libxfont1-dev package not libxfont-dev
  package (version 2.0.1).

  I am trying to build xorgxrdp and it fails because fontutil.h is
  missing.

  In Ubuntu, libxfont1-dev package is required however libxfont1-dev and
  libxfont-dev cannot be installed together. This is the problem.

  I looked at Debian, too. /usr/include/xorg/dixfont.h in Debian does
  NOT include X11/fonts/fontutil.h.

  This is the right state.

  Package info: Ubuntu 16.04

  $  dpkg -la | grep -e xserver-xorg-dev -e libxfont-dev
  ii  libxfont-dev   1:2.0.1-3~ubuntu16.04.1
amd64X11 font rasterisation library (development headers)
  ii  xserver-xorg-dev   2:1.18.4-0ubuntu0.3
amd64Xorg X server - development files

  brian

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

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


[Desktop-packages] [Bug 1707691] Re: libxfont1-dev is missing fontutil.h

2017-08-01 Thread Timo Aaltonen
you need to build with xserver-xorg-dev-hwe-16.04 instead

** Changed in: libxfont (Ubuntu)
   Status: New => Won't Fix

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

Title:
  libxfont1-dev is missing fontutil.h

Status in libxfont package in Ubuntu:
  Won't Fix

Bug description:
  /usr/include/xorg/dixfont.h includes X11/fonts/fontutil.h.

  fontutil.h is contained in libxfont1-dev package not libxfont-dev
  package (version 2.0.1).

  I am trying to build xorgxrdp and it fails because fontutil.h is
  missing.

  In Ubuntu, libxfont1-dev package is required however libxfont1-dev and
  libxfont-dev cannot be installed together. This is the problem.

  I looked at Debian, too. /usr/include/xorg/dixfont.h in Debian does
  NOT include X11/fonts/fontutil.h.

  This is the right state.

  Package info: Ubuntu 16.04

  $  dpkg -la | grep -e xserver-xorg-dev -e libxfont-dev
  ii  libxfont-dev   1:2.0.1-3~ubuntu16.04.1
amd64X11 font rasterisation library (development headers)
  ii  xserver-xorg-dev   2:1.18.4-0ubuntu0.3
amd64Xorg X server - development files

  brian

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

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


[Desktop-packages] [Bug 1601971] Re: update fails, "AppStream cache update failed."

2017-08-01 Thread Aadithya S
Bug also confirmed in 16.04.2 live boot. So far,this seems to work : 
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1601971/comments/11

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

Title:
  update fails, "AppStream cache update failed."

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  Booted 16.04 amd64 from DVD, opened a gnome-terminal and ran,

  ubuntu@ubuntu:~$ sudo apt-get update
  Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial InRelease
  Hit:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial Release
  Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]  
 
  Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[119 kB]
  Get:8 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB]
  Get:9 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB]
   
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[45.3 kB]
  Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 
Metadata [44.0 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 
Icons [50.8 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
DEP-11 Metadata [158 B]
  Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata 
[733 kB]
  Get:15 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 
kB]
  Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 
[252 kB]
  Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en 
[99.8 kB]
  Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 
Metadata [186 kB]
  Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 
Icons [150 kB]
  Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
DEP-11 Metadata [157 B]
  Fetched 4,293 kB in 1s (2,360 kB/s) 

  ** (appstreamcli:2593): CRITICAL **: Error while moving old database out of 
the way.
  AppStream cache update failed.
  Reading package lists... Done

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Mon Jul 11 19:24:40 2016
  LiveMediaBuild: 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: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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