[Desktop-packages] [Bug 2023327] [NEW] package ubuntu-standard 1.501 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret

[Niels Baggesen]

Public bug reported:

Trying to install ubuntu-gnome-desktop

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: ubuntu-standard 1.501
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Apr 17 17:53:06 2023
ErrorMessage: afhængighedsproblemer - efterlader den ukonfigureret
InstallationDate: Installed on 2016-02-08 (2677 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: ubuntu-meta
Title: package ubuntu-standard 1.501 failed to install/upgrade: 
afhængighedsproblemer - efterlader den ukonfigureret
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

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

Title:
  package ubuntu-standard 1.501 failed to install/upgrade:
  afhængighedsproblemer - efterlader den ukonfigureret

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Trying to install ubuntu-gnome-desktop

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-standard 1.501
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Apr 17 17:53:06 2023
  ErrorMessage: afhængighedsproblemer - efterlader den ukonfigureret
  InstallationDate: Installed on 2016-02-08 (2677 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: ubuntu-meta
  Title: package ubuntu-standard 1.501 failed to install/upgrade: 
afhængighedsproblemer - efterlader den ukonfigureret
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1944102] [NEW] unity-settings-daemon crashed with SIGSEGV in XQueryExtension()

[Niels Baggesen]

Public bug reported:

Just logged in, i opened Terminal ...

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Sep 20 06:33:42 2021
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2016-02-08 (2050 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
 LANG=da_DK.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libXext.so.6
 XSyncQueryExtension () from /lib/x86_64-linux-gnu/libXext.so.6
 gsd_idle_monitor_init_dbus () from 
/lib/x86_64-linux-gnu/libunity-settings-daemon.so.1
 main ()
Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare staff sudo 
wireshark
separator:

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


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

** Information type changed from Private to Public

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

Title:
  unity-settings-daemon crashed with SIGSEGV in XQueryExtension()

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

Bug description:
  Just logged in, i opened Terminal ...

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Sep 20 06:33:42 2021
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (2050 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libXext.so.6
   XSyncQueryExtension () from /lib/x86_64-linux-gnu/libXext.so.6
   gsd_idle_monitor_init_dbus () from 
/lib/x86_64-linux-gnu/libunity-settings-daemon.so.1
   main ()
  Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare staff sudo 
wireshark
  separator:

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


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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows

[Niels Keurentjes]

Made a quick video to illustrate the issues:
https://youtu.be/SwBtxqTqsHc

** Summary changed:

- Fractional scaling does not persist across reboots in resizable VM windows
+ Fractional scaling does not persist while resizing or rebooting in VM windows

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows

[Niels Keurentjes]

Behaviour seems somewhat improved but the root issue is still there.

When rebooting with VMware Player running the scaling is now remembered
correctly, however if I then shut the VM down completely and restart it,
it still starts up at first in default screen size, removing the
scaling.

Also the scaling modifications seem more aggressive now - if I have the
windowed VMware Player maximized on my 4k screen (practical resolution
3840x2015, note not 2160 pixels high due to host window chrome) it
allows me to set 125% scaling, but if I then resize the host window or
just unmaximize the 125% options disappear from setting *and Ubuntu
snaps right back to 200%*.

So effectively what I described in
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/9
is still happening as before.

I still think
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/11
is the only true fix - in _virtual_ monitors the system should never
intervene with scaling settings at all and just trust whatever the user
selects for himself, as he may be resizing, maximizing, changing
displays etc. all the time.

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows

[Niels Keurentjes]

Wayland doesn't work at all, hangs for 5+ minutes after login in VMware
(this reflects my experiences with Wayland on 18.04 and 18.10 in VMware,
don't think I've ever seen it work properly).

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

Title:
  Fractional scaling does not persist across reboots in resizable VM
  windows

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows

[Niels Keurentjes]

Considering that Mutter indeed knows that a monitor is virtual -
shouldn't it just ignore resolution completely for resolving existing
configuration? It changes all the time while dragging windows on the
host machine, maximizing,  minimizing etc

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

Title:
  Fractional scaling does not persist across reboots in resizable VM
  windows

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885026] Re: Fractional scaling contains 175% option twice

[Niels Keurentjes]

Thanks Daniel for referencing that comment, it's indeed also relevant
here.

It seems weird as a whole that the available scaling options appear to
depend on common monitor resolutions. As stated there at 3840x2075
(that's 4k minus the VMware window borders) I see the
100/125/175/175/250 selector, at 3480x1859 I don't even get any
fractional scaling options at all.

It looks like somebody tried to make it really user friendly by
tailoring the experience towards the end user ("nobody wants 300%
scaling on a 640x480 screen") and then completely overlooked the
windowed VM scenario, or any kind of remote desktop where you also want
to be able to set the scaling correctly based on the host machine's
resolution.

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

Title:
  Fractional scaling contains 175% option twice

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

Bug description:
  When opening the Settings, select Displays and then enable "Fractional
  Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250%

  If you click the first 175% option it will even automatically select
  the second one instead.

  The third option should likely be 150% instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 15:21:07 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling not persisted in VMware Player

[Niels Keurentjes]

I think I just found out the real issue, and that information is not
going to help you because it will contain seemingly random indicators
depending on how I size my windows.

VMware Player, like most virtualization software, runs windowed by
default, and that window is dynamically resizeable. Now someone in all
their wisdom at Ubuntu apparently decided that the available scaling
options depend on the current resolution.

So when I keep the settings screen open, and start resizing the window,
thus dynamically resizing the "monitor", I can see the available scaling
options change in real time. At 3840x2075 (that's 4k minus the VMware
window borders) I see the 100/125/175/175/250 selector, at 3480x1859 I
don't even get any fractional scaling options, at really low resolutions
all scaling options disappear.

When VMware Player boots, it snaps to the default 1024x768 size. So
that's the monitor resolution when the desktop loads, it concludes
scaling is not allowed at that level, and resets to 100%, no matter what
it was before the reboot.

The real issue appears to be: scaling settings should not be modified
based on resolution during boot.

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

Title:
  Fractional scaling not persisted in VMware Player

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player

[Niels Keurentjes]

gnome-shell seems to be the right one, filed
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885026

This bug can continue to be about the missing persistence.

** Summary changed:

- Fractional scaling broken in VMware Player
+ Fractional scaling not persisted in VMware Player

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

Title:
  Fractional scaling not persisted in VMware Player

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885026] [NEW] Fractional scaling contains 175% option twice

[Niels Keurentjes]

Public bug reported:

When opening the Settings, select Displays and then enable "Fractional
Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250%

If you click the first 175% option it will even automatically select the
second one instead.

The third option should likely be 150% instead.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 24 15:21:07 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-22 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Fractional scaling contains 175% option twice

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When opening the Settings, select Displays and then enable "Fractional
  Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250%

  If you click the first 175% option it will even automatically select
  the second one instead.

  The third option should likely be 150% instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 15:21:07 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player

[Niels Keurentjes]

I opened https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1885025 for the open-vm-tools issue, I don't know for which
package I should file the bug with the missing 150% setting.

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

Title:
  Fractional scaling not persisted in VMware Player

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player

[Niels Keurentjes]

As a sidenote: the "Fractional scaling selector" in display settings
allows me to choose between 100%, 125%, 175%, 175% and 250%. Note the
duplicate 175% that should likely be 150%.

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

Title:
  Fractional scaling broken in VMware Player

Status in mutter package in Ubuntu:
  New

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1884754] [NEW] Fractional scaling broken in VMware Player

[Niels Keurentjes]

Public bug reported:

Related to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but
those report the issues are fixed. They also do not mention the VMware
specific issues.

Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
automatically with Easy Install), go to settings, enable Fractional
Scaling and select any non-integer value.

Results:
 - The scaling is applied
 - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
 - After next reboot the setting is reverted to 100%

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 23 04:30:21 2020
InstallationDate: Installed on 2020-06-22 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Fractional scaling broken in VMware Player

Status in mutter package in Ubuntu:
  New

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804965] [NEW] package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: forsøger at overskrive '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', som også er i pakken nvidia-

[Niels Jensen]

Public bug reported:

I do not have further details about the issue.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglvnd-dev 1.0.0-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libgles1:amd64: Install
 libglvnd-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Nov 24 22:05:25 2018
DpkgHistoryLog:
 Start-Date: 2018-11-24  22:05:24
 Commandline: apt-get install -f
 Requested-By: niels (1001)
 Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic)
 Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
ErrorMessage: forsøger at overskrive 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', som også er i pakken nvidia-340 
340.106-0ubuntu3
InstallationDate: Installed on 2018-05-13 (195 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: libglvnd
Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
forsøger at overskrive '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', som også er 
i pakken nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade:
  forsøger at overskrive '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so',
  som også er i pakken nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  I do not have further details about the issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libgles1:amd64: Install
   libglvnd-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Nov 24 22:05:25 2018
  DpkgHistoryLog:
   Start-Date: 2018-11-24  22:05:24
   Commandline: apt-get install -f
   Requested-By: niels (1001)
   Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic)
   Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
  ErrorMessage: forsøger at overskrive 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', som også er i pakken nvidia-340 
340.106-0ubuntu3
  InstallationDate: Installed on 2018-05-13 (195 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
forsøger at overskrive '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', som også er 
i pakken nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back

[Niels Roetert]

Attached the output as requested by Daniel van Vugt.

** Attachment added: "Output of  journalctl -b-1 > prev_boot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799964/+attachment/5205732/+files/prev_boot.txt

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

Title:
  Ubuntu  18.10 After Blank Screen System Won't Come Back

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 if the blank screen feature initiates (5 minutes
  default) the system will remain blank and there is no way to get the
  display back on without a hard reset. The video card I am using is a
  Vega 64. Other users who have Vega AMD GPU's are experiencing the same
  issue. This is only happening in Ubuntu 18.10. Does not occur in my
  Arch or Fedora installs.

  To reproduce:
  - Let 'Blank Screen' feature execute (5 min default)
  - Screen will not come back

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 10:18:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
  InstallationDate: Installed on 2018-10-19 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd. MS-7B78
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PRO CARBON (MS-7B78)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B78
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back

[Niels Roetert]

Similar to #1799965

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

Title:
  Ubuntu  18.10 After Blank Screen System Won't Come Back

Status in xorg package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.10 if the blank screen feature initiates (5 minutes
  default) the system will remain blank and there is no way to get the
  display back on without a hard reset. The video card I am using is a
  Vega 64. Other users who have Vega AMD GPU's are experiencing the same
  issue. This is only happening in Ubuntu 18.10. Does not occur in my
  Arch or Fedora installs.

  To reproduce:
  - Let 'Blank Screen' feature execute (5 min default)
  - Screen will not come back

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 10:18:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
  InstallationDate: Installed on 2018-10-19 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd. MS-7B78
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PRO CARBON (MS-7B78)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B78
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1799965] [NEW] Blank screen doesn't recover

[Niels Roetert]

Public bug reported:

When I leave my machine for 10 minutes (default is 5) the screen blanks.
Unfortunately it doesn't come back after that, not by hitting a key or moving 
the mouse.
I end up stopping the machine and turning it back on again.

May be related with my Vega 64 card/drivers?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 25 16:21:52 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
InstallationDate: Installed on 2018-10-24 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2b5f903c-f044-4872-8865-685b48bb83de ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4023
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  Blank screen doesn't recover

Status in xorg package in Ubuntu:
  New

Bug description:
  When I leave my machine for 10 minutes (default is 5) the screen blanks.
  Unfortunately it doesn't come back after that, not by hitting a key or moving 
the mouse.
  I end up stopping the machine and turning it back on again.

  May be related with my Vega 64 card/drivers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 16:21:52 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
  InstallationDate: Installed on 2018-10-24 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2b5f903c-f044-4872-8865-685b48bb83de ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4023
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Desktop-packages] [Bug 1795479] [NEW] ark does not save pdf from internal viewer

[Niels Elgaard Larsen]

Public bug reported:

Open a zip file with ark
in ark settings choose preview the file with internal previewer.
Open a pdf file from the zip archive.

Save the file using "Save as by choosing a new directory (outside /tmp/)

The file is saved, but when the PDF previewer is closed, the file disappears.
an strace of the ark process shows 
  unlink("/home/elgaard/foo.pdf") 

which is where the PDF was saved to.


I did have a similar problems years ago, and I am almost sure that I checked 
the option "open the file with associated application" back then and suspect 
that the setting was changed behind my back at a later update.

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ark

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

Title:
  ark does not save pdf from internal viewer

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Open a zip file with ark
  in ark settings choose preview the file with internal previewer.
  Open a pdf file from the zip archive.

  Save the file using "Save as by choosing a new directory (outside
  /tmp/)

  The file is saved, but when the PDF previewer is closed, the file disappears.
  an strace of the ark process shows 
unlink("/home/elgaard/foo.pdf") 

  which is where the PDF was saved to.

  
  I did have a similar problems years ago, and I am almost sure that I checked 
the option "open the file with associated application" back then and suspect 
that the setting was changed behind my back at a later update.

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

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

[Desktop-packages] [Bug 472450] Re: gnome-keyring crashes for no apparent reason

[Niels Erik Jensen]

?

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

Title:
  gnome-keyring crashes for no apparent reason

Status in gnome-keyring package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-keyring

  doing nothing related to the keyring. entering keyring password at
  startup succeeded.

  applications in use: evolution, firefox, tasque, empathy

  possibly unrelated observations:
  a jabber account used in empathy regularly goes offline (about every 11 
minutes) - reason unknown.

  might be related to: #405667

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: ERROR:gck-file-tracker.c:97:update_file: assertion failed: 
(old_mtime)
  CheckboxSubmission: 0b44424daa2eeb8fdbb5cd71b44a076d
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  CrashCounter: 1
  Date: Tue Nov  3 10:44:48 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  Package: gnome-keyring 2.28.1-0ubuntu1
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron: LANG=de_DE.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   __kernel_vsyscall ()
   *__GI_raise (sig=6)
   *__GI_abort () at abort.c:92
   IA__g_assertion_message (domain=0x0, 
   IA__g_assertion_message_expr (domain=0x0,
  Title: gnome-keyring-daemon assert failure: 
ERROR:gck-file-tracker.c:97:update_file: assertion failed: (old_mtime)
  Uname: Linux 2.6.31-14-generic-pae i686
  UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev 
plugdev powerdev sambashare scanner users video www-data

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

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

[Desktop-packages] [Bug 1754173] [NEW] Laptop has integrated Intel and discrete Nvidia graphics, the Intel graphics are not detected. Worked fine with 17.10.

[Niels Roetert]

Public bug reported:

HP ZBook 15, 2014 model.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Wed Mar  7 22:38:17 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:197b]
InstallationDate: Installed on 2018-03-07 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307)
MachineType: Hewlett-Packard HP ZBook 15
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=752bcb50-d5d1-4251-a33b-18fc83b6dd9e ro quiet splash vt.handoff=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L70 Ver. 01.39
dmi.board.name: 1909
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.56
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL70Ver.01.39:bd01/24/2018:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.56:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP ZBook 15
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic regression reproducible 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/1754173

Title:
  Laptop has integrated Intel and discrete Nvidia graphics, the Intel
  graphics are not detected. Worked fine with 17.10.

Status in mesa package in Ubuntu:
  New

Bug description:
  HP ZBook 15, 2014 model.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar  7 22:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:197b]
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=752bcb50-d5d1-4251-a33b-18fc83b6dd9e ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L70 Ver. 01.39
  dmi.board.name: 1909
 

[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Niels Böhm]

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

On Xubuntu, can you try downgrading the package xubuntu-default-settings
from version 18.04.2 to version 18.04.1? Maybe it's related to what I'm
seeing in bug #1752798

(you can find the older package here:
https://launchpad.net/ubuntu/+source/xubuntu-default-
settings/18.04.1/+build/13749132 )

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Niels Erik Jensen]

?

-- 
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 1654703] Re: /usr/share/doc/fig2dev/CHANGES.gz is a broken symlink

[Niels Thykier]

This looks like it is caused by the Ubuntu specific changes to
dh_installchangelogs.

Namely, the original debhelper will look for (among other) "CHANGES" as
an upstream changelog.  Ubuntu have removed this to save disk space and
leads to debhelper picking "changelog" as a candidate for the "main
package" (and nothing for others).

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

Title:
  /usr/share/doc/fig2dev/CHANGES.gz is a broken symlink

Status in debhelper package in Ubuntu:
  New
Status in fig2dev package in Ubuntu:
  Confirmed

Bug description:
  nate@minerva:~$ ls -l /usr/share/doc/fig2dev/CHANGES.gz 
  lrwxrwxrwx 1 root root 12 Aug 14 12:22 /usr/share/doc/fig2dev/CHANGES.gz -> 
changelog.gz
  nate@minerva:~$ ls -l /usr/share/doc/fig2dev/changelog.gz
  ls: cannot access '/usr/share/doc/fig2dev/changelog.gz': No such file or 
directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: fig2dev 1:3.2.6-2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Jan  6 21:07:13 2017
  SourcePackage: fig2dev
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (19 days ago)

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

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

[Desktop-packages] [Bug 1471342] Re: Sync gnome-sudoku 1:3.16.0-1 (main) from Debian unstable (main)

[Aputsiak Niels Janussen]

Danish translations of gnome-sudoku on Launchpad hasn't been updated since 
2013. 
The upstream translations has been done consistenly, see here: 
https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da
Could something be broken?

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

Title:
  Sync gnome-sudoku 1:3.16.0-1 (main) from Debian unstable (main)

Status in gnome-sudoku package in Ubuntu:
  Fix Released

Bug description:
  Please sync gnome-sudoku 1:3.16.0-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/control:
  - Build-depend on appstream-util
* debian/control:
  - Build-depend on libjson-glib-dev
* New upstream release:
  - Miscellaneous fixes
  - Fix crash that was reported by Ubuntu's crash catcher over 5000 times
  - Some more stuff is translated now
* debian/patches/git_working_undo.patch:
* debian/patches/use_correct_translation_domain.patch:
  - Applied upstream
* New upstream version
* debian/control.in: updated g-i requirement
* debian/patches/use_correct_translation_domain.patch:
  - use the correct translations domain (lp: #1327205)
* debian/patches/git_working_undo.patch:
  - "This fixes undo when only one number is on the board." (lp: #1272716)
* 0002-fix-sort-syntax-error.patch: Backport upstream
  commit that fixes crashes when saving a "Very Hard"
  game (LP: #1252220).
* 0002-fix-sort-syntax-error.patch: Backport upstream
  commit that fixes crashes when saving a "Very Hard"
  game (LP: #1252220).
* New upstream release:
  - Quit when SIGINT is received instead of ignoring it
  - Fix everything being initially hidden
  - Fix a crash when clearing notes
  - Slightly improve the look of the number pad
  - Fix the high contrast icon
  - Add an appdata file for GNOME Software
  - Fix running uninstalled
  - Fix NumberBox events configuration with latest pygobject
  - Game no longer disappears when opening "print multiple sudokus" in 
fullscreen
  - Reduce the width of the About dialog
  - Don't use deprecated GObject.timeout_add_seconds
  - Use /usr/bin/python instead of /usr/bin/env/python
  - Fix some broken links in user help
* debian/patches/01_fix_runtime_error_with_new_pygobject.patch:
  - Applied upstream
* Apply patch porting gnome-sudoku to python3. (LP: #1078720)
  There are no real changes left

  Changelog entries since current wily version 1:3.16.0-0ubuntu2:

  gnome-sudoku (1:3.16.0-1) unstable; urgency=medium

* New upstream release.
* Update Build-Depends:
  - Add appstream-util.
  - Bump intltool to (>= 0.50).
  - Bump libgtk-3-dev to (>= 3.15.0) as per upstream gnome-3-16 branch.
  - Bump valac (>= 0.27.1) as per upstream gnome-3-16 branch.
* Bump debhelper compatibility level to 9.

   -- Michael Biebl   Sun, 14 Jun 2015 15:01:26 +0200

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

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

[Desktop-packages] [Bug 1574052] Re: titlesec does not render section numbers

[Niels van Adrichem]

Hi Michael, that is perfectly possible, I have actually adopted it in a
class-file, so I have not tested it with the \makeatletter and
\makeatother commands myself. I tried to (apparently incorrectly) adapt
the code to the use-case of Frédéric. Please try for yourself what
works, thank you for your observation.

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

Title:
  titlesec does not render section numbers

Status in texlive-extra package in Ubuntu:
  Triaged

Bug description:
  The titlesec package does not work properly after distribution upgrade
  to 16.04LTS.

  Steps to reproduce:
  1) Create a tex document and include titlesec
  2) Create some sections headers via \section{Some section}
  3) Run pdflatex/lualatex/xelatex

  What should happen
  The section should be created with the corresponding number: 1 Some Section

  What happens
  Only the text is present: Some Section

  If the section header format is changed via \titleformat, the entire
  formatting disappears from the final pdf.

  
  Might be related to 
https://groups.google.com/forum/#!topic/comp.text.tex/MBd3-o2Dzx8

  
  Ubuntu Version: 16.04 LTS
  texlive-latex-extra Version: 2015.20160320-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1574052/+subscriptions

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

[Desktop-packages] [Bug 1574052] Re: titlesec does not render section numbers

[Niels van Adrichem]

You can also add the following after \usepackage{titlesec} to only apply
the patch when you're on the specific version of titlesec (which is what
I did on a shared project). Remove the \makeatletter and \makeatother
and change \usepackage to \RequirePackage when you're adding it to your
classfile right after \RequirePackage{titlesec}.

\@ifpackagelater{titlesec}{2016/03/21}{%
% Package titlesec is on version 2.10.2 or higher, nothing to do %
}{%
% Check if package titlesec is on version 2.10.1 %
\@ifpackagelater{titlesec}{2016/03/15}{%
% Package titlesec on version 2.10.1, patch accordingly %
\usepackage{etoolbox}%
\makeatletter

\patchcmd{\ttlh@hang}{\parindent\z@}{\parindent\z@\leavevmode}{}{}%
\patchcmd{\ttlh@hang}{\noindent}{}{}{}%
\makeatother
}{%
% Package titlsecon is on version 2.10.0 or lower, nothing to 
do %
}%
}

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

Title:
  titlesec does not render section numbers

Status in texlive-extra package in Ubuntu:
  Triaged

Bug description:
  The titlesec package does not work properly after distribution upgrade
  to 16.04LTS.

  Steps to reproduce:
  1) Create a tex document and include titlesec
  2) Create some sections headers via \section{Some section}
  3) Run pdflatex/lualatex/xelatex

  What should happen
  The section should be created with the corresponding number: 1 Some Section

  What happens
  Only the text is present: Some Section

  If the section header format is changed via \titleformat, the entire
  formatting disappears from the final pdf.

  
  Might be related to 
https://groups.google.com/forum/#!topic/comp.text.tex/MBd3-o2Dzx8

  
  Ubuntu Version: 16.04 LTS
  texlive-latex-extra Version: 2015.20160320-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1574052/+subscriptions

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

[Desktop-packages] [Bug 1021375] Re: Nautilus says the USB stick is read only when it is not

[niels]

Has the same problem wie 12.04 #22 helps. Here the diff
diff nautilus.bad/ nautilus
diff nautilus.bad/desktop-metadata nautilus/desktop-metadata
3c3
< nautilus-icon-view-layout-timestamp=1449680128
---
> nautilus-icon-view-layout-timestamp=1449688294

Which is really strange. No idea why this fix the problem.

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

Title:
  Nautilus says the USB stick is read only when it is not

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

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

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

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

[Desktop-packages] [Bug 1429390] Re: Xorg freezes irrecoverably with EQ overflowing

[Niels]

As per https://wiki.ubuntu.com/X/Troubleshooting/Freeze, these
attachments follow:

- `avivotool regs all` output captured during a working X session: 
regdump_good.txt
- `avivotool regs all` output captured during a frozen X session: 
regdump_bad.txt
- dmesg log captured after a freeze

** Attachment added: `avivotool regs all` output captured during a working X 
session
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1429390/+attachment/4337822/+files/regdump_good.txt

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

Title:
  Xorg freezes irrecoverably with EQ overflowing

Status in xorg-server package in Ubuntu:
  New

Bug description:
  X frequently freezes with EQ overflowing message(s) in the logs.
  lightdm/X can be stopped and restarted, but never returns to a usable
  state until rebooting. Either the screen remains black, or the input
  devices remain frozen.

  This happens multiple times a day but can not be reliably reproduced.
  Frequently, it will happen within minutes after booting up; other
  times it seems to happen at times of high load / memory usage.
  Sometimes the system remains working for hours, sometimes just for
  minutes.

  The problem occurs both with the xserver-xorg-video-ati and fglrx
  drivers from the standard repositories (+ backports, + updates, +
  security).

  The system remains fully responsive via SSH, with seemingly no
  dangling processes after stopping X.

  Kernel 3.16.0-31-generic, amd64.
  Release utopic.

  Graphics card:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Device 21f6
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e000 (64-bit, prefetchable) [size=256M]
  Memory at fbcc (64-bit, non-prefetchable) [size=128K]
  I/O ports at de00 [size=256]
  [virtual] Expansion ROM at fbc0 [disabled] [size=128K]
  Capabilities: [50] Power Management version 3
  Capabilities: [58] Express Legacy Endpoint, MSI 00
  Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 
Len=010 ?
  Capabilities: [150] Advanced Error Reporting
  Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Fri Mar  6 10:38:17 2015
  ExecutablePath: /usr/bin/Xorg
  ProcEnviron:
   
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1429390] Re: Xorg freezes irrecoverably with EQ overflowing

[Niels]

** Attachment added: `avivotool regs all` output captured during a frozen X 
session
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1429390/+attachment/4337823/+files/regdump_bad.txt

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

Title:
  Xorg freezes irrecoverably with EQ overflowing

Status in xorg-server package in Ubuntu:
  New

Bug description:
  X frequently freezes with EQ overflowing message(s) in the logs.
  lightdm/X can be stopped and restarted, but never returns to a usable
  state until rebooting. Either the screen remains black, or the input
  devices remain frozen.

  This happens multiple times a day but can not be reliably reproduced.
  Frequently, it will happen within minutes after booting up; other
  times it seems to happen at times of high load / memory usage.
  Sometimes the system remains working for hours, sometimes just for
  minutes.

  The problem occurs both with the xserver-xorg-video-ati and fglrx
  drivers from the standard repositories (+ backports, + updates, +
  security).

  The system remains fully responsive via SSH, with seemingly no
  dangling processes after stopping X.

  Kernel 3.16.0-31-generic, amd64.
  Release utopic.

  Graphics card:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Device 21f6
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e000 (64-bit, prefetchable) [size=256M]
  Memory at fbcc (64-bit, non-prefetchable) [size=128K]
  I/O ports at de00 [size=256]
  [virtual] Expansion ROM at fbc0 [disabled] [size=128K]
  Capabilities: [50] Power Management version 3
  Capabilities: [58] Express Legacy Endpoint, MSI 00
  Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 
Len=010 ?
  Capabilities: [150] Advanced Error Reporting
  Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Fri Mar  6 10:38:17 2015
  ExecutablePath: /usr/bin/Xorg
  ProcEnviron:
   
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1429390] Re: Xorg freezes irrecoverably with EQ overflowing

[Niels]

** Attachment added: dmesg log captured after a freeze
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1429390/+attachment/4337824/+files/dmesg.log

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

Title:
  Xorg freezes irrecoverably with EQ overflowing

Status in xorg-server package in Ubuntu:
  New

Bug description:
  X frequently freezes with EQ overflowing message(s) in the logs.
  lightdm/X can be stopped and restarted, but never returns to a usable
  state until rebooting. Either the screen remains black, or the input
  devices remain frozen.

  This happens multiple times a day but can not be reliably reproduced.
  Frequently, it will happen within minutes after booting up; other
  times it seems to happen at times of high load / memory usage.
  Sometimes the system remains working for hours, sometimes just for
  minutes.

  The problem occurs both with the xserver-xorg-video-ati and fglrx
  drivers from the standard repositories (+ backports, + updates, +
  security).

  The system remains fully responsive via SSH, with seemingly no
  dangling processes after stopping X.

  Kernel 3.16.0-31-generic, amd64.
  Release utopic.

  Graphics card:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Device 21f6
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e000 (64-bit, prefetchable) [size=256M]
  Memory at fbcc (64-bit, non-prefetchable) [size=128K]
  I/O ports at de00 [size=256]
  [virtual] Expansion ROM at fbc0 [disabled] [size=128K]
  Capabilities: [50] Power Management version 3
  Capabilities: [58] Express Legacy Endpoint, MSI 00
  Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 
Len=010 ?
  Capabilities: [150] Advanced Error Reporting
  Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Fri Mar  6 10:38:17 2015
  ExecutablePath: /usr/bin/Xorg
  ProcEnviron:
   
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1429390] [NEW] Xorg freezes irrecoverably with EQ overflowing

[Niels]

Public bug reported:

X frequently freezes with EQ overflowing message(s) in the logs.
lightdm/X can be stopped and restarted, but never returns to a usable
state until rebooting. Either the screen remains black, or the input
devices remain frozen.

This happens multiple times a day but can not be reliably reproduced.
Frequently, it will happen within minutes after booting up; other times
it seems to happen at times of high load / memory usage. Sometimes the
system remains working for hours, sometimes just for minutes.

The problem occurs both with the xserver-xorg-video-ati and fglrx
drivers from the standard repositories (+ backports, + updates, +
security).

The system remains fully responsive via SSH, with seemingly no dangling
processes after stopping X.

Kernel 3.16.0-31-generic, amd64.
Release utopic.

Graphics card:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device 21f6
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at e000 (64-bit, prefetchable) [size=256M]
Memory at fbcc (64-bit, non-prefetchable) [size=128K]
I/O ports at de00 [size=256]
[virtual] Expansion ROM at fbc0 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
?
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-core 2:1.16.0-1ubuntu1.3
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Date: Fri Mar  6 10:38:17 2015
ExecutablePath: /usr/bin/Xorg
ProcEnviron:
 
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

** Attachment added: Xorg.1.log
   https://bugs.launchpad.net/bugs/1429390/+attachment/4337070/+files/Xorg.1.log

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

Title:
  Xorg freezes irrecoverably with EQ overflowing

Status in xorg-server package in Ubuntu:
  New

Bug description:
  X frequently freezes with EQ overflowing message(s) in the logs.
  lightdm/X can be stopped and restarted, but never returns to a usable
  state until rebooting. Either the screen remains black, or the input
  devices remain frozen.

  This happens multiple times a day but can not be reliably reproduced.
  Frequently, it will happen within minutes after booting up; other
  times it seems to happen at times of high load / memory usage.
  Sometimes the system remains working for hours, sometimes just for
  minutes.

  The problem occurs both with the xserver-xorg-video-ati and fglrx
  drivers from the standard repositories (+ backports, + updates, +
  security).

  The system remains fully responsive via SSH, with seemingly no
  dangling processes after stopping X.

  Kernel 3.16.0-31-generic, amd64.
  Release utopic.

  Graphics card:

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Device 21f6
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e000 (64-bit, prefetchable) [size=256M]
  Memory at fbcc (64-bit, non-prefetchable) [size=128K]
  I/O ports at de00 [size=256]
  [virtual] Expansion ROM at fbc0 [disabled] [size=128K]
  Capabilities: [50] Power Management version 3
  Capabilities: [58] Express Legacy Endpoint, MSI 00
  Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 
Len=010 ?
  Capabilities: [150] Advanced Error Reporting
  Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Fri Mar  6 10:38:17 2015
  ExecutablePath: /usr/bin/Xorg
  ProcEnviron:
   
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

[Niels Mayer]

To Thomas (camminady-thomas): just make sure not to upgrade recent upgrade 
packages: xserver-common xserver-xorg-core which would overwrite the patched 
packages.
Fortunately I noticed this would happen before I upgraded and intervened.

TBD: see if my instructions at #201 apply to the version-number
presented in the new security patch for the X server.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

[Niels Mayer]

Nikhil (nmahale) -- thanks for your patch. In
https://bugs.launchpad.net/ubuntu/+source/nvidia-
prime/+bug/1220426/comments/201 I believed it worked, now I'm certain it
fixes the freezing problem.

However, like 'sgustafso', I too noticed the eventual disappearance two-
finger scrolling.  I'm now testing edge scrolling setting from Unity
Tweak Tool,  which perhaps generates fewer events (?).

Also, curious as to the role of smartscroll, which is on by default:
smartscroll:Logitech Smartscroll autorepeat, 1 = enabled (default), 0 = 
disabled. (bool)

root@gnuvelle:/sys/module/psmouse/parameters# ls
proto  rate  resetafter  resolution  resync_time  smartscroll
root@gnuvelle:/sys/module/psmouse/parameters# cat *
auto
100
5
200
0
Y

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Confirmed
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-343” package in Ubuntu:
  Invalid
Status in “nvidia-prime” package in Ubuntu:
  Invalid

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

[Niels Mayer]

No arguing or instigating from me, just thanking, because perhaps this
patch is working. The only part not explained is that you don't need to
apply the resultant .deb files which aren't part of the current Xorg
install. In my case, 14.04LTS, only needed  sudo dpkg -i ./xserver-
common_1.15.1-0ubuntu2.3_all.deb ./xserver-xorg-
core_1.15.1-0ubuntu2.3_amd64.deb 

after doing:

xorg-server (2:1.15.1-0ubuntu2.3) UNRELEASED; urgency=medium

  * Patched per Balazs Scheidler (bazsi) https://bugs.launchpad.net/bugs/1220426
- Layman terms (on trusty): Download patch from the bugzilla and place
it in a file, let's say foo.diff
- $ apt-get build-dep xorg-server
- $ apt-get source xorg-server
- $ cd xorg-server-1.15.1
- $ patch -p1  ../foo.diff
- $ fakeroot debian/rules binary
- This should eventually build a couple of .deb packages with the
patch incorporated. It is running for me just now. So no news if
it worked or not.
- Also, it might make sense to modify debian/changelog and add your
own version to make it possible to see the change by judging the
version number. (e.g. debchange -i, edit and save)

 -- Niels P. Mayer npm@gnuvelle  Mon, 17 Nov 2014 14:56:45 -0800


npm@gnuvelle:~/Downloads$ sudo apt-get build-dep xorg-server
...
npm@gnuvelle:~/Downloads$ cd xorg-server-1.15.1/
npm@gnuvelle:~/Downloads/xorg-server-1.15.1$ patch -p1  
../nvidia-psmouse.patch 
patching file os/WaitFor.c
npm@gnuvelle:~/Downloads/xorg-server-1.15.1$ fakeroot debian/rules binary
...
npm@gnuvelle:~/Downloads$ ll *.deb
-rw-r--r-- 1 npm npm  823370 Nov 17 15:09 xdmx_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm  138496 Nov 17 15:09 xdmx-tools_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm  683040 Nov 17 15:09 xnest_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm 6128668 Nov 17 15:09 
xorg-server-source_1.15.1-0ubuntu2.3_all.deb
-rw-r--r-- 1 npm npm 1645058 Nov 17 15:08 
xserver-common_1.15.1-0ubuntu2.3_all.deb
-rw-r--r-- 1 npm npm  896566 Nov 17 15:09 
xserver-xephyr_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm 1312066 Nov 17 15:09 
xserver-xorg-core_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm 3874916 Nov 17 15:09 
xserver-xorg-core-dbg_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm  289522 Nov 17 15:09 
xserver-xorg-dev_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm  104410 Nov 17 15:09 
xserver-xorg-xmir_1.15.1-0ubuntu2.3_amd64.deb
-rw-r--r-- 1 npm npm  827668 Nov 17 15:09 xvfb_1.15.1-0ubuntu2.3_amd64.deb

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Confirmed
Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-343” package in Ubuntu:
  Invalid
Status in “nvidia-prime” package in Ubuntu:
  Invalid

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 336761] Re: gvfs-fuse: not able to set smb timestamps

[Niels van Adrichem]

I can confirm that this bug also appears when connecting to a Windows
file server. However, in retrospect to #9, at file copy no error is
thrown, but it silently overrides the alteration and created timestamps
with the current time as in #5.

The problem perseveres both with
$gvfs-copy --preserve Test.txt smb://server/share/folderX/Y/Z/.
and
$cp --preserve=timestamp Test.txt 
/run/user/1000/gvfs/smb-share\:server\,share\=share/folderX/Y/Z/

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

Title:
  gvfs-fuse: not able to set smb timestamps

Status in GVFS:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Triaged
Status in “gvfs” package in Fedora:
  Unknown
Status in “gvfs” package in openSUSE:
  Confirmed

Bug description:
  Binary package hint: gvfs

  Apparently this bug was supposed to have been fixed as of gvfs 1.1.1.
  As of 1.1.6-0ubuntu2 on Jaunty I still see the issue.

  Steps
  1. Mount a remote smb fileshare
  2. In the terminal cd to the ~/.gvfs/path/to/mount
  3. touch -d some date foo

  Result:

  touch: settings times of `foo': Operation not supported

  
  Could this be some sort of configuration problem on the samba side, note 
copying files to the samba server works fine for keeping proper dates. This may 
be an Ubuntu specific issue, somehow(?), since upstream claims this issue was 
corrected in 1.1.1, or else upstream didn't actually fix the problem like they 
thought.

  Chris

  https://bugzilla.redhat.com/show_bug.cgi?id=479199#c28

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

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

[Desktop-packages] [Bug 1297459] [NEW] nm-applet crashed with SIGSEGV in mm_sim_get_identifier()

[Niels Baggesen]

Public bug reported:

During login

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: network-manager-gnome 0.9.8.8-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 25 19:44:31 2014
ExecutablePath: /usr/bin/nm-applet
InstallationDate: Installed on 2014-01-07 (77 days ago)
InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 
(20131016)
IpRoute:
 default via 62.107.63.254 dev wlan0  proto static 
 62.107.0.0/18 dev wlan0  proto kernel  scope link  src 62.107.28.21  metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=da_DK.UTF-8
 SHELL=/bin/false
RfKill: Error: [Errno 2] Ingen sådan fil eller filkatalog: 'rfkill'
SegvAnalysis:
 Segfault happened at: 0x7f41ce192f96 mm_sim_get_identifier+22:   cmp
%rax,(%rdx)
 PC (0x7f41ce192f96) ok
 source %rax ok
 destination (%rdx) (0x20002) not located in a known VMA region (needed 
writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 mm_sim_get_identifier () from /usr/lib/x86_64-linux-gnu/libmm-glib.so.0
 ?? ()
 g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsecret-1.so.0
 g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nm-applet crashed with SIGSEGV in mm_sim_get_identifier()
UpgradeStatus: Upgraded to trusty on 2014-03-07 (17 days ago)
UserGroups:
 
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 ttyACM1gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/2  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


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

** Information type changed from Private to Public

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

Title:
  nm-applet crashed with SIGSEGV in mm_sim_get_identifier()

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  During login

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar 25 19:44:31 2014
  ExecutablePath: /usr/bin/nm-applet
  InstallationDate: Installed on 2014-01-07 (77 days ago)
  InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 
(20131016)
  IpRoute:
   default via 62.107.63.254 dev wlan0  proto static 
   62.107.0.0/18 dev wlan0  proto kernel  scope link  src 62.107.28.21  metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  ProcCmdline: nm-applet
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=da_DK.UTF-8
   SHELL=/bin/false
  RfKill: Error: [Errno 2] Ingen sådan fil eller filkatalog: 'rfkill'
  SegvAnalysis:
   Segfault happened at: 0x7f41ce192f96 mm_sim_get_identifier+22: cmp
%rax,(%rdx)
   PC (0x7f41ce192f96) ok
   source %rax ok
   destination (%rdx) (0x20002) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   mm_sim_get_identifier () from /usr/lib/x86_64-linux-gnu/libmm-glib.so.0
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsecret-1.so.0
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: nm-applet crashed with SIGSEGV in mm_sim_get_identifier()
  UpgradeStatus: Upgraded to trusty on 2014-03-07 (17 days ago)
  UserGroups:
   
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyACM1gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   

[Desktop-packages] [Bug 1297597] [NEW] can not update ore upgrade to new ubuntu linix? ships:=))))))))?please help?sos new upgrades?

[niels suurbier]

Public bug reported:

apt-get update; apt-get install gdb apport bugs to updat?

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.32.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14
Uname: Linux 2.6.35-32-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 26 03:24:31 2014
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=nl_NL:en
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1675): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-power-manager:1585): Gtk-WARNING **: A floating object was finalized. 
This means that someone
 (nautilus:1683): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed

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


** Tags: amd64 apport-bug maverick

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

Title:
  can not update ore upgrade to new ubuntu linix?
  ships:=?please help?sos new upgrades?

Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  apt-get update; apt-get install gdb apport bugs to updat?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-terminal 2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14
  Uname: Linux 2.6.35-32-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Mar 26 03:24:31 2014
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=nl_NL:en
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1675): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-power-manager:1585): Gtk-WARNING **: A floating object was finalized. 
This means that someone
   (nautilus:1683): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed

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

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

[Desktop-packages] [Bug 1272731] Re: Typo in Exiv2 package (string 3033)

[Niels Kristian Bech Jensen]

Fix in upstream svn trunk.

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

Title:
  Typo in Exiv2 package (string 3033)

Status in “exiv2” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Colort temperature should be replaced by Color temperature

  Link:
  
https://translations.launchpad.net/ubuntu/trusty/+source/exiv2/+pots/exiv2/fr/3033/+translate

  Thanks

  Jean-Marc

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

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

[Desktop-packages] [Bug 1269629] [NEW] [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] regular timed dropouts /crackling sound

[Niels Albers]

Public bug reported:

Problem only existed after installing Ubuntu 13.10. Previous versions of
Ubuntu did not have any sound problems. The Sound has breaks in output
roughly every second, causing a crackle effect in sound output on both
channels.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nralbers   3498 F pulseaudio
 /dev/snd/controlC0:  nralbers   3498 F pulseaudio
Date: Wed Jan 15 23:49:08 2014
InstallationDate: Installed on 2014-01-13 (2 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Green Line Out, Rear
Symptom_Type: Underruns, dropouts, or crackling sound
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: P55 Pro/USB3
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.:bvrP1.30:bd10/14/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55Pro/USB3: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.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] regular
  timed dropouts /crackling sound

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Problem only existed after installing Ubuntu 13.10. Previous versions
  of Ubuntu did not have any sound problems. The Sound has breaks in
  output roughly every second, causing a crackle effect in sound output
  on both channels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nralbers   3498 F pulseaudio
   /dev/snd/controlC0:  nralbers   3498 F pulseaudio
  Date: Wed Jan 15 23:49:08 2014
  InstallationDate: Installed on 2014-01-13 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: P55 Pro/USB3
  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.:bvrP1.30:bd10/14/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55Pro/USB3: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/alsa-driver/+bug/1269629/+subscriptions

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

[Desktop-packages] [Bug 1269629] Re: [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] regular timed dropouts /crackling sound

[Niels Albers]

Disableling automute in the alsamixer removes the stutter

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

Title:
  [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] regular
  timed dropouts /crackling sound

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Problem only existed after installing Ubuntu 13.10. Previous versions
  of Ubuntu did not have any sound problems. The Sound has breaks in
  output roughly every second, causing a crackle effect in sound output
  on both channels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nralbers   3498 F pulseaudio
   /dev/snd/controlC0:  nralbers   3498 F pulseaudio
  Date: Wed Jan 15 23:49:08 2014
  InstallationDate: Installed on 2014-01-13 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: P55 Pro/USB3
  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.:bvrP1.30:bd10/14/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55Pro/USB3: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/alsa-driver/+bug/1269629/+subscriptions

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

[Desktop-packages] [Bug 1242918] Re: Writing metadata is not supported for CR2

[Niels Kristian Bech Jensen]

You must update to at least exiv2-0.23 to get write support for CR2
files.

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

Title:
  Writing metadata is not supported for CR2

Status in “exiv2” package in Ubuntu:
  New

Bug description:
  I tried to write metadata to RAW CR2 files in digikam, but without
  success (it worked for JPG).

  When I started digikam from console I got the following:
  digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2ExceptionError: 
Cannot find Xmp key 'Xmp.mwg-rs.Regions/mwg-rs:RegionList[0]/mwg-rs:Name' into 
image using Exiv2 (Error # 35 : No namespace info available for XMP prefix 
`mwg-rs' digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::getXmpTagStringSeq: XMP 
String Seq ( Xmp.digiKam.TagsList ): (Betti, Próba) digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::setIptcKeywords: /home/kisben/Képek/új/IMG_2590.CR2 == 
Iptc Keywords: Betti,Emberek,Próba digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: KExiv2::metadataWritingMode 0 digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: Will write Metadata to file IMG_2590.CR2 
digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: Writing 
metadata is not supported for file IMG_2590.CR2 digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: Metadata for file IMG_2590.CR2 written to file.

  NOTE:
  I already reported the problem to digikam 
(https://bugs.kde.org/show_bug.cgi?id=326408), but they closed as the problem 
is in libexiv2.

  If this is not the right place to report, pls write me where I can
  report the problem.

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

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

[Desktop-packages] [Bug 1077741] Re: driver does not load, undefined symbol NEO_Sync

[Niels Elgaard Larsen]

bug still present in lubuntu 13.10

I could not get the pathces to work

But the git source (version 1.2.8 master commit 
a559a07989265a84ee31530a2b002899b40389ae)
work fine.

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

Title:
  driver does not load, undefined symbol NEO_Sync

Status in “xserver-xorg-video-neomagic” package in Ubuntu:
  Confirmed

Bug description:
  As a result the server starts with vesa driver that has a lot of
  graphical glitches

  Also my card has 2MB(!) of video memory that makes useful to force
  depth at 16bit in order to reach full screen 1024x768 otherwise it
  starts at 24 bit 800x600

  This is feasible also with vesa driver but graphic output is very bad
  quality

  A full discussion about this problem has already been made in gentoo:
  https://bugs.gentoo.org/show_bug.cgi?id=434468

  and a patch has been posted:
  http://lists.x.org/archives/xorg-devel/2012-September/033607.html

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-neomagic 1:1.2.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: 8192cu
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sun Nov 11 22:58:57 2012
  InstallationDate: Installed on 2001-03-24 (4250 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017)
  MarkForUpload: True
  SourcePackage: xserver-xorg-video-neomagic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-neomagic/+bug/1077741/+subscriptions

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

[Desktop-packages] [Bug 1122833] Re: Raw color setting produces semi-transparent TIFF with -h

[Niels Kristian Bech Jensen]

Have you reported it upstream to Dave Coffin?

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

Title:
  Raw color setting produces semi-transparent TIFF with -h

Status in “dcraw” package in Ubuntu:
  New

Bug description:
  dcraw -T -h -o 0 DSC06156.ARW

  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of

  dcraw -T -o 0 DSC06156.ARW

  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
  affected, but it doesn't support my camera really.

  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

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

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

[Desktop-packages] [Bug 1063795] Re: nautilus conflict with svn

[Niels Clemmensen]

** Changed in: nautilus (Ubuntu)
   Status: New = Fix Released

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

Title:
  nautilus conflict with svn

Status in “nautilus” package in Ubuntu:
  Fix Released

Bug description:
  Nautilus (1:3.6.0-0ubuntu1~ubuntu12.10.1(quantal)) don't work when
  there is a directory or subdirectory making by svn (subversion
  1.7.5-1ubuntu2(quantal)). Nautilus is not responding and the harddisk
  is running until you kill it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.27
  ProcVersionSignature: hostname 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niels  4771 F pulseaudio
   /dev/snd/controlC0:  niels  4771 F pulseaudio
  CRDA: Error: [Errno 2] Ingen sådan fil eller filkatalog: 'iw'
  CurrentDmesg:
   [  124.001859] r8169 :06:00.0: eth0: link down
   [  124.002581] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [  124.947970] NVRM: GPU at :01:00: 
GPU-fc7df0b8-e727-40b7-ca7d-dc8c6a3368c6
   [  125.696217] r8169 :06:00.0: eth0: link up
   [  125.696898] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Mon Oct  8 15:39:53 2012
  HibernationDevice: RESUME=UUID=ca183bd0-69b7-45f6-b657-4fe2814a04f2
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 
(20120327.1)
  MachineType: Hewlett-Packard HPE-530sc
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=40be4265-7d6e-4734-9b7d-2367c5801a0c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-09-11 (27 days ago)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.13
  dmi.board.name: 2AB6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: CZC12165V4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.13:bd05/04/2011:svnHewlett-Packard:pnHPE-530sc:pvr1.04:rvnPEGATRONCORPORATION:rn2AB6:rvr1.04:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HPE-530sc
  dmi.product.version: 1.04
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 916466] [NEW] package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Niels Smeulders]

Public bug reported:

not opening files or the main program, running 12.04.

lsb_release -rd

Description:Ubuntu precise (development branch)
Release:12.04


installArchives() failed: (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 146899 files and directories currently installed.)
Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using 
.../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ...
rmdir: kan usr/lib/libreoffice/basis3.4/program/ niet verwijderen: Map is niet 
leeg
dpkg: error processing 
/var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb 
(--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb
Error in function: 
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libreoffice-math:
 libreoffice-math depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-math (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-impress:
 libreoffice-impress depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-impress (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-writer:
 libreoffice-writer depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-writer (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-base-core:
 libreoffice-base-core depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-base-core (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-filter-binfilter:
 libreoffice-filter-binfilter depends on libreoffice-core (= 
1:3.5.0~beta2-2ubuntu2); however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-filter-binfilter (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-gnome:
 libreoffice-gnome depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-gnome (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-gtk:
 libreoffice-gtk depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-gtk (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python-uno:
 python-uno depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing python-uno (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-draw:
 libreoffice-draw depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
dpkg: error processing libreoffice-draw (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-help-en-us:
 libreoffice-help-en-us depends on libreoffice-writer | 
language-support-translations-en; however:
  Package libreoffice-writer is not configured yet.
  Package language-support-translations-en is not installed.
dpkg: error processing libreoffice-help-en-us (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libreoffice-calc:
 libreoffice-calc depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
 libreoffice-calc depends on libreoffice-base-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
  Package 

[Desktop-packages] [Bug 916466] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Niels Smeulders]

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

Title:
  package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  not opening files or the main program, running 12.04.

  lsb_release -rd

  Description:  Ubuntu precise (development branch)
  Release:  12.04


  installArchives() failed: (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%
  (Reading database ... 15%
  (Reading database ... 20%
  (Reading database ... 25%
  (Reading database ... 30%
  (Reading database ... 35%
  (Reading database ... 40%
  (Reading database ... 45%
  (Reading database ... 50%
  (Reading database ... 55%
  (Reading database ... 60%
  (Reading database ... 65%
  (Reading database ... 70%
  (Reading database ... 75%
  (Reading database ... 80%
  (Reading database ... 85%
  (Reading database ... 90%
  (Reading database ... 95%
  (Reading database ... 100%
  (Reading database ... 146899 files and directories currently installed.)
  Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using 
.../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ...
  rmdir: kan usr/lib/libreoffice/basis3.4/program/ niet verwijderen: Map is 
niet leeg
  dpkg: error processing 
/var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb
  Error in function: 
  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
  dpkg: dependency problems prevent configuration of libreoffice-math:
   libreoffice-math depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-math (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-impress:
   libreoffice-impress depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-impress (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-writer:
   libreoffice-writer depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-writer (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-base-core:
   libreoffice-base-core depends on libreoffice-core (= 
1:3.5.0~beta2-2ubuntu2); however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-base-core (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
libreoffice-filter-binfilter:
   libreoffice-filter-binfilter depends on libreoffice-core (= 
1:3.5.0~beta2-2ubuntu2); however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-filter-binfilter (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-gnome:
   libreoffice-gnome depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-gnome (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-gtk:
   libreoffice-gtk depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-gtk (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of python-uno:
   python-uno depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing python-uno (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-draw:
   libreoffice-draw depends on libreoffice-core (= 1:3.5.0~beta2-2ubuntu2); 
however:
Version of libreoffice-core on system is 1:3.4.4-0ubuntu2.
  dpkg: error processing libreoffice-draw (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libreoffice-help-en-us:
   libreoffice-help-en-us depends on libreoffice-writer | 
language-support-translations-en; however:
Package