date:20190320

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

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

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions

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

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

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"

2019-03-20 Thread Bug Watch Updater

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT. Assertion failure in
  meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode ==
  META_POWER_SAVE_ON"

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally

2019-03-20 Thread Bug Watch Updater

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

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

Title:
  Lock/login screen displays password in clear text occasionally

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

Interesting that errors.ubuntu.com is showing zero reports of this crash
in 19.04, and zero reports in the final release version of Xorg for
18.10 onward. But those same Xorg versions are crashing in 18.04. So I
would have to conclude that this was fixed in mutter in Ubuntu 18.10
onward.

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821126] [NEW] Leading zero in "Programming Mode -> Binary" inserts extra zeros

2019-03-20 Thread Anton Slooten

Public bug reported:

This bug is about inputting data in "Programming Mode -> Binary mode" in
the gnome-calculator snap.

1) 
Description:Ubuntu 18.10
Release:18.10

2) - Its the default snap - so I guess this?

gnome-calculator  3.32.0+git2.cae338ea   352   stable/…
canonical✓  -

3)
When inputting data in binary format, you should be able to lead with an 
arbitrary amount of zeros. When accepting the input (by pressing enter, or 
clicking equals) the answer should be the value you entered (less the leading 
zero)
01001  = 1001
010101001  = 10101001

4)
I you lead your input with zeros and input more than 2 digits (with an obvious 
'1' being in there) there is a large quantity of inserted zero's in the output, 
obviously making the value totally different to what you input.

For instance the input:
01001  = 11
010101001  =101011

However leading with a 1 produces the correct result:
1010  = 1010

The obvious answer is do not lead with a zero. But monkey see monkey do
when inputting data.

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

** Attachment added: "gnome calculator binary bug.png"
   
https://bugs.launchpad.net/bugs/1821126/+attachment/5248102/+files/gnome%20calculator%20binary%20bug.png

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

Title:
  Leading zero in "Programming Mode -> Binary" inserts extra zeros

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1816396] Re: Starting snap from the after-install notification fails

2019-03-20 Thread Robert Ancell

** Description changed:

- Looking to the journal it looks like it's trying to use the wrong
- desktop name, e.g on vlc it gave an error "no such desktop file:
- io.snapcraft.vlc-"
+ [Impact]
+ The launch button on the notification shown after snaps are installed doesn't 
 work.
+ 
+ [Test Case]
+ 1. Open GNOME Software
+ 2. Select a snap that is not installed
+ 3. Install that snap
+ 4. Switch focus to another application (i.e. so GNOME Software doesn't have 
focus)
+ 
+ Expected result:
+ A notification is shown saying the app is installed with a button that 
launches it.
+ 
+ Observed result:
+ A notification is shown but the launch button give an error like "no such 
desktop file: io.snapcraft.vlc-"
+ 
+ [Regression Potential]
+ TBD

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

Title:
  Starting snap from the after-install notification fails

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally

** No longer affects: gdm3 (Ubuntu)

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/460
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.gnome.org/GNOME/gdm/issues/305
- 
- ---
- 
  Hello, folks,
  
  Today when I returned to my computer (which I locked with Super+L) and
  attempted to unlock it, it displayed my passphrase in cleartext in the
  'Password' box. I noticed as soon as I got the first character in, then
  typed in the second character and it stayed clear. I then picked up my
  phone to record the attached video and while I was fiddling with it to
  get a good camera shot, the screen locked (for inactivity perhaps?) and
  when I unlocked this time, the password only displayed as dots (as
  expected).
  
  So unfortunately, I don't know how to replicate. It _did_ occur though,
  as the attached video will show if you go slowly (look for "hu", the
  first characters of legendary password "hunter2").
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 20:27:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Dell HD Graphics 630 [1028:07a1]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
     Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002]
  InstallationDate: Installed on 2018-05-02 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc.
   Bus 001 Device 002: ID 046d:c338 Logitech, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.9
  dmi.board.name: 0NW6H5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7050
  dmi.sys.vendor: Dell Inc.
  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.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

** No longer affects: mutter (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Lock/login screen displays password in clear text occasionally

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally

2019-03-20 Thread Alex Murray

https://gitlab.gnome.org/GNOME/gnome-shell/issues/460#note_331931 seems
to offer a pretty compelling explanation of why this might be seen
inadvertently.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #460
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/460

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

Title:
  Lock/login screen displays password in clear text occasionally

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

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

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

Title:
  monitors.xml is not parsed or applied correctly during login after
  reboot or shutdown

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items

And upstream has proposed a fix already :)

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/467

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1094
   Importance: Unknown
   Status: Unknown

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

** Tags added: visual-quality

** Summary changed:

- gnome-shell's user menu/item is not aligned like other menu items
+ gnome-shell's user menu/item is not aligned like other menu items (if 
extensions are installed that add menu buttons)

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

Title:
  gnome-shell's user menu/item is not aligned like other menu items (if
  extensions are installed that add menu buttons)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

** Also affects: gst-plugins-good via
   https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579
   Importance: Unknown
   Status: Unknown

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

Title:
  totem comma key does not go 1 frame back ["gst_segment_do_seek:
  assertion 'start <= stop' failed"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1820883/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard.

** Tags removed: artful
** Tags added: bionic

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'. | This was previously supported, but is not correct
  according to the ES6 standard.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821003] Re: Screen locking issue

2019-03-20 Thread Alex Murray

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

** This bug has been marked a duplicate of bug 1772791
   Lock/login screen displays password in clear text occasionally

** Information type changed from Private Security to Public Security

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

Title:
  Screen locking issue

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

2019-03-20 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Expired => New

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1767817] Re: Full text search does not work

2019-03-20 Thread Fernando

1:3.26.4-0~ubuntu18.04.4 also fixed this bug for me in Bionic, thanks!

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

Title:
  Full text search does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions

> that runs a very high risk of either being disruptive to the release

Hum, my understanding is that it is basically be a no-op unless the
gsettings key is set? If so I see the risk for the release being low,
'go enable an experimental gsettings key and restart your session'
doesn't sound like a release problem, users opting for experimental
options get what they ask for?

> A PPA seems like the right place to handle distributing such
experimental features to people.

That doesn't have the same "easy to try" nor PR potential, it also can't
be described as part of the release...

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821012] Re: can t run snap gnome-system-monitor

2019-03-20 Thread HankB

The snap is now working. (In other words, not able to reproduce.)
I'm not sure what made the change but I did reboot several times.

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

Title:
  can t run snap gnome-system-monitor

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions

2019-03-20 Thread Iain Lane

This is a *great* feature that it'd be really cool for Ubuntu to have
and I'm very pleased that the team has been working on it, but...

I really don't feel very good about this freeze exception request. It
doesn't seem right to me to be adding unmerged, experimental and
unfinished features into the release - especially so late on.

It is going to need iteration either before or after the release and
that runs a very high risk of either being disruptive to the release
(making updates to the altered packages potentially more difficult if
they need to be changed for other reasons), taking up time of the
release/SRU teams having to review changes, or (if iterations aren't
included in disco) the package in the release being behind the latest
developments meaning that it ends up not being as useful to people as it
could be — known bugs will be fixed in the development branches but not
in disco.

A PPA seems like the right place to handle distributing such
experimental features to people. Testing things is one thing that PPAs
are for, and any publicity that you want to do around this feature could
have upgrading via `add-apt-repository` as its first step. Such a PPA
could even live under an uploading team like ~ubuntu-desktop to make it
seem more official if you wanted.

There's no problem with ubuntu/disco-x-fractional branches being created
in the packaging repositories, to make handling the PPA easier.

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard.

2019-03-20 Thread lotuspsychje

Ubuntu 18.04.2 up to date at 20/3/2019

getting similar warnings:

Mar 20 19:57:28 RooTBooK gnome-shell[2561]: Some code accessed the
property 'WindowPreviewMenu' on the module 'windowPreview'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'. | This was previously supported, but is not correct
  according to the ES6 standard.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1770299] Re: Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

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

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

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

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

Title:
  Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-03-20 Thread Apport retracing service

** Tags added: disco

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821051] Re: totem crashed with signal 5

2019-03-20 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1758287
   totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821051] [NEW] totem crashed with signal 5

2019-03-20 Thread corrado venturini

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

Public bug reported:

Open a .webm video clicking on it, click on the '<' icon top left ...
crash

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 18:29:10 2019
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2019-03-14 (6 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
 ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
 ?? () from /lib/x86_64-linux-gnu/libGLX.so.0
 ?? () from /lib/x86_64-linux-gnu/libGLX.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
separator:

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


** Tags: amd64 apport-crash disco

** Information type changed from Private to Public

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

Title:
  totem crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820904] Re: Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04

2019-03-20 Thread Qianqian Fang

would it be possible to find out which update fixed this issue and back
port to 16.04? Majority of my systems (10+ boxes) are on 16.04 because
many things broke (otherwise) on 18.04. I do not plan to upgrade in the
next few years.

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

Title:
  Evince stop rendering text with anti-aliasing after upgrading to
  Ubuntu 16.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820904] Re: Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04

2019-03-20 Thread Qianqian Fang

on another machine running Ubuntu 18.04, the rendering of this PDF looks
normal.

** Attachment added: "sample pdf that failed on 16.04"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1820904/+attachment/5247895/+files/Solving_system_equations_using_math_tools.pdf

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

Title:
  Evince stop rendering text with anti-aliasing after upgrading to
  Ubuntu 16.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821012] Re: can t run snap gnome-system-monitor

Being discussed on https://forum.snapcraft.io/t/cant-run-gnome-system-
monitor-ubuntu-18-04/10495/1

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

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

Title:
  can t run snap gnome-system-monitor

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter

I think the problem here is CUPS' own method of generating temporary
queues for discovered driverless printers. gnome-control-center, and
probably other GUIs, like the GTK print dialog, cannot cope with this.
So we leave this bug report assigned to gnome-control-center for now.

Christian, if you stop cups-browsed you have still auto-generated print
queues. This is because CUPS itself kicks in here.

If you run

lpstat -e

you see queue names which you do not see with

lpstat -v

The extra queue names are temporary CUPS queues. These are created by
CUPS if you try to print on them or to access them in general, and they
are removed by CUPS again after 1 minute of inactivity.

gnome-control-center probably gets completely confused by that. It can
have seen such a queue as actual queue, shortly after such a queue was
used, and added it to its list. Now, more than a minute later, the user
clicks on the entry, the queue is not there any more, and he gets
something unexpected, an error message, an empty option dialog, a
"(null):631".

gnome-control-center and all other printing GUIs need to be adapted to
CUPS' temporary print queues.

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

Title:
"driverless" printer workflow has bad usability/ is partly broken

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter

Christian, both your attached PPD files are auto-generated, and both
pass cupstestppd.

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-03-20 Thread Chris Rainey

I find that primary(left-clicking) up to 15 or 20+ times _eventually_
spawns the pkexec-gui box.


On Wed, Mar 20, 2019 at 9:26 AM Bjoern H. <1727...@bugs.launchpad.net>
wrote:

> I have this issue both in 18.10 and 19.04. Using arrows and space does
> not work, the only workaround I've found is "sudo software-properties-
> gtk". Would be happy to provide any details that could be useful.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1727908
>
> Title:
>   Software & Updates application does not permit changes on the "Other
>   Software" tab
>
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in software-properties package in Ubuntu:
>   Confirmed
>
> Bug description:
>
>   On the "Other Software" tab, I am unable to select "Canonical Partners".
>   Similarly, the other checkboxes on the "Other Software" can not be
> clicked.
>   Clicking on a checkbox has no effect, and a dialog requesting the admin
> password is not presented.
>
>   However, activating or deactivating checkboxes on other tabs causes an
>   authorization dialog to be presented to the user.
>
>   I experience this bug in an an Xorg session.
>
>   sources.list and sources.list.d have the following permissions:
>   -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
>   drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d
>
>   All files in sources.list.d have the following permissions as this
> example:
>   -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list
>
>   $ lsb_release -rd
>   Description:  Ubuntu 17.10
>   Release:  17.10
>
>   $ apt-cache policy software-properties-gtk
>   software-properties-gtk:
> Installed: 0.96.24.17
> Candidate: 0.96.24.17
> Version table:
>*** 0.96.24.17 500
>   500 http://us.archive.ubuntu.com/ubuntu artful/main amd64
> Packages
>   500 http://us.archive.ubuntu.com/ubuntu artful/main i386
> Packages
>   100 /var/lib/dpkg/status
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: software-properties-gtk 0.96.24.17
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3.1
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Oct 26 22:45:09 2017
>   InstallationDate: Installed on 2017-10-26 (1 days ago)
>   InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful
> Aardvark"
>   PackageArchitecture: all
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: software-properties
>   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/1727908/+subscriptions
>

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter

Christian, first, it seems that you did "cupstestppd" on a PPD file
which is not auto-generated:

--
$ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd
/etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate
CustomBox *Option18 SDCard".
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*Option18
SDCard *KCCollate CustomBox".
WARN Datei einthält gemischt CR, LF, und CR LF Zeilenmenden.
WARN Size "A5" should be "149x210mm".
WARN Size "A6" should be "105x149mm".
WARN Size "B6" should be "128x182mm".
WARN Size "OficioII" should be the Adobe standard name
"FanFoldGermanLegal".
WARN Size "P16K" should be "7,75x10,75".
WARN Size "OficioMX" should be the Adobe standard name "Oficio".
--

This seems to be from a manufacturer-supplied PPD file. The auto-
generated ones do not have "UIConstraints" lines. They also do not
contain mixed line ends.

Also sorry for giving you a wrong "ipptool" command line. Please run the
command line

ipptool -tv ipp://KM15881D.local:631/ipp/print get-printer-
attributes.test > ~/attrs.txt

The file get-printer-attributes-2.0.test only came with a later CUPS
version.

Please attach the attrs.txt file.

*.O files are generated by CUPS, to put the original version of a PPD
file when they change or replace it. Only the files without ".O" are
relevant for their print queue.

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

Title:
"driverless" printer workflow has bad usability/ is partly broken

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821019] [NEW] gnome-terminal does not gain focus upon launch

2019-03-20 Thread Brian Curtis

Public bug reported:

Ubuntu 19.04, 64 bit machine, nvidia graphics drivers

Upon first and subsequent launches of gnome-terminal the window shows
but does not immediately gain focus to start typing in commands.

I expect it to immediately gain focus to type commands upon launch each
and every time.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-terminal 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 10:40:18 2019
InstallationDate: Installed on 2018-03-02 (382 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  gnome-terminal does not gain focus upon launch

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

2019-03-20 Thread Chris Rainey

** Description changed:

- WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
- screensaver + numlockx(optionally)
+ WORKAROUND
+ 
+ Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver +
+ numlockx(optionally)
+ 
  
  TL;DR
+ 
+ Correct positioning and working of multiple displays until reboot or
+ shutdown and then subsequent login from gdm3. HDMI monitor(projector)
+ goes blank and the VGA monitor only shows 'Secondary' monitor screen
+ without any user visible controls or windows as they are all being
+ painted to the now blanked 'Primary' HDMI connected display.
+ 
+ 
+ REPRODUCTION
  
  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting
  a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a FHD
  projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
- monitor setup in my current session. However, upon a reboot or power
- cycle of the computer and a successful login from GDM(gdm3), the HDMI
- goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even
- though I set it as 'Primary' in the "Displays" dialog. The monitors.xml
- file, attached, shows the correct layout and survives the reboot without
- alteration. I am unable to see anything on the 'Primary' display, which
- has incorrectly been given to the  HDMI projector. Unseating the HDMI
- cable does not restore the VGA to 'Primary' display automatically and I
- must reboot the computer while leaving the HDMI unplugged in order to
- restore my ability to see the 'Primary' display on the VGA connection.
+ monitor setup in my current session.
+ 
+ However, after a reboot or power cycle of the computer and a successful
+ login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor
+ shows as 'Secondary' monitor even though I set it as 'Primary' in the
+ "Displays" dialog.
+ 
+ The monitors.xml file, attached, shows the correct layout and survives
+ the reboot without alteration.
+ 
+ I am unable to see anything on the 'Primary' display, which has
+ incorrectly been given to the HDMI projector. Unseating the HDMI cable
+ does not restore the VGA to 'Primary' display automatically and I must
+ reboot the computer while leaving the HDMI unplugged in order to restore
+ my ability to see the 'Primary' display on the VGA connection.
+ 
  Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is
  repeatedly provable through multiple reboots or changes to the logical
  layout of the screens in the 'Displays' settings of gnome-control-
  center.
  
- ERRORS(syslog) = "Failed to get current display configuration state:
+ 
+ ERRORS(syslog)
+ 
+ "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"
  
  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17
  
- CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP
- Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA
- as primary monitor and HDMI(wireless Tx) as secondary to projector and
- then apply custom monitor positioning using g-c-c "Displays" panel.
- 
- RESULT = correct positioning and working of multiple displays until
- reboot or shutdown and then subsequent login from gdm3. HDMI
- monitor(projector) goes blank and the VGA monitor only shows 'Secondary'
- monitor screen without any user visible controls or windows as they are
- all being painted to the now blanked 'Primary' HDMI connected display.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  WORKAROUND
  
  Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver +
  numlockx(optionally)
  
  
  TL;DR
  
  Correct positioning and working of multiple displays until reboot or
  shutdown and then subsequent login from gdm3. HDMI monitor(projector)
  goes blank and the VGA monitor only shows 'Secondary' monitor screen
  without any user visible

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-03-20 Thread Bjoern H.

I have this issue both in 18.10 and 19.04. Using arrows and space does
not work, the only workaround I've found is "sudo software-properties-
gtk". Would be happy to provide any details that could be useful.

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821012] [NEW] can t run snap gnome-system-monitor

2019-03-20 Thread HankB

Public bug reported:

Can't run from 'gnome find' - nothing happens.
Try to run from terminal - get this:

hbarta@karakum:~$ gnome-system-monitor 
You need to connect this snap to the gnome platform snap.

You can do this with those commands:
snap install gnome-3-26-1604
snap connect gnome-system-monitor:gnome-3-26-1604 gnome-3-26-1604

(the '3-26-1604' number defines the platform version and might change)
hbarta@karakum:~$ 
hbarta@karakum:~$ snap install gnome-3-26-1604
snap "gnome-3-26-1604" is already installed, see 'snap help refresh'
hbarta@karakum:~$ snap connect gnome-system-monitor:gnome-3-26-1604 
gnome-3-26-1604
error: snap "gnome-system-monitor" has no plug named "gnome-3-26-1604"
hbarta@karakum:~$ 

Remove snap, install deb - runs OK.

Remove deb, install snap (with intent to see if this fixes the issue or
to file a bug report) and now get

hbarta@karakum:~$ gnome-system-monitor
Failed to register: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.112" (uid=1000 pid=10105 
comm="gnome-system-monitor " 
label="snap.gnome-system-monitor.gnome-system-monitor (enforce)") 
interface="org.gtk.Actions" member="DescribeAll" error name="(unset)" 
requested_reply="0" destination="org.gnome.SystemMonitor" (uid=1000 pid=3975 
comm="gnome-system-monitor " label="unconfined")
hbarta@karakum:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-system-monitor (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 20 09:05:16 2019
InstallationDate: Installed on 2019-01-30 (48 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  can t run snap gnome-system-monitor

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1821014] [NEW] budgie-wm crashes sometimes

2019-03-20 Thread David Kedves

Public bug reported:

Sometimes it crashes, i think i was trying to move a window to the right
side of the screen when this happened.

Backtrace:
sudo gdb /usr/bin/budgie-wm /tmp/coredump.budgie-wm.12829.kedz-i7s850.1553090616
GNU gdb (Ubuntu 8.2-0ubuntu1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/budgie-wm...Reading symbols from 
/usr/lib/debug/.build-id/4b/fb3bfed09d0116b7a46bbe32d4a9546a9c12d4.debug...done.
done.
[New LWP 12829]
[New LWP 12841]
[New LWP 12842]
[New LWP 12934]
[New LWP 12933]
[New LWP 12839]
[New LWP 16576]
[New LWP 12940]
[New LWP 12935]
[New LWP 12936]
[New LWP 12938]
[New LWP 12937]
[New LWP 12939]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `budgie-wm'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  _cogl_unpack_bgra__8 (width=, dst=0x55eca12b3b90 "", 
src=0x7fc51f384000 )
at cogl-bitmap-packing.h:143
143 cogl-bitmap-packing.h: No such file or directory.
[Current thread is 1 (Thread 0x7fc569925f40 (LWP 12829))]
(gdb) back
#0  0x7fc56fecb210 in _cogl_unpack_bgra__8
(width=, dst=0x55eca12b3b90 "", src=0x7fc51f384000 ) at cogl-bitmap-packing.h:143
#1  0x7fc56fecb210 in _cogl_unpack_8
(width=1808, dst=0x55eca12b35d0 "\016A\020\b", src=0x7fc51f383a40 
"\020A\016\bd", format=COGL_PIXEL_FORMAT_BGRA__PRE) at 
cogl-bitmap-packing.h:362
#2  0x7fc56fecb210 in _cogl_bitmap_convert_into_bitmap
(src_bmp=src_bmp@entry=0x55ec9f8c2ac0, 
dst_bmp=dst_bmp@entry=0x7fc55c006a30, error=error@entry=0x7fffddb7e818) at 
cogl-bitmap-conversion.c:454
#3  0x7fc56fecc2fc in _cogl_bitmap_convert
(src_bmp=0x55ec9f8c2ac0, dst_format=COGL_PIXEL_FORMAT_RGB_888, 
error=0x7fffddb7e818)
at cogl-bitmap-conversion.c:509
#4  0x7fc56fecc446 in _cogl_bitmap_convert_for_upload
(src_bmp=src_bmp@entry=0x55ec9f8c2ac0, internal_format=, 
can_convert_in_place=can_convert_in_place@entry=0, 
error=error@entry=0x7fffddb7e818) at cogl-bitmap-conversion.c:610
#5  0x7fc56feb2d68 in _cogl_texture_2d_gl_copy_from_bitmap
(tex_2d=0x55ec9f7fdf10, src_x=0, src_y=0, width=1808, height=784, 
bmp=0x55ec9f8c2ac0, dst_x=0, dst_y=0, level=0, error=0x7fffddb7e818) at 
driver/gl/cogl-texture-2d-gl.c:765
#6  0x7fc56feeb5c5 in _cogl_texture_2d_set_region
(tex=0x55ec9f7fdf10, src_x=, src_y=, 
dst_x=, dst_y=, width=, 
height=784, level=0, bmp=0x55ec9f8c2ac0, error=0x7fffddb7e818)
at cogl-texture-2d.c:613
#7  0x7fc56feeb014 in _cogl_texture_set_region
(texture=0x55ec9f7fdf10, width=width@entry=1808, height=height@entry=784, 
format=format@entry=COGL_PIXEL_FORMAT_BGRA__PRE, rowstride=, 
data=, dst_x=0, dst_y=0, level=0, error=0x7fffddb7e818) at 
cogl-texture.c:464
#8  0x7fc56ff084d4 in _cogl_texture_pixmap_x11_update_image_texture 
(tex_pixmap=0x55ec9f7fde00)
at winsys/cogl-texture-pixmap-x11.c:747
#9  0x7fc56ff084d4 in _cogl_texture_pixmap_x11_update
(tex_pixmap=0x55ec9f7fde00, needs_mipmap=) at 
winsys/cogl-texture-pixmap-x11.c:804
#10 0x7fc56ff08b03 in _cogl_texture_pixmap_x11_pre_paint 
(tex=0x55ec9f7fde00, flags=(unknown: 0))
at winsys/cogl-texture-pixmap-x11.c:1051
#11 0x7fc56feddded in _cogl_pipeline_layer_pre_paint (layer=0x55eca12f4030)
at cogl-pipeline-layer.c:864
#12 0x7fc56fedc197 in _cogl_pipeline_pre_paint_for_layer
(pipeline=pipeline@entry=0x55eca130bbe0, layer_id=layer_id@entry=0) at 
cogl-pipeline.c:2607
#13 0x7fc56fecc46b in _cogl_rectangles_validate_layer_cb
(pipeline=0x55eca130bbe0, layer_index=0, user_data=0x7fffddb7e9b0) at 
cogl-primitives.c:542
#14 0x7fc56fedaa09 in cogl_pipeline_foreach_layer
(pipeline=pipeline@entry=0x55eca130bbe0, 
callback=callback@entry=0x7fc56fecc450 <_cogl_rectangles_validate_layer_cb>, 
user_data=user_data@entry=0x7fffddb7e9b0) at cogl-pipeline.c:735
#15 0x7fc56feccd31 in _cogl_framebuffer_draw_multitextured_rectangles
(framebuffer=framebuffer@entry=0x55ec9f416e50, 
pipeline=pipeline@entry=0x55eca130bbe0, rects=rects@entry=0x7fffddb7ea70, 
n_rects=n_rects@entry=1, disable_legacy_state=disable_legacy_state@entry=1)
at cogl-primitives.c:658
#16 0x7fc56fefa9b1 in cogl_framebuffer_draw_multitextured_rectangle

[Bug 1820232] Re: [MIR] zeromq3 as dependency of mailman3

2019-03-20 Thread Christian Ehrhardt 

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

Thanks Andreas, also I now have taken a look at the demotion.
The only reason to demote is was that the need from unity to pull it in went 
away.
There was no explicit demotion reason filed.

Therefore we can piggy-back on the old MIR and can close this one as
dup.

** This bug has been marked a duplicate of bug 1597439
   [MIR] zeromq3

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

Title:
  [MIR] zeromq3 as dependency of mailman3

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items

2019-03-20 Thread shemgp

Filed upstream at: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1094

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1094
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1094

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

Title:
  gnome-shell's user menu/item is not aligned like other menu items

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1816264] Re: software center stuck on Chrome package dialog

2019-03-20 Thread Olivier Tilloy

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

That's bug #1798053, which was fixed in gnome-software 3.30.2-0ubuntu8.
Just install the latest updates in your VM.

** This bug has been marked a duplicate of bug 1798053
   [SRU] Click on the back icon in gnome-software doesn't work

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

Title:
  software center stuck on Chrome package dialog

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

Thank you for your bug report. Confirmed and sent upstream
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579

** Bug watch added: gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues 
#579
   https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Triaged

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

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

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

Title:
  totem comma key does not go 1 frame back ["gst_segment_do_seek:
  assertion 'start <= stop' failed"]

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1816264] Re: software center stuck on Chrome package dialog

Well, I still can't reproduce with those steps :/ When the new dialog
opens in 6-7 it's the main windows and not the details from the previous
step, such there is no < to use...

The warning might give a clue to someone looking at the problem though
(ideally it should be reported upstream)

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

Title:
  software center stuck on Chrome package dialog

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

Jonas, that is bug 1812527 you have. Please comment in bug 1812527
instead.

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

Nikolay,

Please follow the steps in comment #9.

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820904] Re: Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04

Thank you for your bug report. What desktop environment do you use? Does
this happen on any document? Could you try on newer ubuntu series?

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

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

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

Title:
  Evince stop rendering text with anti-aliasing after upgrading to
  Ubuntu 16.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-03-20 Thread Jonas Stenberg

Re-pasting attachment cleaned from sensitive data.

** Attachment removed: "Part of syslog when gnome crash occured"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+attachment/5247755/+files/syslog_gnome_crash.txt

** Attachment added: "Part of syslog when gnome crash occured"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+attachment/5247779/+files/syslog_gnome_crash.txt

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

2019-03-20 Thread Mitchell Clifford

Sure, here's my Xorg.log


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+attachment/5247765/+files/Xorg.0.log

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

Title:
  (xorg) multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

Jonas, that is bug 1812527 you have. Please comment in bug 1812527
instead.

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1820936] Re: When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux"

2019-03-20 Thread Pedro

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

Yes, I think it is the same bug, just happen in different application.

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

Title:
  When I switch workspace, gnome-shell will have a very high chance of
  crashing, especially running "PlayOnLinux"

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-03-20 Thread Jonas Stenberg

I have exactly the same problem but it only happens when I talk to
people that uses Windows on their desktop. I attached a section of my
syslog where this happened.

** Attachment added: "Part of syslog when gnome crash occured"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+attachment/5247755/+files/syslog_gnome_crash.txt

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 551863] Re: Save dialog exhibits unhelpful behaviour after opening a folder