[Desktop-packages] [Bug 2081384] [NEW] bluetooth headphones need reconnect after every reboot

[Tobias Heider]

Public bug reported:

This issue seems to be caused by a recent package update in oracular.
Every time I reboot my desktop my bluetooth headset will fail to connect
until I manually go through forget device -> new pairing.

journalctl says:

23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice 
gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice 
gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:14:00 desktop bluetoothd[3274]: No matching connection for device
23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get 
Hands-Free Voice gateway SDP record: Operation already in progress
23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice 
gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
23:15:46 desktop bluetoothd[3274]: 
/org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready

In dmesg I see lots of:
[44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837

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

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

** Affects: bluez (Ubuntu Oracular)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Oracular)
 Importance: Undecided
 Status: New

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

** Also affects: linux (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Oracular)
   Importance: Undecided
   Status: New

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

Title:
  bluetooth headphones need reconnect after every reboot

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in bluez source package in Oracular:
  New
Status in linux source package in Oracular:
  New

Bug description:
  This issue seems to be caused by a recent package update in oracular.
  Every time I reboot my desktop my bluetooth headset will fail to
  connect until I manually go through forget device -> new pairing.

  journalctl says:

  23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:00 desktop bluetoothd[3274]: No matching connection for device
  23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get 
Hands-Free Voice gateway SDP record: Operation already in progress
  23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:15:46 desktop bluetoothd[3274]: 
/org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready

  In dmesg I see lots of:
  [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837
  [44749.325565]

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

> Was it it more than a red line in systemctl status output? Does it
have annoying logging behaviour or break some other service if it isn't
running?

Red lines and an avoidable boot delay while trying to restart and
failing a bunch of times.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

I don't think that's enough since it also gets pulled in by ubuntu-
desktop and ubuntu-desktop-minimal as recommends. It would also be nice
if we found a solution that fixes the issue on existing installations
since upgrades from mantic to noble will trigger the bug.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

Looking at the diff between mantic and noble I think the regression was
cause by a change to pd-mapper.service.in for
https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

Can confirm that this is was a major annoyance on my m2 air after
upgrading to noble. it seems like this worked better in previous
releases. Looking at my logs it seems like it was already installed on
mantic but didn't cause startup problems. I think it gets pulled in by
being in Recommends for ubuntu-desktop.

I'm all for making it device specific instead. IMO there is no point in
having it installed on non Qualcomm devices.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 1861609] Re: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]

[Tobias Bühlmann]

I have the same issue on Ubuntu 23.10 using VirtualBox 7.0.14 when using
i3. It doesn't occur when logging in using Ubuntu (Gnome).

The issue doesn't occur when enabling 3D Acceleration in VirtualBox (but
it slows down everything a lot).

Can also confirm uninstalling libva-wayland2 helps.

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

Title:
  Xorg crashed with assertion failure (usually in a VM) at
  [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized'
  failed]

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

Bug description:
  Xorg crashed with assertion failure (usually in a VM):

  privates.h:121: dixGetPrivateAddr: Assertion `key->initialized'
  failed.

  WORKAROUND

  Select 'Ubuntu on Wayland' on the login screen.

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


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

[Desktop-packages] [Bug 2027656] Re: blank screen after mutter update

[Tobias]

At least one more colleague in my company just experienced the same
issue after upgrading.

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

Title:
  blank screen after mutter update

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  running on Ubuntu 22.04.2 LTS.

  I upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and suddenly
  experienced the problem described here:

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966808
  black screen and logs like in #2 of above post.

  My own Logs:

  Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
  Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument

  
  After some investigation and finally finding the bug above here adding
  MUTTER_DEBUG_USE_KMS_MODIFIERS=0
  to
  /etc/environment

  fixed it for me. Disabling wayland via /etc/gdm3/custom.conf worked as
  a workaround, too.

  Output of drm_info is attached.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.9-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:09:58 2023
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-11-23 (231 days ago)

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


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

[Desktop-packages] [Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv

[Tobias]

Hey Daniel,

new bug opened:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656

thanks

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

Title:
  [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon
  systems (Failed to lock front buffer on /dev/dri/cardN:
  drmModeAddFB2WithModifiers failed: Invalid argument)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  WORKAROUND:

  Add this to /etc/environment:  MUTTER_DEBUG_USE_KMS_MODIFIERS=0

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2027656] [NEW] blank screen after mutter update

[Tobias]

Public bug reported:

Hey,

running on Ubuntu 22.04.2 LTS.

I upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and suddenly
experienced the problem described here:

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966808
black screen and logs like in #2 of above post.

My own Logs:

Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument


After some investigation and finally finding the bug above here adding
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
to
/etc/environment

fixed it for me. Disabling wayland via /etc/gdm3/custom.conf worked as a
workaround, too.

Output of drm_info is attached.
thanks

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42.9-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 13 09:09:58 2023
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-11-23 (231 days ago)

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


** Tags: amd64 apport-bug jammy regression-update wayland-session

** Attachment added: "drm_info.txt"
   
https://bugs.launchpad.net/bugs/2027656/+attachment/5685973/+files/drm_info.txt

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

Title:
  blank screen after mutter update

Status in mutter package in Ubuntu:
  New

Bug description:
  Hey,

  running on Ubuntu 22.04.2 LTS.

  I upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and suddenly
  experienced the problem described here:

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966808
  black screen and logs like in #2 of above post.

  My own Logs:

  Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
  Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on 
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument

  
  After some investigation and finally finding the bug above here adding
  MUTTER_DEBUG_USE_KMS_MODIFIERS=0
  to
  /etc/environment

  fixed it for me. Disabling wayland via /etc/gdm3/custom.conf worked as
  a workaround, too.

  Output of drm_info is attached.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.9-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:09:58 2023
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-11-23 (231 days ago)

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


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

[Desktop-packages] [Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv

[Tobias]

Yesterday i upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and
suddenly experienced the problem described in this thread. (black screen
and logs like in #2)

After some investigation and finally finding this bug here adding
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
to
/etc/environment

fixed it for me, too.
Seems like the bug was brought back somehow?

Thanks
Tobias

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

Title:
  [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon
  systems (Failed to lock front buffer on /dev/dri/cardN:
  drmModeAddFB2WithModifiers failed: Invalid argument)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  WORKAROUND:

  Add this to /etc/environment:  MUTTER_DEBUG_USE_KMS_MODIFIERS=0

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987631] Re: Screencast only records one second

[Tobias Heider]

Deleting .cache/gstreamer-1.0 doesn't change anything. The bug you mention also 
seems to be a different one because I get a video, it is just very choppy.
The upstream bug fix i shared also doesn't seem to help.

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

Title:
  Screencast only records one second

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

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

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


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

[Desktop-packages] [Bug 1987631] Re: Screencast only records one second

[Tobias Heider]

Look like a temporary fix for the bug landed in upstream with
https://gitlab.gnome.org/skeller/gnome-
shell/-/commit/398b1c6c79da0bb0630ab7448cd227d85c3985eb#249ab328def8cba907309a9d7c0ddf940776c578.
I will test if this also fixes the bug for me.

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

Title:
  Screencast only records one second

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

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

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


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

[Desktop-packages] [Bug 1987631] [NEW] Screencast only records one second

[Tobias Heider]

Public bug reported:

When recording a screencast with gnome on kinetic the resulting video
will play for one second and then freeze. It looks like the same bug was
discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/5585

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

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

Title:
  Screencast only records one second

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

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


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

[Desktop-packages] [Bug 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks

[Tobias Heider]

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  [REGRESSION] Unable to connect to EAP-TLS networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 22.04, currently with network-manager
  1.36.4-2ubuntu1

  Attempting to connect to an EAP-TLS network fails with:

  NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): 
Activation: (wifi) connection 'AP' has security, and secrets exist.  No new 
secrets needed.
  NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
  NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' 
value '1'
  NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
  NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
  NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
  NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
  NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
  NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
  NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
  NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
  NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
  NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
  NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')

  
  Caused by NM providing an empty domain_suffix_match option

  Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
  Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

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


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

[Desktop-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

[Tobias Grundmann]

after enabling fractional scaling you can even disable it again after plugging 
in the hub/second monitor (useful because it's blurry).
So my workaround looks like this:
boot -> freeze -> unplug hub -> enable fractional scaling -> plug hub in again 
-> disable fractional scaling -> adjust display arrangement -> work

additional observation: when the displays freeze the taskbar is cut off
halfway, like it wouldn't fit completely on the screen.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

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

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

[Tobias Grundmann]

boot log

** Attachment added: "boot.txt.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970043/+attachment/5585327/+files/boot.txt.gz

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

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

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

[Tobias Grundmann]

same problem here.
Dell XPS13, intel graphics,
second monitor connected via USB-C Hub. Mouse connected to same hub can be 
moved for halve a second after plugging in the hub, then everything freezes. 
X11 works.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

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

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1958538] Re: Extreme Screen flickering when setting a non-native resolution

[Tobias Bossert]

** Summary changed:

- Extreme Screen flickering when non native resolution
+ Extreme Screen flickering when setting a non-native resolution

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

Title:
  Extreme Screen flickering when setting a non-native resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  As soon I set the screen resolution to non native (4k laptop display)
  the screen begins to flicker and horizontal/vertical lines appear.
  (See attached image) Interestingly this happens only to the internal
  screen, external monitors work fine.

  Also during boot (supposedly when the display driver is loaded) severe
  tearing is visible for brief moment.

  An issue with the screen itself can be ruled out since there are no
  issues when running ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Thu Jan 20 15:14:11 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Cezanne [17aa:5094]
  InstallationDate: Installed on 2022-01-03 (16 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XLS0CJ00
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic 
root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET41W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XLS0CJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a:
  dmi.product.family: ThinkPad T14 Gen 2a
  dmi.product.name: 20XLS0CJ00
  dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a
  dmi.product.version: ThinkPad T14 Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1958538] [NEW] Extreme Screen flickering when non native resolution

[Tobias Bossert]

Public bug reported:

As soon I set the screen resolution to non native (4k laptop display)
the screen begins to flicker and horizontal/vertical lines appear. (See
attached image) Interestingly this happens only to the internal screen,
external monitors work fine.

Also during boot (supposedly when the display driver is loaded) severe
tearing is visible for brief moment.

An issue with the screen itself can be ruled out since there are no
issues when running ubuntu 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Thu Jan 20 15:14:11 2022
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Cezanne [17aa:5094]
InstallationDate: Installed on 2022-01-03 (16 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20XLS0CJ00
ProcEnviron:
 LANGUAGE=de_CH:de
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic 
root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET41W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XLS0CJ00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a:
dmi.product.family: ThinkPad T14 Gen 2a
dmi.product.name: 20XLS0CJ00
dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a
dmi.product.version: ThinkPad T14 Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug corruption impish ubuntu

** Attachment added: "resized.jpg"
   
https://bugs.launchpad.net/bugs/1958538/+attachment/837/+files/resized.jpg

** Description changed:

  As soon I set the screen resolution to non native (4k laptop display)
- the screen begins to flicker and horizontal/vertical lines appear.
- Interestingly this happens only to the internal screen, external
- monitors work fine.
+ the screen begins to flicker and horizontal/vertical lines appear. (See
+ attached image) Interestingly this happens only to the internal screen,
+ external monitors work fine.
  
  Also during boot (supposedly when the display driver is loaded) severer
  tearing is visible for brief moment.
  
  An issue with the screen itself can be ruled out since there are no
  issues when running ubuntu 20.04.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Thu Jan 20 15:14:11 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
-Subsystem: Lenovo Cezanne [17aa:5094]
+  Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
+    Subsystem: Lenovo Cezanne [17aa:5094]
  InstallationDate: Installed on 2022-01-03 (16 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XLS0CJ00
  ProcEnviron:
-  LANGUAGE=de_CH:de
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=de_CH.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=de_CH:de
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_CH.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic 

[Desktop-packages] [Bug 1931388] Re: Firefox disaplayerror after Update on last version 89

[Tobias Schimpf]

Hello Olivier,

thanks for your reply and yes I can reproduce the bug. Bevore I
reinstalled it I removed all Preferences.

Now I ran the Command above and got a Mail with this report

A new OAuth token consumer was enabled in Launchpad.

If you did not make this change, please open a new Question on Launchpad
 or visit
#launchpad on IRC at irc.libera.chat to alert staff of the issue.

I hope this helps to find the Issue

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

Title:
  Firefox disaplayerror after Update on last version 89

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After the last Update from Firefox Browser to Version 89 Firefox is unsuable. 
The Program starts but the window is somehow transparent and white. I removed 
and reinstalled Firefox but the problem is the same. My computer is an Amd 
Mashine running Ubuntu Mate 20.10 Mate 1.24.1
  I took a Screenshot.

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

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

[Desktop-packages] [Bug 1928791] Re: gnome-shell runs on 60--100% CPU usage

[Tobias Reich]

hi, thanks for caring,
re 1. yeah, that's right, I got only the 3 default extensions installed
re 2. and 3. I think I cannot do this anymore, cuz the problem suddenly 
disappeared when I reset the "Tweaks" setting to default. So, I reckon, it got 
something to do with "unlucky" and/or compromised Tweak settings, but I can't 
tell with ones. I set them back to the setting I *think* I've had before. but 
the gnome-shell process(es) stay(s) relatively cool, now.

and yes, I got animated indicators in my panel like indicator-multiload and 
clock seconds, however this was only a small percentage in difference. The 
seconds make up almost no difference at all, and when starting 
indicator-multiload, now, the gnome-shell only reaches like 25% CPU usage 
instead of 60-100% without indicator-multiload (prior to resetting the Tweak 
settings to default).
And I don't think it has to do with my Firefox browser or Thunderbird mail 
client, cause also now when open all of them even with multi Firefox instances 
(profiles) and Discord, MS Teams. Telegram, Nextcloud client any many more the 
gnome-shell still stays absolutely cool:

top - 10:13:50 up  1:02,  1 user,  load average: 2,16, 2,17, 1,59
Tasks: 377 total,   4 running, 373 sleeping,   0 stopped,   0 zombie
%Cpu(s): 31,3 us,  1,8 sy,  0,0 ni, 65,3 id,  0,1 wa,  0,0 hi,  1,5 si,  0,0 st
MiB Mem :   7960,7 total,402,0 free,   5835,6 used,   1723,0 buff/cache
MiB Swap:  26058,0 total,  25075,5 free,982,5 used.   1147,8 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  
    
  12683 tobias20   0 2653208 300408 224756 R 108,6   3,7  12:59.40 Web 
Content      
   8685 tobias20   0 3916848 629076 301284 S  38,1   7,7   6:35.34 firefox  

   2982 root  20   0  604680 339056 319360 R  27,2   4,2   8:05.53 Xorg 
    
   3216 tobias20   0 5564976 892044  80780 S   9,9  10,9   7:16.01 
gnome-shell      
   9149 tobias20   0 4257832 518540 123472 S   3,3   6,4   2:01.05 
thunderbird      
  10894 tobias20   0 4063956  48868  19612 S   2,3   0,6   0:05.50 teams

   2983 root -51   0   0  0  0 S   2,0   0,0   0:55.11 
irq/35-nvidia
808 root  20   0   0  0  0 S   1,7   0,0   0:53.74 
nvidia-modeset/      
  10486 tobias20   0   21,0g 159864  46864 S   1,7   2,0   0:43.80 Discord  
    
  12272 tobias20   0  818300  51952  35748 S   1,7   0,6   0:11.74 
gnome-terminal-      
  10210 tobias20   0 4928588  62172  20264 S   1,3   0,8   0:24.89 Discord  

386 root  19  -1  127172  63600  62776 S   0,7   0,8   0:06.07 
systemd-journal      
  10826 tobias20   0 2508384 352328  49164 S   0,7   4,3   1:15.08 teams

  13432 root  20   0   0  0  0 I   0,7   0,0   0:01.30 
kworker/4:0-events   
   1520 root  20   02548720668 S   0,3   0,0   0:17.57 acpid

   2985 root  20   0   0  0  0 S   0,3   0,0   0:06.63 nv_queue 
    
   3149 tobias 9 -11 4366744  11612   8696 S   0,3   0,1   0:14.64 
pulseaudio   
   8646 tobias20   0 4177312 564096 253408 S   0,3   6,9   3:23.27 firefox  
    
   8858 tobias20   0   20,6g 285284 186692 S   0,3   3,5   1:02.59 Web 
Content      
   9072 tobias20   0   14,6g 259344  46428 S   0,3   3,2   0:32.74 
WebExtensions    
   9287 tobias20   0 3558884 212352  42240 S   0,3   2,6   0:28.64 teams

  12395 root  20   0   0  0  0 R   0,3   0,0   0:02.24 
kworker/3:1-events   
  13057 root  20   0   0  0  0 I   0,3   0,0   0:01.06 
kworker/2:1-events   
  13070 root  20   0   0  0

[Desktop-packages] [Bug 1928791] [NEW] gnome-shell runs on 60--100% CPU usage

[Tobias Reich]

Public bug reported:

from top output:

top - 14:18:02 up  5:45,  1 user,  load average: 1,55, 1,54, 1,77
Tasks: 419 total,   1 running, 418 sleeping,   0 stopped,   0 zombie
%Cpu(s): 13,2 us,  2,6 sy,  0,0 ni, 83,7 id,  0,1 wa,  0,0 hi,  0,4 si,  0,0 st
MiB Mem :   7960,7 total,233,0 free,   5719,6 used,   2008,1 buff/cache
MiB Swap:  26058,0 total,  23596,0 free,   2462,0 used.576,0 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  

 
  20866 tobias20   0 6652668 996,0m  83472 S  63,4  12,5  33:56.49 
gnome-shell 


this is so wrong… how to fix it?

best, Tobias

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 18 14:11:41 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-22 (300 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.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/1928791

Title:
  gnome-shell runs on 60--100% CPU usage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  from top output:

  top - 14:18:02 up  5:45,  1 user,  load average: 1,55, 1,54, 1,77
  Tasks: 419 total,   1 running, 418 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 13,2 us,  2,6 sy,  0,0 ni, 83,7 id,  0,1 wa,  0,0 hi,  0,4 si,  0,0 
st
  MiB Mem :   7960,7 total,233,0 free,   5719,6 used,   2008,1 buff/cache
  MiB Swap:  26058,0 total,  23596,0 free,   2462,0 used.576,0 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND 
  
20866 tobias20   0 6652668 996,0m  83472 S  63,4  12,5  33:56.49 
gnome-shell 


  this is so wrong… how to fix it?

  best, Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 18 14:11:41 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (300 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.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/1928791/+subscriptions

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

[Desktop-packages] [Bug 1902801] Re: Encrypted attachments cannot be opened or saved as decrypted files

[Tobias]

Hi, I've stumbled across this post here after I've searched for the
error message "rnp_op_verify_execute returned unexpected" on Google.

@yg-info I've tested the beta version "88.0b2" (simply downloading the
.tar.bz2 for Linux and executing the "thunderbird" binary) and it's now
working. The two emails, which can't be open by Thunderbird "78.9.1",
can be open with Thunderbird "88.0b2".

The first email has no attachments and the second email has one
attachment (simple csv file), which I can open.

I'm using (Manjaro Arch) Linux, Kernel 5.11.10-1-MANJARO, x64.

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Fix Released
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Tobias Pedersen]

I've managed to make the subwoofer work with some caveats, I've made a
short guide here:
https://gist.github.com/BXZ/48cd8173807676a1402cf4bc7928c0c0

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1908089] [NEW] gnome-shell-extension-multi-monitors crash on gnome shell 3.36.4

[Tobias Weiss]

Public bug reported:

I've installed gnome-shell-extension-multi-monitors 19-1 on ubuntu 20.04
and running gnome-shell 3.36.4:

The extension is available within gnome-tweaks and can be enabled. But
when logging in it crashes: gnome-tweaks shows "Error loading extension"
and the following error shows up in the syslog:

Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS WARNING: 
[/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js 
402]: reference to undefined property "_onButtonPress"
Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS ERROR: Extension 
multi-monitors-add-on@spin83: TypeError: this._onButtonPress is 
undefined#012_init@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js:402:4#012_pushPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:220:15#012_monitorsChanged@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:199:11#012showPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:87:10#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:209:24#012wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:331:21#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:349:26#012_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:18#012collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17#012_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:574:19#012_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:608:18#012_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:639:18#012init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14#012_initializeUI@resource:///org/gnome/shell/ui/main.js:257:22#012start@resource:///org/gnome/shell/ui/main.js:146:5#012@:1:47


I've checked https://extensions.gnome.org/extension/921/multi-monitors-add-on/ 
and it seems that the version 19 of the extension is not compatible with 
3.36.4. It seems like you need at least version 20 of 
gnome-shell-extension-multi-monitors. So I guess an update is necessary...

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

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

Title:
  gnome-shell-extension-multi-monitors crash on gnome shell 3.36.4

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I've installed gnome-shell-extension-multi-monitors 19-1 on ubuntu
  20.04 and running gnome-shell 3.36.4:

  The extension is available within gnome-tweaks and can be enabled. But
  when logging in it crashes: gnome-tweaks shows "Error loading
  extension" and the following error shows up in the syslog:

  Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS WARNING: 
[/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js 
402]: reference to undefined property "_onButtonPress"
  Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS ERROR: Extension 
multi-monitors-add-on@spin83: TypeError: this._onButtonPress is 
undefined#012_init@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js:402:4#012_pushPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:220:15#012_monitorsChanged@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:199:11#012showPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:87:10#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:209:24#012wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:331:21#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:349:26#012_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:18#012collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17#012_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:574:19#012_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:608:18#012_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:639:18#012init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14#012_initializeUI@resource:///org/gnome/shell/ui/main.js:257:22#012start@resource:///org/gnome/shell/ui/main.js:146:5#012@:1:47

  
  I've checked 
https://extensions.gnome.org/extension/921/multi-monitors-add-on/ and it seems 
that the version 19 of the extension is not compatible with 3.36.4. It seems 
like you need at least version 20 of gnome-shell

[Desktop-packages] [Bug 1900716] Re: "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu 20.10

[Tobias]

As I've already mentioned, i did try with and without xserver-xorg-
input-synaptics installed. It is currently installed and the touchpad
still does not work.

Greetings
Tobi

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

Title:
  "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu
  20.10

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Laptop: Asus EeeBook X205TA
  Touchpad stopped working after the upgrade to Ubuntu 20.10

  I followed this guide
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  I tried to use the Touchpad with and without xserver-xorg-input-
  synaptics installed, neither works.

  External mouse is working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1900716/+subscriptions

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

[Desktop-packages] [Bug 1900716] [NEW] "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu 20.10

[Tobias]

Public bug reported:

Laptop: Asus EeeBook X205TA
Touchpad stopped working after the upgrade to Ubuntu 20.10

I followed this guide https://wiki.ubuntu.com/DebuggingTouchpadDetection

I tried to use the Touchpad with and without xserver-xorg-input-
synaptics installed, neither works.

External mouse is working fine.

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "sudo evtest /dev/input/event7 > ~/evtest"
   https://bugs.launchpad.net/bugs/1900716/+attachment/5424682/+files/evtest

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

Title:
  "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu
  20.10

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Laptop: Asus EeeBook X205TA
  Touchpad stopped working after the upgrade to Ubuntu 20.10

  I followed this guide
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  I tried to use the Touchpad with and without xserver-xorg-input-
  synaptics installed, neither works.

  External mouse is working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1900716/+subscriptions

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

[Desktop-packages] [Bug 1900716] Re: "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu 20.10

[Tobias]

** Attachment added: "Xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1900716/+attachment/5424683/+files/Xorg.0.log

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

Title:
  "Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu
  20.10

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Laptop: Asus EeeBook X205TA
  Touchpad stopped working after the upgrade to Ubuntu 20.10

  I followed this guide
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  I tried to use the Touchpad with and without xserver-xorg-input-
  synaptics installed, neither works.

  External mouse is working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1900716/+subscriptions

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

[Desktop-packages] [Bug 1869963] Re: Unable to install chromium-browser 20.04

[Tobias Krönke]

I agree this would just end up in messy workarounds. I see the main
culprit in the snap daemon. I don't see a chance, that Ubuntu will
switch back from snap to plain deb for this package because it fixes
only this 1 snap. A fundamental solution would be to make snaps work in
general for containerized applications. However, I have no clue, what
the daemon does and if it can be made optional for containers.

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

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

Title:
  Unable to install chromium-browser 20.04

Status in cloud-images:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

Bug description:
  Steps to reproduce: Create a docker container with the official image
  "ubuntu:focal". Inside of the container, run "apt-get install
  chromium-browser".

  Expected results: Chromium is installed.

  Actual results: Chromium installation fails. The error is telling me
  that it is unable to reach the snap store (probably because snapd is
  not running).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions

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

[Desktop-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Tobias Kuhn]

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

It doesn't seem to me that this is really a duplicate of bug #1849859.
At least the reported symptoms are not identical.

In any case, has anybody found a workaround for this?

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 837456] Re: XTestFakeKeyEvent changes keyboard mapping to 'us'

[Tobias Schlemmer]

I found this issue in the X.org bug tracker:

https://gitlab.freedesktop.org/xorg/xserver/issues/589

I think further discussion should go on, there.

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #589
   https://gitlab.freedesktop.org/xorg/xserver/issues/589

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

Title:
  XTestFakeKeyEvent changes keyboard mapping to 'us'

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Typing with the onscreen keyboard Onboard on a system with German
  default layout immediately switches the keyboard layout to 'English
  (US)'. Touching any key on a physical keyboard switches back to the
  German default. This can be repeated indefinitely.

  Onboard uses XTestFakeKeyEvent to send key events. When switching from
  a physical keyboard to Onboard, the first call to this function leads
  to an unwanted MappingNotify event and the keyboard map changes from
  'pc+de+inet(evdev)', 'German' to 'pc+us+inet(evdev)', 'English (US)'.
  Pressing any key on an attached USB keyboard switches back to
  'pc+de+inet(evdev)', 'German'.

  Running any of the following temporarily fixes  the problem for the current 
session:
  $ setxkbmap de
  $ sudo dpkg-reconfigure keyboard-configuration

  Restarting X brings back the unwanted layout switches.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Tue Aug 30 16:21:46 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. Device [105b:0df0]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110826)
  MachineType: OEM OEM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic 
root=UUID=3bee4cb7-392a-4347-a496-f32c7141e658 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: G31MG-S
  dmi.board.vendor: Foxconn
  dmi.board.version: FAB:1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/04/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MG-S:rvrFAB1.0:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1785063] Re: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

[Tobias Dæ]

Also affects me. I attached the alsa-info.txt created by Alsainfo:
https://wiki.ubuntu.com/Audio/AlsaInfo

** Attachment added: "alsa-info.txt.dbLPPYkDup"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1785063/+attachment/5257861/+files/alsa-info.txt.dbLPPYkDup

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

Title:
  [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound at all, through speakers or headphones jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  natty  4286 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug  2 15:07:12 2018
  InstallationDate: Installed on 2017-10-12 (293 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1248 F pulseaudio
natty  4286 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (120 days ago)
  dmi.bios.date: 06/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02HAC.004.170626.WY.1442
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W720NZKBBTU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8766A2S-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKBBTU:rvrSGL8766A2S-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 12
  dmi.product.version: P02HAC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-13T14:38:49.320280

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

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

[Desktop-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

[Tobias Hoffmann]

When pdftocairo ist used with libcairo2-1.15.12-1 -- which (AFAIK)
contains the bug I linked above -- to output a pdf file (as pdftopdf
1.21 will do!), it would be no surprise have a corrupt pdf after
pdftocairo, which gs then rightly will complain about; esp. the ET
-thing is the one things such a buggy libcairo2 will produce.

The only thing form-flattening has to do with it, is that pdftopdf 1.21
would only call pdftocairo when a form is present in the pdf.

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

Title:
  Unable to correctly print PDF file: Error: Ignoring spurious ET
  operator.

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Upstream bug report https://github.com/OpenPrinting/cups-
  filters/issues/93.

  The university document
  [antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
  filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
  different printers.

  Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
  is first printed, and on the first page after _Email_ everything is
  missing. The second page is fine.

  ```
    Error: Ignoring spurious ET operator. Output may be inco 
  ```

  For that printer a special filter `sicgsfilter` has to be used, and is
  distributed by Canon. This also happens with their CQue 4.0-1 release
  from September 2018.

  ```
   *FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C 
-dPDFFitPage  -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u&user; 
-V"&title;" -n&copies; "
  ```

  On the Epson printer _WorkForce WF-2660_, no error page is printed,
  but on the first page everything after _Email_ _is missing_ too.

  Trying to use different pdftops renderers did not make any difference.
  For example,

  ```
   lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
  ```

  gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

  Following `/usr/share/doc/cups-filters/README.gz` and
  https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
  exact same PDF is put into the CUPS spool directory, and I captured
  the data sent to the printer with the commands below.

  $ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P 
~/chipprinterpcl.ppd
  $ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

  I get the attached Postscript file, which indeed contains the error
  messages.

  ```
  ESC%-12345X@PJL CQue4.0-1 x86_64
  @PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
  @PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
  @PJL SET RENDERMODE=COLOR
  @PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
  @PJL COMMENT CANPJL SET SORTERMODE=GENERICON
  @PJL COMMENT CANPJL SET STAPLE=GENERICOFF
  @PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
  @PJL SET DENSITY=0
  @PJL ENTER LANGUAGE=PCL
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  […]
  ```

  Please find that file attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Thu Feb 21 10:23:08 2019
  InstallationDate: Installed on 2017-03-20 (702 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
   device for DCP375CW: socket://141.14.220.198
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Papersize: a4
  PpdFiles:
   Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
   DCP375CW: Brother 

[Desktop-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

[Tobias Hoffmann]

My observations:
As changing pdftops-renderer does not seem to make a difference, probably only 
one of the programs is installed and thus used in all cases?

According to Dependencies.txt, libcairo2-1.15.12-1 seems to installed, which 
AFAIK is affected by the problem described e.g. here: 
https://github.com/Kozea/WeasyPrint/issues/705
I have no explanation though, how the pdf (which, by itself, does not seem to 
contain the error, AFAIAC) would run through the cairo pdf backend ... 

It does not really seem form-related, but there are some options to change the 
form-flattening engines (Till?)
 - or could it possibly be that the 1.21 cups-filter uses some pdf-to-pdf form 
flattening which uses the cairo backend ?


** Bug watch added: github.com/Kozea/WeasyPrint/issues #705
   https://github.com/Kozea/WeasyPrint/issues/705

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

Title:
  Unable to correctly print PDF file: Error: Ignoring spurious ET
  operator.

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Upstream bug report https://github.com/OpenPrinting/cups-
  filters/issues/93.

  The university document
  [antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
  filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
  different printers.

  Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
  is first printed, and on the first page after _Email_ everything is
  missing. The second page is fine.

  ```
    Error: Ignoring spurious ET operator. Output may be inco 
  ```

  For that printer a special filter `sicgsfilter` has to be used, and is
  distributed by Canon. This also happens with their CQue 4.0-1 release
  from September 2018.

  ```
   *FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C 
-dPDFFitPage  -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u&user; 
-V"&title;" -n&copies; "
  ```

  On the Epson printer _WorkForce WF-2660_, no error page is printed,
  but on the first page everything after _Email_ _is missing_ too.

  Trying to use different pdftops renderers did not make any difference.
  For example,

  ```
   lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
  ```

  gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

  Following `/usr/share/doc/cups-filters/README.gz` and
  https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
  exact same PDF is put into the CUPS spool directory, and I captured
  the data sent to the printer with the commands below.

  $ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P 
~/chipprinterpcl.ppd
  $ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

  I get the attached Postscript file, which indeed contains the error
  messages.

  ```
  ESC%-12345X@PJL CQue4.0-1 x86_64
  @PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
  @PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
  @PJL SET RENDERMODE=COLOR
  @PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
  @PJL COMMENT CANPJL SET SORTERMODE=GENERICON
  @PJL COMMENT CANPJL SET STAPLE=GENERICOFF
  @PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
  @PJL SET DENSITY=0
  @PJL ENTER LANGUAGE=PCL
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  […]
  ```

  Please find that file attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Thu Feb 21 10:23:08 2019
  InstallationDate: Installed on 2017-03-20 (702 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
   device for DCP375CW: socket://141.14.220.198
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004:

[Desktop-packages] [Bug 1731628] Re: Cannot add caldav calendar

[Tobias Bannert]

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

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

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

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

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

Title:
  Cannot add caldav calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I try to add a caldav calendar

  calendars -> Add -> From Web ->
  https://posteo.de:8443/calendars/max.mustermann/default/

  and I hit enter but the "add" button in the right upper corner remains
  grayed out.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 14:47:03 2017
  InstallationDate: Installed on 2017-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1782951] [NEW] package policykit-1 0.105-20 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1

[tobias]

Public bug reported:

I am new to ubuntu so i have no idea whats going on

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: policykit-1 0.105-20
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jul 18 19:36:56 2018
DuplicateSignature:
 package:policykit-1:0.105-20
 Preparing to unpack .../policykit-1_0.105-20ubuntu0.18.04.1_amd64.deb ...
 Failed to get properties: Connection timed out
 dpkg: error processing archive 
/var/cache/apt/archives/policykit-1_0.105-20ubuntu0.18.04.1_amd64.deb 
(--unpack):
  new policykit-1 package pre-installation script subprocess returned error 
exit status 1
ErrorMessage: new policykit-1 package pre-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-07-16 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: policykit-1
Title: package policykit-1 0.105-20 failed to install/upgrade: new policykit-1 
package pre-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package policykit-1 0.105-20 failed to install/upgrade: new
  policykit-1 package pre-installation script subprocess returned error
  exit status 1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I am new to ubuntu so i have no idea whats going on

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: policykit-1 0.105-20
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jul 18 19:36:56 2018
  DuplicateSignature:
   package:policykit-1:0.105-20
   Preparing to unpack .../policykit-1_0.105-20ubuntu0.18.04.1_amd64.deb ...
   Failed to get properties: Connection timed out
   dpkg: error processing archive 
/var/cache/apt/archives/policykit-1_0.105-20ubuntu0.18.04.1_amd64.deb 
(--unpack):
new policykit-1 package pre-installation script subprocess returned error 
exit status 1
  ErrorMessage: new policykit-1 package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-07-16 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: policykit-1
  Title: package policykit-1 0.105-20 failed to install/upgrade: new 
policykit-1 package pre-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1781852] [NEW] package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

[Tobias Mikutta]

Public bug reported:

I don know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgconf-2-4:amd64 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jul 15 16:49:32 2018
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
InstallationDate: Installed on 2018-07-15 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, 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.2
SourcePackage: gconf
Title: package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in gconf package in Ubuntu:
  New

Bug description:
  I don know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgconf-2-4:amd64 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 15 16:49:32 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2018-07-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, 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.2
  SourcePackage: gconf
  Title: package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778143] Re: SIGSEV when turning on display while screensaver is active (gnome-screensaver-dialog crash)

[Tobias Knöppler]

Do you need any more information?

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

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

Title:
  SIGSEV when turning on display while screensaver is active (gnome-
  screensaver-dialog crash)

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Since the update to Ubuntu 18.04 (ubuntu budgie) the screensaver
  stopped working.

  Description of the error:

  When I lock the screen, the display turns black (as intended). However, when 
I press a key or move the mouse to turn the display again, no login-dialog is 
shown - instead I see the lockscreen wallpaper and the mouse cursor shows 
graphical glitches (becoming invisible and visible when moving it).
  I can unlock again by typing `gnome-screensaver-command -d` into a tty.

  I have found out, that the program 'gnome-screensaver-dialog' crashes
  with a SIGSEV and causes the described failure. Purging and
  reinstalling the package 'gnome-screensaver' did not help. Running
  'gnome-screensaver-dialog' with gdb generates the attached output
  (which is hopefully useful for tracking down the problem).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Jun 22 00:15:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-14 (127 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (53 days ago)

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

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

[Desktop-packages] [Bug 1779658] [NEW] Dropping to shell twice crashes system

[Tobias]

Public bug reported:

If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and 
repeat once more:
Expected result:
- Normal functioning X session
Real result:
- No interaction with the system possible anymore.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..25.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:25:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jul  2 13:24:01 2018
DistUpgraded: 2018-06-06 15:37:57,793 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050] [1458:3747]
InstallationDate: Installed on 2018-02-22 (129 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=6c4a23a4-85d5-4ec4-b6f1-cfececbb0353 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-06-06 (25 days ago)
dmi.bios.date: 09/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.90
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
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.:bvr1.90:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


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

Title:
  Dropping to shell twice crashes system

Status in xorg package in Ubuntu:
  New

Bug description:
  If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and 
repeat once more:
  Expected result:
  - Normal functioning X session
  Real result:
  - No interaction with the system possible anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..25.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:25:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PD

[Desktop-packages] [Bug 1778143] Re: SIGSEV when turning on display while screensaver is active (gnome-screensaver-dialog crash)

[Tobias Knöppler]

Thank you for the response. With debug symbols installed, gdb produces
the attached output.

** Attachment added: "gnome-screensaver-debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1778143/+attachment/5156561/+files/gnome-screensaver-debug.txt

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

Title:
  SIGSEV when turning on display while screensaver is active (gnome-
  screensaver-dialog crash)

Status in gnome-screensaver package in Ubuntu:
  Incomplete

Bug description:
  Since the update to Ubuntu 18.04 (ubuntu budgie) the screensaver
  stopped working.

  Description of the error:

  When I lock the screen, the display turns black (as intended). However, when 
I press a key or move the mouse to turn the display again, no login-dialog is 
shown - instead I see the lockscreen wallpaper and the mouse cursor shows 
graphical glitches (becoming invisible and visible when moving it).
  I can unlock again by typing `gnome-screensaver-command -d` into a tty.

  I have found out, that the program 'gnome-screensaver-dialog' crashes
  with a SIGSEV and causes the described failure. Purging and
  reinstalling the package 'gnome-screensaver' did not help. Running
  'gnome-screensaver-dialog' with gdb generates the attached output
  (which is hopefully useful for tracking down the problem).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Jun 22 00:15:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-14 (127 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (53 days ago)

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

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

[Desktop-packages] [Bug 1778143] [NEW] SIGSEV when turning on display while screensaver is active (gnome-screensaver-dialog crash)

[Tobias Knöppler]

Public bug reported:

Since the update to Ubuntu 18.04 (ubuntu budgie) the screensaver stopped
working.

Description of the error:

When I lock the screen, the display turns black (as intended). However, when I 
press a key or move the mouse to turn the display again, no login-dialog is 
shown - instead I see the lockscreen wallpaper and the mouse cursor shows 
graphical glitches (becoming invisible and visible when moving it).
I can unlock again by typing `gnome-screensaver-command -d` into a tty.

I have found out, that the program 'gnome-screensaver-dialog' crashes
with a SIGSEV and causes the described failure. Purging and reinstalling
the package 'gnome-screensaver' did not help. Running 'gnome-
screensaver-dialog' with gdb generates the attached output (which is
hopefully useful for tracking down the problem).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Jun 22 00:15:10 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-02-14 (127 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
SourcePackage: gnome-screensaver
UpgradeStatus: Upgraded to bionic on 2018-04-29 (53 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Output of running gnome-screensaver-dialog with gdb."
   
https://bugs.launchpad.net/bugs/1778143/+attachment/5155340/+files/gnome-screensaver-dialog-crash.txt

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

Title:
  SIGSEV when turning on display while screensaver is active (gnome-
  screensaver-dialog crash)

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Since the update to Ubuntu 18.04 (ubuntu budgie) the screensaver
  stopped working.

  Description of the error:

  When I lock the screen, the display turns black (as intended). However, when 
I press a key or move the mouse to turn the display again, no login-dialog is 
shown - instead I see the lockscreen wallpaper and the mouse cursor shows 
graphical glitches (becoming invisible and visible when moving it).
  I can unlock again by typing `gnome-screensaver-command -d` into a tty.

  I have found out, that the program 'gnome-screensaver-dialog' crashes
  with a SIGSEV and causes the described failure. Purging and
  reinstalling the package 'gnome-screensaver' did not help. Running
  'gnome-screensaver-dialog' with gdb generates the attached output
  (which is hopefully useful for tracking down the problem).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Jun 22 00:15:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-14 (127 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (53 days ago)

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

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

Re: [Desktop-packages] [Bug 1738546] Re: firefox quantum not loading

[tobias john knight]

Thankyou so very much for your help.

My computer is all up to date and upgraded, with firefox 57 as part of 
the package.

Thanks again, and have an amazing new year and many many more.

TK

On 27/12/17 12:01, Paul White wrote:
> Thank you for reporting this bug to Ubuntu. The 16.10 release reached
> EOL (end of line) on 20th July 2017, over five months ago. Please refer
> to this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases.
>
> Please use only supported releases of Ubuntu when reporting bugs.
>
> Firefox 57 is currently available from the repositories of all currently
> supported Ubuntu releases.
>
> Please upgrade to or install a supported release. If you are still
> having problems with Firefox 57 then please let us know.
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  firefox quantum not loading

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  All I know is the firefox quantum will not not load as I get taken to
  file manager and have no clue what any of it means or how to use any
  of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  foxyloxy   2380 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat Dec 16 15:22:10 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-18 (392 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
   192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
   
   enp0s20u5u2  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to yakkety on 2017-04-18 (242 days ago)
  dmi.bios.date: 05/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81F1
  dmi.board.vendor: HP
  dmi.board.version: 64.29
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

Re: [Desktop-packages] [Bug 1734138] Re: firefox quantum not loading

[tobias john knight]

Doing sudo apt stuff is so not my thing, as I do not know how to do or 
where do such stuff.

Thankyou though very much for your advice, and everything is ok now as I 
was using a

16.10 system and it got updated to 17.10 system, I think, and firefox 57 
was part of the

upgrade. So thanks again, and have amazing new year and many many more.

TK


On 23/11/17 17:11, Etienne Papegnies wrote:
> When you filed this bug, it was under Firefox 54 
> (54.0+build3-0ubuntu0.16.10.1)
> Not sure how you got this old version but to reinstall:
>
>> sudo apt remove --purge firefox
>> sudo apt update
>> sudo apt install firefox
> Then please attempt to launch it from the command line (Open terminal
> with CTRL+ALT+T then type "firefox") and provide any feedback.
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  firefox quantum not loading

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I have not got a clue about what is going on or how to report it, as I
  am not computer speak literate, and the instructions for downloading
  firefox quantum only apply to 'about firefox', the old one, and not
  installing the new.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  foxyloxy   1970 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Nov 23 14:49:08 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-18 (369 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
   192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   enp0s20u5u2  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to yakkety on 2017-04-18 (219 days ago)
  dmi.bios.date: 05/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81F1
  dmi.board.vendor: HP
  dmi.board.version: 64.29
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1700645] Re: gpg-agent not running when needed by Déjà Dup

[Tobias Barden]

Hello Vej,

I'm also affected from this bug.

System details:
Ubuntu 17.10
deja-dup 36.2-0ubuntu1
duplicity 0.7.12
gpgv 2.1.15-1ubuntu8

Same problem: gpg-agent was not running
But: ~/.gnupg/gpg.conf does not contain a use-agent statement (everything is 
commented out). As I was not able to find any reference on how the default 
gpg.conf file should look like, I'm note sure if this is supposed to or not.

Same solution: starting the agent manually solves the problem.

Kind regards

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

Title:
  gpg-agent not running when needed by Déjà Dup

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  New

Bug description:
  Some have reported problems before with repeated demands for
  encryption passwords, but mine gives a different error.  I've deleted
  all my previous backups and reinstalled duplicity and deja-dup, but I
  still get the error:

  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .
  DUPLICITY: .

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no 
effect
  DUPLICITY: . gpg: invalid size of lockfile 
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
  DUPLICITY: . gpg: cannot read lockfile
  DUPLICITY: . gpg: can't connect to the agent: Invalid argument
  DUPLICITY: . gpg: problem with the agent: No agent running
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  System details:
  Ubuntu 17.04
  deja-dup  34.4-0ubuntu1
  duplicity 0.7.06-2ubuntu3

  Thank you in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1700645/+subscriptions

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

[Desktop-packages] [Bug 1738677] [NEW] Runtime Error: Server Error in '/' Application

[tobias john knight]

Public bug reported:

I have not got a clue how to use computers apart from using websites, so
all I know is that on 'autism.org.uk' I went back to the Online
Community forum page after cancelling a reply, three error panels came
up, so I decided, not knowing why, to sign out, and a Runtime Error page
remains the case and I can no longer get access to the Online Community
forum, whilst all the other options are available.

I went on the internet to find out what a runtime error involved, saw
some advice about un-installing and re-installing firefox, which I
followed via the Ubuntu Software icon, but it made no difference.

Hence I reported the problem as is here the case.

The system I have is Ubuntu 16.10, with Firefox 54.0 ~ and I cannot for
the life of me work out how to install Firefox Quantum as it does not
automatically do so. I got the download for FQ, clicked on the box,
archive manager comes up ~ and I know not what that involves or how to
make use of it.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 54.0+build3-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  foxyloxy   2038 F pulseaudio
BuildID: 20170612122018
Channel: Unavailable
CurrentDesktop: Unity
Date: Mon Dec 18 00:18:07 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-11-18 (394 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
 169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
 192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
IwConfig:
 enp3s0no wireless extensions.
 
 lono wireless extensions.
 
 enp0s20u5u2  no wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to yakkety on 2017-04-18 (243 days ago)
dmi.bios.date: 05/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81F1
dmi.board.vendor: HP
dmi.board.version: 64.29
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Runtime Error: Server Error in '/' Application

Status in firefox package in Ubuntu:
  New

Bug description:
  I have not got a clue how to use computers apart from using websites,
  so all I know is that on 'autism.org.uk' I went back to the Online
  Community forum page after cancelling a reply, three error panels came
  up, so I decided, not knowing why, to sign out, and a Runtime Error
  page remains the case and I can no longer get access to the Online
  Community forum, whilst all the other options are available.

  I went on the internet to find out what a runtime error involved, saw
  some advice about un-installing and re-installing firefox, which I
  followed via the Ubuntu Software icon, but it made no difference.

  Hence I reported the problem as is here the case.

  The system I have is Ubuntu 16.10, with Firefox 54.0 ~ and I cannot
  for the life of me work out how to install Firefox Quantum as it does
  not automatically do so. I got the download for FQ, clicked on the
  box, archive manager comes up ~ and I know not what that involves or
  how to make use of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS CO

[Desktop-packages] [Bug 1738546] [NEW] firefox quantum not loading

[tobias john knight]

Public bug reported:

All I know is the firefox quantum will not not load as I get taken to
file manager and have no clue what any of it means or how to use any of
it.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 54.0+build3-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  foxyloxy   2380 F pulseaudio
BuildID: 20170612122018
Channel: Unavailable
CurrentDesktop: Unity
Date: Sat Dec 16 15:22:10 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-11-18 (392 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
 169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
 192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
IwConfig:
 enp3s0no wireless extensions.
 
 lono wireless extensions.
 
 enp0s20u5u2  no wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to yakkety on 2017-04-18 (242 days ago)
dmi.bios.date: 05/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81F1
dmi.board.vendor: HP
dmi.board.version: 64.29
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug yakkety

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

Title:
  firefox quantum not loading

Status in firefox package in Ubuntu:
  New

Bug description:
  All I know is the firefox quantum will not not load as I get taken to
  file manager and have no clue what any of it means or how to use any
  of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  foxyloxy   2380 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat Dec 16 15:22:10 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-18 (392 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
   192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
   
   enp0s20u5u2  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to yakkety on 2017-04-18 (242 days ago)
  dmi.bios.date: 05/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81F1
  dmi.board.vendor: HP
 

[Desktop-packages] [Bug 1734138] [NEW] firefox quantum not loading

[tobias john knight]

Public bug reported:

I have not got a clue about what is going on or how to report it, as I
am not computer speak literate, and the instructions for downloading
firefox quantum only apply to 'about firefox', the old one, and not
installing the new.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 54.0+build3-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  foxyloxy   1970 F pulseaudio
BuildID: 20170612122018
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Nov 23 14:49:08 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-11-18 (369 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
 169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
 192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
 
 enp0s20u5u2  no wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to yakkety on 2017-04-18 (219 days ago)
dmi.bios.date: 05/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81F1
dmi.board.vendor: HP
dmi.board.version: 64.29
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug yakkety

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

Title:
  firefox quantum not loading

Status in firefox package in Ubuntu:
  New

Bug description:
  I have not got a clue about what is going on or how to report it, as I
  am not computer speak literate, and the instructions for downloading
  firefox quantum only apply to 'about firefox', the old one, and not
  installing the new.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  foxyloxy   1970 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Nov 23 14:49:08 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-18 (369 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev enp0s20u5u2  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u5u2  scope link  metric 1000 
   192.168.0.0/24 dev enp0s20u5u2  proto kernel  scope link  src 192.168.0.178  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   enp0s20u5u2  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to yakkety on 2017-04-18 (219 days ago)
  dmi.b

[Desktop-packages] [Bug 1733131] [NEW] map file entry in updmap caused ubuntu upgrade to fail

[Tobias Wrigstad]

Public bug reported:

similar to #1236951 but when upgrading from 17.04 to 17.10

When upgrading Ubuntu from 17.04 to 17.10 an entry in an updmap in TeX
caused the TeX upgrade to fail which caused the whole upgrade to fail.
This also happened as I upgraded from 16.10 to 17.04 but then caused the
system to not be bootable.

There has been no problems with my TeX installation nor the font in
question (minion pro).

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
Date: Sun Nov 19 01:53:20 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-07-28 (478 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to artful on 2017-11-19 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  map file entry in updmap caused ubuntu upgrade to fail

Status in tex-common package in Ubuntu:
  New

Bug description:
  similar to #1236951 but when upgrading from 17.04 to 17.10

  When upgrading Ubuntu from 17.04 to 17.10 an entry in an updmap in TeX
  caused the TeX upgrade to fail which caused the whole upgrade to fail.
  This also happened as I upgraded from 16.10 to 17.04 but then caused
  the system to not be bootable.

  There has been no problems with my TeX installation nor the font in
  question (minion pro).

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  Date: Sun Nov 19 01:53:20 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-28 (478 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-11-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()

[Tobias Bradtke]

For me this happens after connecting to a bluetooth device. Everything
works, just gnome-control-center crashes after the connection is
established.

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

Title:
  gnome-control-center crashed with SIGSEGV in
  manager_recheck_permissions()

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1675863] Re: Nautilus crash after renaming an ODS file whilst in Filtered view

[Tobias Ribizel]

I ran into this bug as well, see the attached stack trace.

The cause of this bug seems to be the fact that the parent_slot of the
file is empty, so the null pointer at g_class is dereferenced in the
NAUTILUS_FILE_GET_CLASS macro:

(gdb) print *file
$1 = {parent_slot = {g_type_instance = {g_class = 0x0}, ref_count = 0, qdata = 
0x0}, details = ...}

** Attachment added: "trace"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1675863/+attachment/4945733/+files/trace

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

Title:
  Nautilus crash after renaming an ODS file whilst in Filtered view

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Reproduction steps:

  Using nautilus, use CTRL-F to filter files viewed (Open Document ods files 
only)
  Right click on any file in the filtered view, and rename it
  and wait (not long).
  Window greys and closes, resulting in an internal error screen.

  Description:  Ubuntu 16.04.2 LTS  (fully updated as of 24 MAR 2017)
  Release:  16.04

  nautilus:
Installed: 1:3.18.4.is.3.14.3-0ubuntu5
Candidate: 1:3.18.4.is.3.14.3-0ubuntu5
Version table:
   *** 1:3.18.4.is.3.14.3-0ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.18.4.is.3.14.3-0ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Tobias]

Confirm that as well with clean install of Ubuntu gnome 17.04  yesterday, but 
maybe can give little support...
Before I decided to install I tried via Live-USB Stick and also connected to my 
google account.
Worked like a charm! Login-Screen that opened from Google was the old one!
After I installed ubuntu and wanted to creat again it didnt work again and 
ubuntu offered me new login screen.
I did a quick web search and found an interesting information here:
https://support.google.com/accounts/answer/7338427?co=GENIE.Platform%3DDesktop&hl=en

See the following:

You might still see the old sign-in page in these cases:
You use an older version of a browser
You've turned off JavaScript

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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

[Desktop-packages] [Bug 1676527] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück

[Tobias H.]

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

Public bug reported:

no clue

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.8.0-42.45~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-42-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog:
 W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 94 (dbus://) went 
away, retrying!
 W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 95 (dbus://) went 
away, retrying!
 W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 98 (dbus://) went 
away, retrying!
Date: Mon Mar 27 19:48:33 2017
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2017-03-15 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lpstat: device for HLL2340D: 
dnssd://Brother%20HL-L2340D%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-68140152a195
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: HLL2340D: Brother HL-L2340D for CUPS
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0066e04e-8eac-429f-a09c-31b7c8b5cc4c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0066e04e-8eac-429f-a09c-31b7c8b5cc4c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0318
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z270-K
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.:bvr0318:bd11/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  neues pre-removal-Skript gab den Fehlerwert 1 zurück

Status in cups package in Ubuntu:
  New

Bug description:
  no clue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.8.0-42.45~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 94 (dbus://) went 
away, retrying!
   W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 95 (dbus://) went 
away, retrying!
   W [27/Mar/2017:13:31:32 +0200] Notifier for subscription 98 (dbus://) went 
away, retrying!
  Date: Mon Mar 27 19:48:33 2017
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 
zurück
  InstallationDate: Installed on 2017-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for HLL2340D: 
dnssd://Brother%20HL-L2340D%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-68140152a195
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: HLL2340D: Brother HL-L2340D for CUPS
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0066e04e-8eac-429f-a09c-31b7c8b5cc4c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0066e04e-8eac-429f-a09c-31b7c8b5cc4c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0318
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z270-K
  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:bvnAmericanMegatrendsI

[Desktop-packages] [Bug 1673165] [NEW] Ignores route depending on other route

[Tobias Wolter]

Public bug reported:

Used versions:
* Ubuntu 16.10
* network-manager 1.2.6-0ubuntu1
* network-manager-openvpn 1.2.6-2ubuntu1
* openvpn 2.3.11-1ubuntu2


Just like iputils refuses to add routes where it doesn't has a route to the 
gateway on the device, openvpn seems pretty much to do the same.

% sudo /usr/lib/NetworkManager/nm-openvpn-service --debug
[...]
nm-openvpn[16132]:  [helper-16342] environment: script_type=up
nm-openvpn[16132]:  [helper-16342] environment: dev_type=tun
nm-openvpn[16132]:  [helper-16342] environment: dev=tun0
nm-openvpn[16132]:  [helper-16342] environment: link_mtu=1542
nm-openvpn[16132]:  [helper-16342] environment: tun_mtu=1500
nm-openvpn[16132]:  [helper-16342] environment: script_context=init
nm-openvpn[16132]:  [helper-16342] environment: 
route_gateway_2=172.19.200.141
nm-openvpn[16132]:  [helper-16342] environment: 
route_netmask_2=255.255.255.0
nm-openvpn[16132]:  [helper-16342] environment: 
route_network_2=172.19.200.0
nm-openvpn[16132]:  [helper-16342] environment: 
route_gateway_1=172.19.200.141
nm-openvpn[16132]:  [helper-16342] environment: 
route_netmask_1=255.255.0.0
nm-openvpn[16132]:  [helper-16342] environment: 
route_network_1=172.19.0.0
nm-openvpn[16132]:  [helper-16342] environment: 
route_vpn_gateway=172.19.200.141
nm-openvpn[16132]:  [helper-16342] environment: 
route_net_gateway=192.168.178.1
nm-openvpn[16132]:  [helper-16342] environment: 
ifconfig_remote=172.19.200.141
nm-openvpn[16132]:  [helper-16342] environment: 
ifconfig_local=172.19.200.142
nm-openvpn[16132]:  [helper-16342] environment: common_name=server
nm-openvpn[16132]:  [helper-16342] environment: trusted_port=1194
nm-openvpn[16132]:  [helper-16342] environment: trusted_ip=IP_REMOVED
nm-openvpn[16132]:  [helper-16342] environment: untrusted_port=1194
nm-openvpn[16132]:  [helper-16342] environment: untrusted_ip=IP_REMOVED
[...TLS certs etc]
nm-openvpn[16132]:  [helper-16342] environment: verb=10
nm-openvpn[16132]:  [helper-16342] environment: daemon=0
nm-openvpn[16132]:  [helper-16342] environment: daemon_log_redirect=0
nm-openvpn[16132]:  [helper-16342] environment: 
daemon_start_time=1489594872
nm-openvpn[16132]:  [helper-16342] environment: daemon_pid=16267
nm-openvpn[16132]:  [helper-16342] environment: proto_1=udp
nm-openvpn[16132]:  [helper-16342] environment: local_port_1=0
nm-openvpn[16132]:  [helper-16342] environment: 
remote_1=HOST_NAME_REMOVED
nm-openvpn[16132]:  [helper-16342] environment: remote_port_1=1194
[...]

% ip r l | grep 172.19
172.19.200.0/24 via 172.19.200.141 dev tun0  proto static  metric 50 
172.19.200.141 dev tun0  proto kernel  scope link  src 172.19.200.142  metric 
50 

I don't see anything happening to the routes wrt errors:
Wed Mar 15 17:21:15 2017 us=306238 PUSH: Received control message: 
'PUSH_REPLY,route 172.19.0.0 255.255.0.0,route 172.19.200.0 255.255.255.0,ping 
10,ping-restart 120,ifconfig 172.19.200.142 172.19.200.141'
Wed Mar 15 17:21:15 2017 us=306271 OPTIONS IMPORT: timers and/or timeouts 
modified
Wed Mar 15 17:21:15 2017 us=306287 OPTIONS IMPORT: --ifconfig/up options 
modified
Wed Mar 15 17:21:15 2017 us=306290 OPTIONS IMPORT: route options modified
Wed Mar 15 17:21:15 2017 us=306371 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 
IFACE=eth0 HWADDR=54:ee:75:51:75:eb
Wed Mar 15 17:21:15 2017 us=324890 TUN/TAP device tun0 opened
Wed Mar 15 17:21:15 2017 us=324925 TUN/TAP TX queue length set to 100
Wed Mar 15 17:21:15 2017 us=324964 
/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 6 16132 
--bus-name org.freedesktop.NetworkManager.openvpn --tun -- tun0 1500 1542 
172.19.200.142 172.19.200.141 init
Wed Mar 15 17:21:15 2017 us=325278 PKCS#11: __pkcs11h_forkFixup entry 
pid=16342, activate_slotevent=1
Wed Mar 15 17:21:15 2017 us=325329 PKCS#11: __pkcs11h_forkFixup return
nm-openvpn[16132]:  [helper-16342] command line: 
"/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper" "--debug" "6" 
"16132" "--bus-name" "org.freedesktop.NetworkManager.openvpn" "--tun" "--"   
"tun0" "1500" "1542" "172.19.200.142" "172.19.200.141" "init"
nm-openvpn[16132]:  [helper-16342] environment: script_type=up

I'm figuring it's trying to add the route before the network route
itself is there, which leads to expected results when testing:

% sudo ip link add foobar0 type dummy
% sudo ip r a 172.19.0.0/16 dev foobar0 via 172.19.200.141
RTNETLINK answers: Network is unreachable

If you use openvpn directly though, it works just fine:
% ip r l | grep 172.19
% 
% sudo openvpn client.conf
[...]
Wed Mar 15 17:42:13 2017 /sbin/ip addr add dev tun0 local 172.19.200.142 peer 
172.19.200.141
Wed Mar 15 17:42:13 2017 /sbin/ip route add 172.19.0.0/16 via 172.19.200.141
Wed Mar 15 17:42:13 2017 /sbin/ip route add 172.19.200.0/24 via 172.19.200.141
[...]
% ip r l | grep 172.19
172.19.0.0/16 via 172.19.200.141 dev tun0 
172.19.200.0/24 via 172.19.200.141 dev tun0 
172.19.200.141 dev tun0  proto kernel  scope link  src 172.19.200.142 

So I'll be blaming nm-openvpn-servi

[Desktop-packages] [Bug 1670730] Re: pdftopdf "inflate data - incorrect data check" with certain PDFs

[Tobias Hoffmann]

Object 39 is an image; but even Object 4 (the content stream of the
first page; obj 93 *is* used on that page) has such a decompression
error.

Ghostscript prints:
  warning: ignoring zlib error: incorrect data check

So probably libqpdf (which is used for the very low-level pdf stuff in
pdftopdf) should also handle this as warning instead of as error?

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

Title:
  pdftopdf "inflate data - incorrect data check" with  certain PDFs

Status in cups-filters package in Ubuntu:
  New

Bug description:
  When /usr/lib/cups/filter/pdftopdf is processing certain PDF files, it
  stops with this error message:

  WARNING: ./file.pdf (file position 101510): error decoding stream 
  data for object 39 0: stream inflate: inflate: data: incorrect data check
  ERROR: Exception: stream inflate: inflate: data: incorrect data check

  Example PDF (attached a copy, too) :
  
https://shop.groveko.nl/images/products/7010209/VIB%20Suma%20Inox%20Classic%20D7%202016-03-31.pdf

  Adobe Pro doesn't seem to have any issues with these PDFs, so the
  error is probably not fatal for processing the file.

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

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

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

[Tobias Weis]

Is there anything we can do to help fix this, do you need additional
info? Or what exactly is the case there has not even been a status
update in the last YEARS? Given that this is the most basic
functionality and affects _all_ users, I wonder why not even the
importance has been set?

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Confirmed

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1665609] [NEW] please update gsfonts to the latest release

[Tobias Schula]

Public bug reported:

The latest gsfonts now have extended and improved cyrillic and greek
glyphs:

"URW++ update to base 35 from June 2016.

This extends the Greek and Cyrillic glyphs originally supplied in only three
font families to cover all the relevant fonts in the base 35."

Furthermore the fonts are finally available as opentype and truetype
fonts, making them usable in modern applications (libreoffice stops
supporting type1 fonts beginning with 5.3)

http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit

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

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

Title:
  please update gsfonts to the latest release

Status in gsfonts package in Ubuntu:
  New

Bug description:
  The latest gsfonts now have extended and improved cyrillic and greek
  glyphs:

  "URW++ update to base 35 from June 2016.

  This extends the Greek and Cyrillic glyphs originally supplied in only three
  font families to cover all the relevant fonts in the base 35."

  Furthermore the fonts are finally available as opentype and truetype
  fonts, making them usable in modern applications (libreoffice stops
  supporting type1 fonts beginning with 5.3)

  http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit

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

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

[Desktop-packages] [Bug 1663617] [NEW] Error message after running "apt update" after adding libreoffice fresh ppa in ubuntu trusty

[Tobias Schula]

Public bug reported:

After libreoffice 5.3 hit the libreoffice fresh ppa the following error message 
appears after running "apt update":
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
.
.
.
.
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.

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


** Tags: ppa

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

Title:
  Error message after running "apt update" after adding libreoffice
  fresh ppa in ubuntu trusty

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After libreoffice 5.3 hit the libreoffice fresh ppa the following error 
message appears after running "apt update":
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  .
  .
  .
  .
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.

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

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

[Desktop-packages] [Bug 1281700] Re: policykit-1 is not aware of groups assigned by pam_group

[Tobias Volfing]

I am affected by this as well. I want my LDAP users to be able to manage
printers. I've tried removing authentication in cupsd.conf, this works
for the CUPS interface. But not from 'Printers' in system settings. So
instead I've added them to the lpadmin group with the pam mount module,
but it is still not possible.

As noted in another comment, id shows the user being a member of
lpadmin, but id username doesn't.

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

Title:
  policykit-1 is not aware of groups assigned by pam_group

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I'm using pam_group for my ldap users so that they get assigned default 
ubuntu groups:
  $ tail -n2 /etc/security/group.conf

  # add LDAP users to these default groups, but don't give them admin rights.
  "*;*;*;Al-2400;audio,video,cdrom,plugdev,fuse"

  These additional group IDs are assigned correctly:

  $ id
  uid=6007(myusername) gid=6000(ldapgroup) 
groups=6000(ldapgroup),24(cdrom),29(audio),44(video),46(plugdev),104(fuse)

  Based on these additional groups, I'm trying to give certain user
  groups the necessary permissions to execute program, using
  policykit-1. Unfortunately, policykit does seem to only 'see' / 'be
  aware' of the primary group that the user belongs to (and not those
  additional groups that are assigend via /etc/security/group.conf).

  This works (users can start the program):
  [AllowUsertoDoSomething]
  Identity=unix-group:ldapgroup

  This doesn't work (users are asked to provide the administrator password):
  [AllowUsertoDoSomething]
  Identity=unix-group:plugdev

  I suspect that this has something to do with the fact that 'id' does
  return conflicting information about groups:

  # call id without username, returns all groups, including the ones defined in 
/etc/security/group.conf
  $ id
  uid=6007(myusername) gid=6000(ldapgroup) 
groups=6000(ldapgroup),24(cdrom),29(audio),44(video),46(plugdev),104(fuse)

  # call id with username, only ldap groups are returned, the ones defined in 
/etc/security/group.conf are missing.
  $ id myusername
  uid=6007(myusername) gid=6000(ldapgroup) groups=6000(ldapgroup)

  My suspicion is that policykit-1 is calling "id user" (or a similar command) 
and "sees" only the main ldap groups.
  I did not expect this behavior, because /etc/pam.d/polkit-1 does include 
/etc/pam.d/common-auth (which includes the "auth optional pam_group.so" line)

  This is Ubuntu 12.04.3 with all latest updates. Any help and
  suggestions are appreciated.

  $ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  $ apt-cache policy policykit-1
  policykit-1:
    Installed: 0.104-1ubuntu1.1
    Candidate: 0.104-1ubuntu1.1
  ---
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: policykit-1 0.104-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
  Tags:  precise
  Uname: Linux 3.5.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 364091] Re: xrandr error with delmode

[Tobias]

The issue is again (or still) a matter within Ubuntu 14.04 LTS (here
14.04.2) with the following parameters:

xrandr --delmode DP1 1920x1080i X Error of failed request: BadAccess
(attempt to access private resource denied) Major opcode of failed
request: 140 (RANDR) Minor opcode of failed request: 19
(RRDeleteOutputMode) Serial number of failed request: 44 Current serial
number in output stream: 45

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

Title:
  xrandr error with delmode

Status in x11-xserver-utils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: x11-xserver-utils

  Ubuntu 9.04 Realase Candidate, i386
  My setup:  Sapphire 2600 XT AGP + Compaq P1100 monitor (maximux resolution 
supported  1920x1440) connected via DVI port

  Output of xrandr
  Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 2048 x 1600
  DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 
380mm x 290mm
 2048x1536  60.0  
 1920x1440  75.0 60.0  
 1856x1392  75.0 60.0  
 1792x1344  75.0 60.0  
 1600x1200  85.0*75.0 70.0 65.0 60.0  
 1680x1050  84.9 74.9 69.9 60.0  
 1600x1024  60.2  
 1400x1050  85.0 74.8 70.0 60.0  
 1280x1024  85.0 75.0 60.0  
 1440x900   59.9  
 1280x960   85.0 60.0  
 1360x768   59.8  
 1152x864  100.0 85.1 85.0 75.0 75.0 70.0 60.0  
 1024x768   85.0 75.0 70.1 60.0 43.5  
 832x62474.6  
 800x60085.1 85.1 72.2 75.0 60.3 56.2  
 640x48085.0 75.0 72.8 75.0 66.7 59.9  
 720x40087.8 85.0 70.1  
 640x40085.1  
 640x35085.1  
  VGA-0 disconnected (normal left inverted right x axis y axis)

  Maximum default resolution "2048 x 1600" reported, is wrong for Compaq
  P1100 monitor and i tried to delete with the command:

  $ xrandr --delmode DVI-0 2048x1536
  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  150 (RANDR)
Minor opcode of failed request:  19 ()
Serial number of failed request:  23
Current serial number in output stream:  24

  Note: GDM (Login Screen) Bad Screen Refresh Rate

  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM 
Controller/Host-Hub Interface [8086:2570] (rev 02)
Subsystem: ASRock Incorporation Device [1849:2570]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV 630 XT AGP 
[Radeon HD 2600 XT AGP] [1002:9586]
Subsystem: PC Partner Limited Device [174b:0028]

  --- 
  Architecture: i386
  CurrentDmesg:
   [   24.596026] eth0: no IPv6 routers present
   [   26.752026] end_request: I/O error, dev fd0, sector 0
   [   26.784033] end_request: I/O error, dev fd0, sector 0
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Package: x11-xserver-utils 7.5+1ubuntu2
  PackageArchitecture: i386
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic 
root=UUID=11fd8e9e-15b4-4eba-bb1d-434d4d5282b3 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Tags: lucid lucid
  Uname: Linux 2.6.32-21-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/07/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.72
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.72:bd11/07/2008:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions

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

[Desktop-packages] [Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page

[Tobias Hoffmann]

For example, here some java/PDFBox-based implementation of how to flatten 
simple forms:
 https://gist.github.com/jribble/beddf7620536939f88db
(IIRC there are more form elements than those 2-3 handled here(?)).

Note that QPDF does not have something like the PDAcroForm class (and
its friends) used there to easily access the form data. So any QPDF/C++
based form flattener has to implement that, too.

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

Title:
  Cannot print a PDF with AcroForms using fit-to-page

Status in cups-filters package in Ubuntu:
  Incomplete
Status in qpdf package in Ubuntu:
  Incomplete

Bug description:
  Using KUbuntu 14.04. I am trying to print the attached PDF with filled
  forms (AcroForms) with the following command:

  lpr -o fit-to-page PDFForm3.pdf

  But my Samsung ML-1210 prints the document with empty forms. If I omit
  -o fit-to-page then all the forms keep the filled data.

  --

  # lsb_release -rd
  Description:Ubuntu 14.04.4 LTS
  Release:14.04

  # apt-cache policy cups
  cups:
    Installed: 1.7.2-0ubuntu1.7
    Candidate: 1.7.2-0ubuntu1.7
    Version table:
   *** 1.7.2-0ubuntu1.7 0
  500 http://ftp.byfly.by/ubuntu/ trusty-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ftp.byfly.by/ubuntu/ trusty/main i386 Packages

  CUPS in Xenial (from here: http://cdimage.ubuntu.com/daily-
  live/current/xenial-desktop-i386.iso) has the same issue. Xenial:

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  # apt-cache policy cups
  cups:
Installed: 2.1.3-3
Candidate: 2.1.3-4
Version table:
   2.1.3-4 500
  500 http://by.archive.ubuntu.com/ubuntu xenial/main i386 Packages
   *** 2.1.3-3 100
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page

[Tobias Hoffmann]

See https://bugs.linuxfoundation.org/show_bug.cgi?id=1315 why this cannot work.
And QPDF won't be able to do anything about it, either...
There might even be PDF-capable printers on the market (i.e. where the 
rasterization is not done by gs / poppler on the host), where the form content 
will not be printed even without the fit-to-page option.

The PDF format generally does not allow arbitrary transformations (as used by 
pdftopdf in certain cases) to be applied to the ("interactive") Form content - 
which is stored separately from the Page content. 
The usual solution for printing is that the viewer application (Evince, Google 
Chrome, ...) converts (hard-codes) any Form content into regular Page content 
before sending the data to the printing chain. Using lpr skips this 
(non-trivial) step.


** Bug watch added: bugs.linuxfoundation.org/ #1315
   https://bugs.linuxfoundation.org/show_bug.cgi?id=1315

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

Title:
  Cannot print a PDF with AcroForms using fit-to-page

Status in cups-filters package in Ubuntu:
  Incomplete
Status in qpdf package in Ubuntu:
  Incomplete

Bug description:
  Using KUbuntu 14.04. I am trying to print the attached PDF with filled
  forms (AcroForms) with the following command:

  lpr -o fit-to-page PDFForm3.pdf

  But my Samsung ML-1210 prints the document with empty forms. If I omit
  -o fit-to-page then all the forms keep the filled data.

  --

  # lsb_release -rd
  Description:Ubuntu 14.04.4 LTS
  Release:14.04

  # apt-cache policy cups
  cups:
    Installed: 1.7.2-0ubuntu1.7
    Candidate: 1.7.2-0ubuntu1.7
    Version table:
   *** 1.7.2-0ubuntu1.7 0
  500 http://ftp.byfly.by/ubuntu/ trusty-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ftp.byfly.by/ubuntu/ trusty/main i386 Packages

  CUPS in Xenial (from here: http://cdimage.ubuntu.com/daily-
  live/current/xenial-desktop-i386.iso) has the same issue. Xenial:

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  # apt-cache policy cups
  cups:
Installed: 2.1.3-3
Candidate: 2.1.3-4
Version table:
   2.1.3-4 500
  500 http://by.archive.ubuntu.com/ubuntu xenial/main i386 Packages
   *** 2.1.3-3 100
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1284318] Re: alternate finger tapping causes cursor to jump

[Tobias Karlsson]

I'm seing this behavior also and can repeat it easily. Worst part is
that i have set AreaBottomEdge and if I tap quickly above AreaBottomEdge
and then below (most often with my thumb to trigger a left click) cursor
jumps to an edge This happens roughly every 10th left click. Is there
anyone with an idea for a workaround? This issue is kind of a
dealbreaker for me to use ubuntu. Seems silly to to have to use
something as awful as windows just to get a working touchpad

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

Title:
  alternate finger tapping causes cursor to jump

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  I've found that if I quickly alternate tapping with two fingers on the
  touchpad the cursor jumps wildly.

  This is quite frustrating for me as I often move the cursor with one
  finger on my right hand while subsequently clicking the bottom left of
  the touchpad with the left to cause a 'left click' action. Often this
  causes my mouse to jump to the bottom left of the screen and open the
  cinnamon menu window.

  It seems if I monitor events with xinput that the a[0] and a[1] events
  are being swapped.

  motion a[0]=4734 
  motion a[0]=4734 
  motion a[0]=4733 
  motion a[1]=1984 
  motion a[1]=1983 
  motion a[1]=1982 
  motion a[1]=1980 
  motion a[1]=1983 
  motion a[1]=1987 
  motion a[1]=1991 
  motion a[1]=1996 
  motion a[1]=2001 
  motion a[0]=2760 a[1]=4719 <-- Jump happens here

  ...
  Example 2:
  motion a[0]=4578 
  motion a[0]=4578 
  motion a[0]=4577 
  motion a[0]=4577 
  motion a[0]=4576 
  motion a[0]=4575 
  motion a[0]=4575 
  motion a[1]=1990 
  motion a[1]=1989 
  motion a[1]=1987 
  motion a[1]=1986 
  motion a[1]=1984 
  motion a[1]=1983 
  motion a[0]=4577 a[1]=1977 
  motion a[0]=1472 a[1]=4719 <-- Jump happens here
  motion a[0]=1472 a[1]=4722 

  I would have thought that the synaptics driver code would have
  identified 'erratic' input events which appear to be too far apart to
  be naturally occurring and simply filter them out?

  I could not repeat this when I loaded an Ubuntu 13.10 Live USB disk
  but the Synaptics TouchPad driver did not appear to be loaded at that
  time as it didn't appear in xinput list.

   ~> lsb_release -rd
  Description:Linux Mint 16 Petra
  Release:16

  ~>uname -a
  Linux chris-XPS13 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux

  ~> dpkg -l | grep input-synaptics
  ii  xserver-xorg-input-synaptics
1.7.1-0ubuntu1  amd64Synaptics TouchPad driver 
for X.Org server

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/50-synaptics.conf]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:00:55 2014
  InstallationDate: Installed on 2014-02-13 (11 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1284318/+subscriptions

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

[Desktop-packages] [Bug 1550319] [NEW] Blurry text in hidpi mode

[Tobias Suchy]

Public bug reported:

On every possible zoom level the text appears blurry. Everything else is
sharp as you can see on the attached screenshot. I have set the scale to
2x in displaysettings because i am using a 4k hidpi display. It has
140dpi.

I have marked the text so you can see its not just a scaled image. It is
text. I am able to copy text and paste it in a textfield.

Ubuntu 14.04.4 LTS
Evince 3.10.3-0ubuntu10.2

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


** Tags: hidpi

** Attachment added: "Auswahl_001.png"
   
https://bugs.launchpad.net/bugs/1550319/+attachment/4581760/+files/Auswahl_001.png

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

Title:
  Blurry text in hidpi mode

Status in evince package in Ubuntu:
  New

Bug description:
  On every possible zoom level the text appears blurry. Everything else
  is sharp as you can see on the attached screenshot. I have set the
  scale to 2x in displaysettings because i am using a 4k hidpi display.
  It has 140dpi.

  I have marked the text so you can see its not just a scaled image. It
  is text. I am able to copy text and paste it in a textfield.

  Ubuntu 14.04.4 LTS
  Evince 3.10.3-0ubuntu10.2

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

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

[Desktop-packages] [Bug 1547908] [NEW] thumbnail previews blurry in hidpi mode

[Tobias Suchy]

Public bug reported:

When setting a higher scale factor in displaysettings (factor 2 for example) 
only the thumbnails appear blurry. 
But Nautilus seems to create bigger thumbnails: just zoom in nautilus with 
strg++. 

It would be nice when nautilus would use this higher resolved thumbs
instead of upscale the smaller ones.

Screenshot attached.

Ubuntu 14.04.4 LTS
Nautilus 1:3.10.1-0ubuntu9.11

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

** Attachment added: "Auswahl_001.jpg"
   
https://bugs.launchpad.net/bugs/1547908/+attachment/4576634/+files/Auswahl_001.jpg

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

Title:
  thumbnail previews blurry in hidpi mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  When setting a higher scale factor in displaysettings (factor 2 for example) 
only the thumbnails appear blurry. 
  But Nautilus seems to create bigger thumbnails: just zoom in nautilus with 
strg++. 

  It would be nice when nautilus would use this higher resolved thumbs
  instead of upscale the smaller ones.

  Screenshot attached.

  Ubuntu 14.04.4 LTS
  Nautilus 1:3.10.1-0ubuntu9.11

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

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

[Desktop-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

[Tobias Lausch]

ok, will you report when they are available on the debs? then i'll redo
the backtrace with compiz debug symbols.

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

Title:
  Unity does not support cpus without sse4

Status in Compiz:
  Incomplete
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

[Tobias Lausch]

hmm. sorry. no debug symbols for compiz
1:0.9.12.1+15.04.20150410.1-0ubuntu1 available for vivid.

since recompiling compiz on the affected machine will remove the illegal
instruction i cannot help you on this any further.

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

Title:
  Unity does not support cpus without sse4

Status in Compiz:
  Incomplete
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

[Tobias Lausch]

sorry, I forgot to look at the pool. none of them is in the ddebs sorted
to dist vivid.

fyi the only compiz debug symbol in the debs  is 
compizconfig-backend-kconfig-dbgsym 
from http://ddebs.ubuntu.com/dists/vivid/universe/binary-amd64/Packages

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

Title:
  Unity does not support cpus without sse4

Status in Compiz:
  Incomplete
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

[Tobias Lausch]

ok, found and installed the unity-dbgsym and  libnux-4.0-0-dbgsym
but that does not change the backtrace, so I assume it's a compiz bug.

I followed https://wiki.ubuntu.com/DebuggingCompiz.
There they say to install compiz-core-dbgsym compiz-plugins-dbgsym 
compiz-fusion-plugins-main-dbgsym compiz-fusion-plugins-extra-dbgsym 
compizconfig-backend-gconf-dbgsym libcompizconfig0-dbgsym compiz-gnome-dbgsym

after adding the debug debs

 deb http://ddebs.ubuntu.com vivid main restricted universe multiverse
 deb http://ddebs.ubuntu.com vivid-updates main restricted universe multiverse
 deb http://ddebs.ubuntu.com vivid-proposed main restricted universe multiverse

and running apt-get update. ;-)

But there are not any compiz-dbgsym in the repositories.
any idea?

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

Title:
  Unity does not support cpus without sse4

Status in Compiz:
  New
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

[Tobias Lausch]

>From the added backtrace we get that pextrd is the illegal instruction
and therefore schouldnt be used.

hmm, I'll try again with installed unity-dbgsym.

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

Title:
  Unity does not support cpus without sse4

Status in Compiz:
  New
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 893210]

[Tobias Wolf]

Created attachment 118207
attachment-25654-0.html

Just for the record, the reporter (me) doesn't have access to that PC
anymore.
On 11 Sep 2015 05:57,  wrote:

> *Comment # 13  on
> bug 42353  from Raymond
>  *
>
>
>
>
> --- /home/kingfisher/Desktop/alsa-info.no-hp.txt
> +++ /home/kingfisher/Desktop/alsa-info.hp.txt
>
> @@ -3,7 +3,7 @@
>
>  !!ALSA Information Script v 0.4.64
>
>  !!
>
>
>
> -!!Script ran on: Fri Sep 11 02:28:42 UTC 2015
> +!!Script ran on: Fri Sep 11 02:31:15 UTC 2015
>
>
>  !!Linux Distribution
>
> @@ -215,7 +215,7 @@
>  0:6c = 
>  0:6e = 
>  0:70 = 
> -0:72 = 1804
> +0:72 = 180c
>  0:74 = 1001
>  0:76 = 2010
>  0:78 = 
>
>
> JACK SENSE/AUDIO INTERRUPT/STATUS REGISTER  Index 0x72
> Reg No.  Name  D15  D14  D13 D12  D11 D10 D9 D8  D7  D6  D5  D4  D3  D2  D1  
> D0
>
> 0x72  Jack Sense  X  X  X  JS MT2   JS MT1  JS MT0 JS1 EQB  JS0 EQB  JS1 TMR
> JS0 TMR JS1 MD JS0 MD JS1 ST JS0 ST JS1 INT JS0 INT
>
> All register bits are read/write except for JS0ST and JS1ST, which are
> read-only.
> All registers are not shown, and bits containing an X are assumed to be
> reserved.
>
>
> Table 41. Jack Sense Mute Select—JSMT [2:0] Ref  JS1 Headphone  JS0 LINE_OUT
> JSMT2  JSMT1  JSMT0 HP_OUT  LINE_OUT  MONO_OUT
> Notes  0 OUT (0) OUT (0) 0 0 0 ACTIVE ACTIVE ACTIVE JS0 and JS1 ignored.
>
>
> 16 OUT (0) OUT (0) 1 0 0 FMUTE FMUTE ACTIVE JS0 mutes Mono; JS1 no mute 
> action.
> 17 OUT (0) IN (1) 1 0 0 FMUTE ACTIVE FMUTE
> 18 IN (1) OUT (0) 1 0 0 ACTIVE FMUTE ACTIVE
> 19  IN (1)  IN (1)  1  0 0 ACTIVE  ACTIVE  FMUTE
>
> --
> You are receiving this mail because:
>
>- You reported the bug.
>
>

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1078704]

[Tobias Wolf]

Created attachment 118207
attachment-25654-0.html

Just for the record, the reporter (me) doesn't have access to that PC
anymore.
On 11 Sep 2015 05:57,  wrote:

> *Comment # 13  on
> bug 42353  from Raymond
>  *
>
>
>
>
> --- /home/kingfisher/Desktop/alsa-info.no-hp.txt
> +++ /home/kingfisher/Desktop/alsa-info.hp.txt
>
> @@ -3,7 +3,7 @@
>
>  !!ALSA Information Script v 0.4.64
>
>  !!
>
>
>
> -!!Script ran on: Fri Sep 11 02:28:42 UTC 2015
> +!!Script ran on: Fri Sep 11 02:31:15 UTC 2015
>
>
>  !!Linux Distribution
>
> @@ -215,7 +215,7 @@
>  0:6c = 
>  0:6e = 
>  0:70 = 
> -0:72 = 1804
> +0:72 = 180c
>  0:74 = 1001
>  0:76 = 2010
>  0:78 = 
>
>
> JACK SENSE/AUDIO INTERRUPT/STATUS REGISTER  Index 0x72
> Reg No.  Name  D15  D14  D13 D12  D11 D10 D9 D8  D7  D6  D5  D4  D3  D2  D1  
> D0
>
> 0x72  Jack Sense  X  X  X  JS MT2   JS MT1  JS MT0 JS1 EQB  JS0 EQB  JS1 TMR
> JS0 TMR JS1 MD JS0 MD JS1 ST JS0 ST JS1 INT JS0 INT
>
> All register bits are read/write except for JS0ST and JS1ST, which are
> read-only.
> All registers are not shown, and bits containing an X are assumed to be
> reserved.
>
>
> Table 41. Jack Sense Mute Select—JSMT [2:0] Ref  JS1 Headphone  JS0 LINE_OUT
> JSMT2  JSMT1  JSMT0 HP_OUT  LINE_OUT  MONO_OUT
> Notes  0 OUT (0) OUT (0) 0 0 0 ACTIVE ACTIVE ACTIVE JS0 and JS1 ignored.
>
>
> 16 OUT (0) OUT (0) 1 0 0 FMUTE FMUTE ACTIVE JS0 mutes Mono; JS1 no mute 
> action.
> 17 OUT (0) IN (1) 1 0 0 FMUTE ACTIVE FMUTE
> 18 IN (1) OUT (0) 1 0 0 ACTIVE FMUTE ACTIVE
> 19  IN (1)  IN (1)  1  0 0 ACTIVE  ACTIVE  FMUTE
>
> --
> You are receiving this mail because:
>
>- You reported the bug.
>
>

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

Title:
  headphone jack sense not enabled

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  bug is present in Ubuntu 12.04 and Xubuntu 12.04 and Lubuntu 12.04.1 64bit 
  alsa-base 1.0.25+dfsg-0ubuntu1 on this machine (64 bit)
  I except Ubuntu to automatically sense the presence of headphones and disable 
the speakers.  This is not the case, the speakers and headphones play 
simultaneously.  I must install gnome-alsamixer to manually set the jack sense. 
 Alsa should have this enabled as the default setting.  This seems as though it 
should be a very easy bug to fix, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  love   1330 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 21'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 33
 Simple ctrls  : 22
  Date: Wed Nov 14 06:42:21 2012
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.11
  dmi.board.name: 08A0
  dmi.board.vendor: Compal
  dmi.board.version: 32.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr:
  dmi.product.name: Presario R3200 (PF153UA#ABA)
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1424413] Re: Missing german translation for an option

[Tobias Bannert]

** Changed in: ubuntu-translations
   Status: New => Confirmed

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

Title:
  Missing german translation for an option

Status in Ubuntu Translations:
  Confirmed
Status in xscreensaver package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu 15.04 dev with xscreensaver 5.30-1ubuntu1 and I'm
  noticing that the option "Quick Power-off in Blank Only Mode" in
  xscreensaver-demo in the register "Advanced" isn't translated into
  german.

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

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

[Desktop-packages] [Bug 1470097] [NEW] Unity does not support cpus without sse4

[Tobias Lausch]

Public bug reported:

Unity uses sse4 instructions which are not available on older  celeron
or pentium cpus.

The instruction being used causing unity to crash is
PEXTRD

In this case one cannot login into the default unity session.
current workaround is to install gnome.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: GNOME
Date: Tue Jun 30 14:32:20 2015
InstallationDate: Installed on 2015-06-29 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug gnome3-ppa third-party-packages vivid

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

Title:
  Unity does not support cpus without sse4

Status in unity package in Ubuntu:
  New

Bug description:
  Unity uses sse4 instructions which are not available on older  celeron
  or pentium cpus.

  The instruction being used causing unity to crash is
  PEXTRD

  In this case one cannot login into the default unity session.
  current workaround is to install gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1 [modified: usr/bin/unity]
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: GNOME
  Date: Tue Jun 30 14:32:20 2015
  InstallationDate: Installed on 2015-06-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1464783] Re: Number up option is processed before the page extraction option

[Tobias Hoffmann]

According to Mike Sweet [1]:

"Dec 28, 2007 by Michael Sweet:
The 1.1.x (and 1.0.x) behavior was incorrect. According to the IPP 
specification, number-up is applied *first*, and page-ranges refers to the 
imposed pages. Similarly, page-set is applied after imposition."

and here [2]:

"Nov 16, 2008 by Michael Sweet:
IPP specifies the page-ranges applies after imposition, so the current 
implementation is correct.

I'll add a note to the documentation about the behavior."

My man page of lp(1) says:

"   -P page-list
Specifies  which  pages  to print in the document. The list can 
contain a list of numbers and ranges (#-#) separated by commas (e.g.
1,3-5,16). The page numbers refer to the output pages and not the 
document's original pages - options like  "number-up"  can  affect
the numbering of the pages."

And -P is just a shortcut for page-ranges=.

For that reason pstops handles page-ranges the way it does. And pdftopdf
deliberately follows pstops' logic.

However I don't know which IPP specification Mike references here. From
my understanding of RFC2911 (IPP 1.1), Section 15.3 [3], page-ranges is
applied in step 2, and number-up is applied only in the next step 3.
Maybe Mike can shed some light on this issue?


[1] http://cups.org/str.php?L2643
[2] http://cups.org/str.php?L3008
[3] https://tools.ietf.org/html/rfc2911#section-15.3

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

Title:
  Number up option is processed before the page extraction option

Status in cups-filters package in Ubuntu:
  New

Bug description:
  When printing multiple pages per sheet, it seems that number-up option
  is processed before the page range option.

  For example, the command below will print 4 pages of the document
  using two sheets of paper, instead of one sheet with two pages.

  lp -o page-ranges=1-2 -o number-up=2 filename.pdf

  This bug makes it impossible to print odd number of pages with number-
  up option > 1. Say, if I want to print three pages using two pages per
  sheet, and I will not be able to.

  This was tested with Cups 1.7.5, cups-filters 1.0.69 on Ubuntu.

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

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

[Desktop-packages] [Bug 1447501] [NEW] deja-dup crashes on start when using S3

[Tobias Wolter]

Public bug reported:

Backtrace when starting deja-dup backup to S3 (either via GUI or using
deja-dup --backup):

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1500, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1494, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1327, in main
action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1047, 
in ProcessCommandLine
globals.backend = backend.get_backend(args[0])
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 221, in 
get_backend
obj = get_backend_object(url_string)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 207, in 
get_backend_object
return factory(pu)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 161, in __init__
self.resetConnection()
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 183, in resetConnection
self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 97, in get_connection
assert scheme == 's3'
AssertionError

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: deja-dup 32.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 23 10:43:45 2015
InstallationDate: Installed on 2013-05-06 (716 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to vivid on 2014-10-23 (181 days ago)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  deja-dup crashes on start when using S3

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Backtrace when starting deja-dup backup to S3 (either via GUI or using
  deja-dup --backup):

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1500, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1494, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1327, in main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 
1047, in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 221, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 207, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 161, in __init__
  self.resetConnection()
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 183, in resetConnection
  self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", 
line 97, in get_connection
  assert scheme == 's3'
  AssertionError

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: deja-dup 32.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 23 10:43:45 2015
  InstallationDate: Installed on 2013-05-06 (716 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to vivid on 2014-10-23 (181 days ago)

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

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

[Desktop-packages] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad

[Tobias Cohen]

Having the same problem on my Macbook Air. Unfortunate, as this seems to
be the primary thing that's making Ubuntu unpleasant to use on this
machine.

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

Title:
  Missing support for thumb resting on bottom of clickpad

Status in xf86-input-synaptics:
  Unknown
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics source package in Precise:
  Confirmed
Status in xserver-xorg-input-synaptics package in Debian:
  New

Bug description:
  When using the trackpad on the MacBook Pro In Mac OS X it is possible to have 
the thumb resting (ready to click) on the bottom part of the touchpad while 
moving the mouse pointer around with your index or middle finger. 
  Likewise it is also possible to use two finger scrolling with the index and 
middle finger on the upper part on the track pad while resting the thumb on the 
lower part of the trackpad.

  This behaviour is not currently supported with the synaptics driver in
  12.04. It wil register a two finger scroll when the thumb is resting
  in the bottom part and index finger moves around in the upper part.

  I have tried playing aroud with the setting AreaBottomEdge that
  disables all motion on the bottom part of the touchpad. Unfortunately
  when this setting is enabled it still detects a finger in the area, so
  it wil register a two finger scroll like before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions

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

[Desktop-packages] [Bug 1425319] Re: Problem with gnome-network-indicator

[Tobias Dausend]

Some further information about this bug:
http://ubuntu.aspcode.net/view/63540014012470517598470/nm-applets-vpn-
menu-disappears

** Package changed: ubuntu => network-manager-applet (Ubuntu)

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

Title:
  Problem with gnome-network-indicator

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

Bug description:
  Hello!

  After last update done today I've got some strange problem regarding
  the indicator for my network-manager: The menu entry to disconnect
  from concurrent network is disabled and also the submenu for vpn-
  configuration is not usable for the moment. Could you please help me
  regarding this problem? Because until today everything was correct and
  functional this seems to be a bug with a package regarding gnome.

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

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

[Desktop-packages] [Bug 1414707] Re: Login fails, returns to login and flickering prevents password typing

[Tobias Schönberg]

apport information

** Tags added: apport-collected vivid

** Description changed:

  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login into
  the machine a few times and run updates and install a few programs. I
  also installed the VirtualBox guest additions. Since today this happens:
  
  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password field,
  which prevents it from being typed.
  
  So I can't login into the machine anymore.
  
  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The iso
  was from the 20th of January, but I did a daily sudo apt-get upgrade on
  it.
  
  Video: https://www.youtube.com/watch?v=7Xpt39AKVuE&feature=youtu.be
+ --- 
+ ApportVersion: 2.15.1-0ubuntu2
+ Architecture: amd64
+ DistroRelease: Ubuntu 15.04
+ InstallationDate: Installed on 2015-01-22 (5 days ago)
+ InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20141218)
+ Package: gdm 3.14.1-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=de_AT:de
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=de_AT.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
+ Tags:  vivid
+ Uname: Linux 3.18.0-9-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  Login fails, returns to login and flickering prevents password typing

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login
  into the machine a few times and run updates and install a few
  programs. I also installed the VirtualBox guest additions. Since today
  this happens:

  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password
  field, which prevents it from being typed.

  So I can't login into the machine anymore.

  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The
  iso was from the 20th of January, but I did a daily sudo apt-get
  upgrade on it.

  Video: https://www.youtube.com/watch?v=7Xpt39AKVuE&feature=youtu.be
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-22 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20141218)
  Package: gdm 3.14.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1414707] Re: Login fails, returns to login and flickering prevents password typing

[Tobias Schönberg]

Oddly enough this worked. I went into GRUB and tried the systemd-option
and this made the login screen work again.

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

Title:
  Login fails, returns to login and flickering prevents password typing

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login
  into the machine a few times and run updates and install a few
  programs. I also installed the VirtualBox guest additions. Since today
  this happens:

  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password
  field, which prevents it from being typed.

  So I can't login into the machine anymore.

  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The
  iso was from the 20th of January, but I did a daily sudo apt-get
  upgrade on it.

  Video: https://www.youtube.com/watch?v=7Xpt39AKVuE&feature=youtu.be
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-22 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20141218)
  Package: gdm 3.14.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1414707] Re: Login fails, returns to login and flickering prevents password typing

[Tobias Schönberg]

** Description changed:

  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login into
  the machine a few times and run updates and install a few programs. I
  also installed the VirtualBox guest additions. Since today this happens:
  
  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password field,
  which prevents it from being typed.
  
  So I can't login into the machine anymore.
  
  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The iso
  was from the 20th of January, but I did a daily sudo apt-get upgrade on
  it.
+ 
+ Video: https://www.youtube.com/watch?v=7Xpt39AKVuE&feature=youtu.be

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

Title:
  Login fails, returns to login and flickering prevents password typing

Status in gdm package in Ubuntu:
  New

Bug description:
  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login
  into the machine a few times and run updates and install a few
  programs. I also installed the VirtualBox guest additions. Since today
  this happens:

  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password
  field, which prevents it from being typed.

  So I can't login into the machine anymore.

  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The
  iso was from the 20th of January, but I did a daily sudo apt-get
  upgrade on it.

  Video: https://www.youtube.com/watch?v=7Xpt39AKVuE&feature=youtu.be

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

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

[Desktop-packages] [Bug 1414707] Re: Login fails, returns to login and flickering prevents password typing

[Tobias Schönberg]

** Description changed:

  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login into
  the machine a few times and run updates and install a few programs. I
  also installed the VirtualBox guest additions. Since today this happens:
  
  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password field,
  which prevents it from being typed.
  
  So I can't login into the machine anymore.
  
- I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM.
+ I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The is
+ was from the 20th of January, but I did a daily sudo apt-get upgrade on
+ it.

** Description changed:

  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login into
  the machine a few times and run updates and install a few programs. I
  also installed the VirtualBox guest additions. Since today this happens:
  
  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password field,
  which prevents it from being typed.
  
  So I can't login into the machine anymore.
  
- I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The is
+ I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The iso
  was from the 20th of January, but I did a daily sudo apt-get upgrade on
  it.

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

Title:
  Login fails, returns to login and flickering prevents password typing

Status in gdm package in Ubuntu:
  New

Bug description:
  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login
  into the machine a few times and run updates and install a few
  programs. I also installed the VirtualBox guest additions. Since today
  this happens:

  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password
  field, which prevents it from being typed.

  So I can't login into the machine anymore.

  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM. The
  iso was from the 20th of January, but I did a daily sudo apt-get
  upgrade on it.

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

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

[Desktop-packages] [Bug 1414707] [NEW] Login fails, returns to login and flickering prevents password typing

[Tobias Schönberg]

Public bug reported:

I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login into
the machine a few times and run updates and install a few programs. I
also installed the VirtualBox guest additions. Since today this happens:

I log into the machine. The login is accepted and the machine does
something for a few seconds. Then the machine jumps back to login, but
with a random flickering. The flickering also resets the password field,
which prevents it from being typed.

So I can't login into the machine anymore.

I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM.

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

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

Title:
  Login fails, returns to login and flickering prevents password typing

Status in gdm package in Ubuntu:
  New

Bug description:
  I was testing Ubuntu Gnome 15.04 in VirtualBox. I was able to login
  into the machine a few times and run updates and install a few
  programs. I also installed the VirtualBox guest additions. Since today
  this happens:

  I log into the machine. The login is accepted and the machine does
  something for a few seconds. Then the machine jumps back to login, but
  with a random flickering. The flickering also resets the password
  field, which prevents it from being typed.

  So I can't login into the machine anymore.

  I am using a HP Probook 6570 b which I upgraded to 16 GB of RAM.

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

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

[Desktop-packages] [Bug 1404144] [NEW] nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build

[Tobias Kellner]

Public bug reported:

Error! Bad return status for module build on kernel: 3.16.0-29-generic (x86_64)
Consult /var/lib/dkms/nvidia-331-uvm/331.113/build/make.log for more 
information.
Error! Problems with depmod detected.  Automatically uninstalling this module.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.113-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-29-generic
Date: Fri Dec 19 09:36:52 2014
PackageVersion: 331.113-0ubuntu0.1
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed 
to build
UpgradeStatus: Upgraded to utopic on 2014-10-27 (52 days ago)

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


** Tags: amd64 apport-package utopic

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

Title:
  nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed
  to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Error! Bad return status for module build on kernel: 3.16.0-29-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-331-uvm/331.113/build/make.log for more 
information.
  Error! Problems with depmod detected.  Automatically uninstalling this module.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.113-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-29-generic
  Date: Fri Dec 19 09:36:52 2014
  PackageVersion: 331.113-0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed 
to build
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (52 days ago)

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

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

[Desktop-packages] [Bug 1313283] Re: gedit always prints in black and white on color printer

[Tobias Bradtke]

It seems to work on Ubuntu-14.10, even though versions do not really differ:
http://changelogs.ubuntu.com/changelogs/pool/main/g/gedit/gedit_3.10.4-0ubuntu6/changelog

But gtksourceview got some new releases, so maybe it is fixed there. Could 
match report from @alberich:
http://changelogs.ubuntu.com/changelogs/pool/main/g/gtksourceview3/gtksourceview3_3.12.3-1ubuntu1/changelog

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

Title:
  gedit always prints in black and white on color printer

Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  gedit shows syntax highlighting (with default Classic color scheme)
  properly, yet prints/previews text as black-and-white for a color
  printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to
  print properly in color.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 27 03:47:14 2014
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2014-04-03 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

[Tobias Sch]

I tried installing the Gnome desktop which did not help. Then I updated
to Gnome 3.14 and the mouse cursor still disappears.

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

Title:
  Mouse pointer disappears and cursor stops blinking

Status in “anjuta” package in Ubuntu:
  Confirmed
Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Open gedit.
  Notice the cursor is blinking.
  Type a few lines of text.
  Highilight some of the text.
  Press  to cut the text.
  Notice that the mouse ponter is invisible while hovering over the gedit 
window. Notice that the gedit cursor is no longer blinking.

   $ uname -a
  Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.10
  Release:  14.10
  Codename: utopic

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

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

Per PDF Spec, the /contents key in a Page dictionary is optional.
The attached pdf's page 9 has no /contents key.

But QPdfObjectHandle::getPageContents() throws an exception;
cups-filter (pdftopdf) calls it via QPDFObjectHandle::addPageContents().

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

/Contents  is the correct spelling.

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

Exception is thrown in libqpdf

** Package changed: cups-filters (Ubuntu) => qpdf (Ubuntu)

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

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 1100190]

[Tobias-pichler]

I can confirm the behavior described from Christian Krützfeldt on Ubuntu
14.10 / LibreOffice 4.3.3.2

I am asked for my password everytime i open any document with
LibreOffice on the WebDAV share mounted via Nautilus.

This is pretty annoying if you are using two factor authentication
(generate a one-time password for your WebDAV connections) like for
example Google is offering.

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

Title:
  [Upstream] I/O Error while opening file from WebDAV over GVFS from
  Nautilus

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Problem description: 
  Error when opening a file from Nautilus with LibreOffice when the file is 
WebDAV mounted with GVFS.

  The Same file can be opened from the same location from within
  LibreOffice, with the Open File Dialogue. Then you get asked for the
  Username and Password and Libreoffice seems to access the file
  directly over HTTP.

  Steps to reproduce:
  1. Mount a DAV Folder with Nautilus. 
  URL in my Case: 
dav://admin@10.1.10.58:8080/alfresco/webdav/Sites/puzzletest/documentLibrary/Alfresco%20WebDAV%20Test/
  2. Open a file with LibreOffice by doubleclick or context menu from Nautilus.
  4. Error occurs.
  Exact message:
  (-) «General input/output error while accessing /home/pgassmann/.gvfs/WebDAV\ 
als\ admin\ auf\ 10.1.10.58%3A8080/Sites/puzzletest/documentLibrary/Alfresco\ 
WebDAV\ Test/Neu.odt.» [OK]

  Working Variant:
  1. = 1. above
  2. Start LibreOffice
  3. Open File dialogue from LibreOffice
  4. Select the same file and click Open.
  5. LibreOffice Dialogue: "Authentication Required", Enter user name and 
password for: "Alfresco DAV Server" on 10.1.10.58
  6. Enter Username and password, click OK
  7. File opens correctly

  LibreOffice Version:
  3.5.2-2ubuntu1

  Involved Software: 
  LibreOffice, Nautilus, GVFS, Alfresco

  Current behavior:
  Opening file from Nautilus causes Error,
  Opening from LibreOffice Open File dialogue asks for credentials and works 
correctly

  Expected behavior:
  Opening from Nautilus works.
  Opening from Open File dialog works without asking for credentials.

  Attachment: strace log from following actions:
  LANG=C libreoffice --strace
  successfully Open File from LibreOffice dialogue.
  Trying to open file from Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Jan 16 10:05:05 2013
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-22 (238 days ago)

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

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

[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

[Tobias Sch]

The bug also affects Anjuta 3.12.0

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

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

Title:
  Mouse pointer disappears and cursor stops blinking

Status in “anjuta” package in Ubuntu:
  New
Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Open gedit.
  Notice the cursor is blinking.
  Type a few lines of text.
  Highilight some of the text.
  Press  to cut the text.
  Notice that the mouse ponter is invisible while hovering over the gedit 
window. Notice that the gedit cursor is no longer blinking.

   $ uname -a
  Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.10
  Release:  14.10
  Codename: utopic

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

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

[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

[Tobias Sch]

I can confirm all of the above for Gedit and Calculator.

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

Title:
  Mouse pointer disappears and cursor stops blinking

Status in “gedit” package in Ubuntu:
  Confirmed

Bug description:
  Open gedit.
  Notice the cursor is blinking.
  Type a few lines of text.
  Highilight some of the text.
  Press  to cut the text.
  Notice that the mouse pinter is invisible while hovering over the gedit 
window. Notice that the gedit cursor is no longer blinking.

   $ uname -a
  Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.10
  Release:  14.10
  Codename: utopic

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

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

[Desktop-packages] [Bug 1343020] Re: Realtek ALC889A No sound output

[Tobias S]

Okay, at least there is a workaround for this: Install "alsa-tools-gui",
start "HDAJackRetask" and override the Pin "0x1a" with "Headphone". Not
a very nice solution, but its the only workaround I got to work.

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

Title:
  Realtek ALC889A No sound output

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

Bug description:
  I checked whole Google for this problem and tried very many things to
  solve it. Alsamixer does recognise if I plug in the headphones and
  does automute the speaker-sound but there is no sound on the
  headphones. The speakers work well. I installed some extern drivers by
  Realtek but this crashed the whole sound and I did a fresh
  installation of Ubuntu 14.04. The only thing I changed now is alsa-
  base.conf, I added the recommended line "options snd-hda-intel
  model=mb5" for my Macbook.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
tobias14404 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 17 01:29:33 2014
  InstallationDate: Installed on 2014-07-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Internes Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
tobias14404 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_Type: No sound at all
  Title: [MacBook5,2, Realtek ALC889A, Green Headphone Out, Rear] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB52.88Z.0088.B05.090416
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22788AA
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788AA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA:
  dmi.product.name: MacBook5,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-16T22:29:29.018786

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

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

[Desktop-packages] [Bug 1343020] Re: Realtek ALC889A No sound output

[Tobias Schönebaum]

Ok, I'll remove it. My bootloader only starts Ubuntu after cold boot,
but not after restart, so it's not true for me.

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

Title:
  Realtek ALC889A No sound output

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

Bug description:
  I checked whole Google for this problem and tried very many things to
  solve it. Alsamixer does recognise if I plug in the headphones and
  does automute the speaker-sound but there is no sound on the
  headphones. The speakers work well. I installed some extern drivers by
  Realtek but this crashed the whole sound and I did a fresh
  installation of Ubuntu 14.04. The only thing I changed now is alsa-
  base.conf, I added the recommended line "options snd-hda-intel
  model=mb5" for my Macbook.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
    tobias14404 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 17 01:29:33 2014
  InstallationDate: Installed on 2014-07-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Internes Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
tobias14404 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_Type: No sound at all
  Title: [MacBook5,2, Realtek ALC889A, Green Headphone Out, Rear] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB52.88Z.0088.B05.090416
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22788AA
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788AA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA:
  dmi.product.name: MacBook5,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-16T22:29:29.018786

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

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

[Desktop-packages] [Bug 1343020] [NEW] Realtek ALC889A No sound output

[Tobias Schönebaum]

Public bug reported:

I checked whole Google for this problem and tried very many things to
solve it. Alsamixer does recognise if I plug in the headphones and does
automute the speaker-sound but there is no sound on the headphones. The
speakers work well. I installed some extern drivers by Realtek but this
crashed the whole sound and I did a fresh installation of Ubuntu 14.04.
The only thing I changed now is alsa-base.conf, I added the recommended
line "options snd-hda-intel model=mb5" for my Macbook.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tobias 1922 F pulseaudio
  tobias14404 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 17 01:29:33 2014
InstallationDate: Installed on 2014-07-16 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: Internes Audio - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tobias 1922 F pulseaudio
      tobias14404 F pulseaudio
Symptom_Jack: Green Headphone Out, Rear
Symptom_Type: No sound at all
Title: [MacBook5,2, Realtek ALC889A, Green Headphone Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB52.88Z.0088.B05.090416
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22788AA
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788AA
dmi.modalias: 
dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA:
dmi.product.name: MacBook5,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-16T22:29:29.018786

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


** Tags: apport-bug i386 trusty

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

Title:
  Realtek ALC889A No sound output

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

Bug description:
  I checked whole Google for this problem and tried very many things to
  solve it. Alsamixer does recognise if I plug in the headphones and
  does automute the speaker-sound but there is no sound on the
  headphones. The speakers work well. I installed some extern drivers by
  Realtek but this crashed the whole sound and I did a fresh
  installation of Ubuntu 14.04. The only thing I changed now is alsa-
  base.conf, I added the recommended line "options snd-hda-intel
  model=mb5" for my Macbook.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
tobias14404 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 17 01:29:33 2014
  InstallationDate: Installed on 2014-07-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Internes Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobias 1922 F pulseaudio
tobias14404 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_Type: No sound at all
  Title: [MacBook5,2, Realtek ALC889A, Green Headphone Out, Rear] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB52.88Z.0088.B05.090416
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22788AA
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788AA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-

[Desktop-packages] [Bug 1335933] [NEW] fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

[Tobias Wagner]

Public bug reported:

System complains about it

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:13.350.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 3.2.1-030201-generic-pae
Date: Sat Jun 28 22:13:34 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx, 13.350.1, 3.13.0-30-generic, i686: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 
5550/5570/5630/6510/6610/7570] [1002:68d9] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 5570 
[174b:e142]
MachineType: Packard Bell imedia S3850
PackageVersion: 2:13.350.1-0ubuntu2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=ce00cd01-7705-4a9a-a1b7-0317e1599ce8 ro splash quiet vt.handoff=7
SourcePackage: fglrx-installer
Title: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: imedia S3850
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A0:bd11/20/2010:svnPackardBell:pnimediaS3850:pvrP01-A0:rvnPackardBell:rnimediaS3850:rvr:cvnPackardBell:ct3:cvr:
dmi.product.name: imedia S3850
dmi.product.version: P01-A0
dmi.sys.vendor: Packard Bell
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Jun 30 19:18:26 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputVF0640 Live! Cam Socialize KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Generic Wheel Mouse MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: fglrx

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty ubuntu

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

Title:
  fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  System complains about it

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:13.350.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 3.2.1-030201-generic-pae
  Date: Sat Jun 28 22:13:34 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-30-generic, i686: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 
5550/5570/5630/6510/6610/7570] [1002:68d9] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 5570 
[174b:e142]
  MachineType: Packard Bell imedia S3850
  PackageVersion: 2:13.350.1-0ubuntu2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=ce00cd01-7705-4a9a-a1b7-0317e1599ce8 ro splash quiet vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.

[Desktop-packages] [Bug 1277971] Re: unity-control-center crashed with SIGSEGV in gtk_builder_get_object()

[Tobias Gerhardt]

Bug also occurs in version 14.10.0+14.10.20140604-0ubuntu2 in Utopic

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

Title:
  unity-control-center crashed with SIGSEGV in gtk_builder_get_object()

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

Bug description:
  NA

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  8 13:34:18 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2013-06-10 (242 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f157f46f716 :mov
(%rbx),%rdx
   PC (0x7f157f46f716) ok
   source "(%rbx)" (0x136bb3f3) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in gtk_builder_get_object()
  UpgradeStatus: Upgraded to trusty on 2014-02-04 (3 days ago)
  UserGroups: adm androiddev cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1319338] [NEW] Default boost v1.54 has broken asio while available 1.55 is fixed

[Tobias Föhst]

Public bug reported:

Release: 14.04 LTS
Version: 1.54.0.1ubuntu1
Expected: Depend on working version of boost
Happened: Depends on boost 1.54

Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
Due to that, working with boost/asio seems impossible.

The bug is still present in boost1.54 but fixed in boost1.55. Therefore
I consider it a bug to use version 1.54 as default, as other libraries'
dev-packages depend on boost-default and hence cannot be installed
together with libboost1.55-dev without being rebuild.

Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

** Affects: boost-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Default boost v1.54 has broken asio while available 1.55 is fixed

Status in “boost-defaults” package in Ubuntu:
  New

Bug description:
  Release: 14.04 LTS
  Version: 1.54.0.1ubuntu1
  Expected: Depend on working version of boost
  Happened: Depends on boost 1.54

  Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
  Due to that, working with boost/asio seems impossible.

  The bug is still present in boost1.54 but fixed in boost1.55.
  Therefore I consider it a bug to use version 1.54 as default, as other
  libraries' dev-packages depend on boost-default and hence cannot be
  installed together with libboost1.55-dev without being rebuild.

  Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
  But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

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

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

[Desktop-packages] [Bug 1173890] Re: Hardware Acceleration Broken on Geforce FX 5200

[Tobias Krais]

Use Gnome instead and your graphical interface will work - but not
really nice.

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

Title:
  Hardware Acceleration Broken on Geforce FX 5200

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  Confirmed

Bug description:
  Hardware Acceleration is reported supported by the Nvidia-173 driver
  for this Device.

  on clean install from ubuntu CD, unable to get to unity desktop (blank
  screen with cursor).

  removing Nouveau and installing Nvidia-173 does not remedy the
  problem.

  Garbage on screen during plymouth. No Hardware Acceleration avaiable
  for unity.

  Compiz returning error messages.

  effecting Ubuntu 13.04 12.10 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.card:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:4x 2x 1x
   Registers:0x1f000217:0x1f000104
  .proc.driver.nvidia.agp.host.bridge:
   Host Bridge:  PCI device 8086:1a30
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:4x 2x 1x
   Registers:0x1f000217:0x0104
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 4x
   Fast Writes:  Disabled
   SBA:  Disabled
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  173.14.37  Wed Mar  6 16:56:05 
PST 2013
   GCC version:  gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
  .tmp.unity.support.test.1:

  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 28 11:25:47 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: nvidia-173, 173.14.37, 3.8.0-19-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2013-04-22 (5 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130402.1)
  Lsusb:
   Bus 002 Device 002: ID 12bd:d015
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Vectra
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=9d67f927-723a-409b-b289-263f761640ef ro vesafb.invalid=1 splash 
nomodeset nopat quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2001
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JA.01.04US
  dmi.board.name: HP System Board
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: A08
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Version 1.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJA.01.04US:bd07/19/2001:svnHewlett-Packard:pnHPVectra:pvrVL420:rvnHewlett-Packard:rnHPSystemBoard:rvrA08:cvnHewlett-Packard:ct3:cvrVersion1.00:
  dmi.product.name: HP Vectra
  dmi.product.version: VL420
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 28 11:18:50 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   DFP-0
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: nvidia

To manage notifications about this bug go to:
https://bugs.launchp

[Desktop-packages] [Bug 1173890] Re: Hardware Acceleration Broken on Geforce FX 5200

[Tobias Krais]

Same here on 14.04: nouveau very slow, nivida-173 with nice background
and mouse arrow but nothing else.

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

Title:
  Hardware Acceleration Broken on Geforce FX 5200

Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  Confirmed

Bug description:
  Hardware Acceleration is reported supported by the Nvidia-173 driver
  for this Device.

  on clean install from ubuntu CD, unable to get to unity desktop (blank
  screen with cursor).

  removing Nouveau and installing Nvidia-173 does not remedy the
  problem.

  Garbage on screen during plymouth. No Hardware Acceleration avaiable
  for unity.

  Compiz returning error messages.

  effecting Ubuntu 13.04 12.10 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.card:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:4x 2x 1x
   Registers:0x1f000217:0x1f000104
  .proc.driver.nvidia.agp.host.bridge:
   Host Bridge:  PCI device 8086:1a30
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:4x 2x 1x
   Registers:0x1f000217:0x0104
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 4x
   Fast Writes:  Disabled
   SBA:  Disabled
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  173.14.37  Wed Mar  6 16:56:05 
PST 2013
   GCC version:  gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
  .tmp.unity.support.test.1:

  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 28 11:25:47 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: nvidia-173, 173.14.37, 3.8.0-19-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2013-04-22 (5 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130402.1)
  Lsusb:
   Bus 002 Device 002: ID 12bd:d015
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Vectra
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=9d67f927-723a-409b-b289-263f761640ef ro vesafb.invalid=1 splash 
nomodeset nopat quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2001
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JA.01.04US
  dmi.board.name: HP System Board
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: A08
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Version 1.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJA.01.04US:bd07/19/2001:svnHewlett-Packard:pnHPVectra:pvrVL420:rvnHewlett-Packard:rnHPSystemBoard:rvrA08:cvnHewlett-Packard:ct3:cvrVersion1.00:
  dmi.product.name: HP Vectra
  dmi.product.version: VL420
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 28 11:18:50 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   DFP-0
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: nvidia

To manage notifications about this bug go

[Desktop-packages] [Bug 1293638] Re: quick alt+letter sequence interpretted as "open HUD".

[Tobias]

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

** This bug is no longer a duplicate of bug 1292623
   Alt-F pops up the HUD
** This bug has been marked a duplicate of bug 1287798
   HUD erroneously pops up when not wanted

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

Title:
  quick alt+letter sequence interpretted as "open HUD".

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I press alt + a letter (or any other letter) in quick succession
  the HUD opens (and the key combination is sent to the focused
  application).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140313-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Mar 17 16:39:02 2014
  InstallationDate: Installed on 2014-01-26 (49 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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