[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps

2020-04-05 Thread Theo
Suddenly affected by this on Ubuntu 16.04. It just showed up yesterday
without changing anything. I have the issue when converting CR2 files to
jpeg through Shotwell.

Removing the ICC_PROFILE does not work for me.

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

Title:
  Images are washed out or colors are skewed in some apps

Status in Eye of GNOME:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

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

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


[Desktop-packages] [Bug 1857328] Re: Thunar closes down when Rename -> Find and replace text. No error message. It just closes.

2020-01-07 Thread Theo Linkspfeifer
Thunar uses different wording, so this is actually a bug in Nautilus.

** Package changed: thunar (Ubuntu) => nautilus (Ubuntu)

** Summary changed:

- Thunar closes down when Rename -> Find and replace text. No error message. It 
just closes.
+ Nautilus closes down when Rename -> Find and replace text. No error message. 
It just closes.

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

Title:
  Nautilus closes down when Rename -> Find and replace text. No error
  message. It just closes.

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  thunar:
  Installed: 1.8.9-1
  Candidate: 1.8.9-1
  Version table:
  *** 1.8.9-1 500
  500 http://es.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages   
100 /var/lib/dpkg/status

  
  What I do:
  I select several files.
  I right click and choose "rename".
  I "rename using a template".
  This works perfectly.

  I tick "Find and replace text".
  About 1 time in 3 thunar simply closes. There is no error message or an offer 
to send a bug report. The application simply closes down completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunar 1.8.9-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 09:52:57 2019
  InstallationDate: Installed on 2019-12-13 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1765775] Re: Window decoration becomes very large if the image has much more height than width

2019-11-15 Thread Theo Linkspfeifer
The bug is in GTK3.

https://gitlab.gnome.org/GNOME/eog/issues/4
https://gitlab.gnome.org/GNOME/gtk/issues/657

** Bug watch added: gitlab.gnome.org/GNOME/eog/issues #4
   https://gitlab.gnome.org/GNOME/eog/issues/4

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #657
   https://gitlab.gnome.org/GNOME/gtk/issues/657

** Package changed: xfce (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Window decoration becomes very large if the image has much more height
  than width

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  When a image with much higher height than width is opened, the window
  decoration becomes very big, as it tries to keep the image
  proportional: https://i.imgur.com/SZu0lOk.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 20 13:08:37 2018
  InstallationDate: Installed on 2017-06-13 (310 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: eog
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

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


[Desktop-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked

2019-11-07 Thread Theo Linkspfeifer
I suggest that you upgrade to 19.10 and replace light-locker with the
new xfce4-screensaver.

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

Title:
  [nouveau][XFCE] Do not see login screen after screen is blanked

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
  InstallationDate: Installed on 2018-09-03 (263 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: U
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right

2019-08-11 Thread Theo Shaw
For what it's worth I'm getting a very similar issue on Linux Mint
Cinnamon after the update from 19.1 to 19.2. The error is:

 cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
bottom >= 1' failed.

I've found that the positions of monitors in a dual monitor setup
dictates whether or not the DE crashes on startup. See this thread:
https://github.com/linuxmint/cinnamon/issues/8754 Hopefully the problem
is identical for you guys and a patch can fix both issues at once.

** Bug watch added: github.com/linuxmint/cinnamon/issues #8754
   https://github.com/linuxmint/cinnamon/issues/8754

** Also affects: cinnamon (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/1837087

Title:
  gnome-shell crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

Status in cinnamon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

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

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

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


[Desktop-packages] [Bug 1835622] Re: Cannot start desktop session with compositor enabled

2019-07-10 Thread Theo Linkspfeifer
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Cannot start desktop session with compositor enabled

Status in Xfwm4:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xfwm4 package in Ubuntu:
  New

Bug description:
  I cannot login to the Xfce desktop session anymore. in ~/.xsession-
  errors there's the message:

  xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285:
  intel_miptree_match_image: Assertion `image->TexObject->Target ==
  mt->target' failed.

  Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0.

  I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA
  with xfwm4 4.13.3

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

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


[Desktop-packages] [Bug 1822380] Re: Thunar right-click menu not expanded

2019-06-16 Thread Theo Linkspfeifer
A workaround is not a proper fix. Would it not make more sense to revert
the GTK commit which broke the menu behavior?

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Thunar right-click menu not expanded

Status in GTK+:
  New
Status in Thunar File Manager:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  New
Status in thunar package in Ubuntu:
  Fix Released

Bug description:
  Submitting this bug report with the SRU template, but hopefully we can
  go ahead have this uploaded before the final images have been built.

  [Impact]

   * The "Create Document" submenu in Thunar does not expand to a usable length.
   
   * The submenu is displayed at just a few pixels tall, enough to see menu 
items as you scroll, but not enough to read any item.
   
   * This breaks a standard use case for file managers: creating new files.
   
   * The proposed upload fixes the bug by loading the menu items synchronously, 
making the menu load with the items already populated instead of having to 
redraw once the items are added.
   
   * The patch provided comes from the upstream maintainer.

  [Test Case]

   * Open Thunar.
   
   * Right click in the blank space (not on an item).
   
   * Move the cursor to the "Create Document" menu.
 * Bug Present: The submenu is displayed but short, and no items are 
visible.
 * Bug Resolved: The submenu is displayed, items present in the ~/Templates 
folder are displayed.

  [Regression Potential]

   * Regression potential is minimal:
 * The modified code affects only the drawing of the submenu items.
 * The submenu is already ununsable, no items are displayed.
 
   * Some limited testing has already been completed:
 * 2 users confirmed the patch fixes the issue on the upstream bug report.
 * 2 Xubuntu team members (bluesabre, Unit193) have also confirmed the 
patch and no regressions.

  [Original Report]
   
  In Thunar, when I right click to create a new file, the menu shows up so 
small that I can't see the options. I have rebooted and the problem persists. 
Haven't checked other file managers yet. Running Xubuntu 19.04 (Development 
Branch), Thunar 1.8.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: thunar 1.8.4-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 16:41:29 2019
  InstallationDate: Installed on 2019-03-29 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration

2019-05-06 Thread Theo Linkspfeifer
** Package changed: xfwm4 (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Ubuntu 18.10 broke dual-screen dual-desktop configuration

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I'm running Xubuntu.  I finally reported this problem to the Xfce
  group and received this response:

  "As arandr/xrandr does not detect correctly your 2nd screen, this
  seems that it is not related directly to Xfce, but a bug in Xubuntu
  stack.  Can you please open a bug on Xubuntu project if the issue is
  still present for you?"

  Thus this bug report.

  
  I've been running Xubuntu for years with two monitors, each running an 
independent xfce4 desktop -- i.e., configured without Xinerama. This has worked 
fine for every upgrade through 18.04.  When upgrading to 18.10, something 
significant changed and the the second monitor (display :0.1) was disabled.  
After much reading and work, I have only been able to restore some extremely 
hobbled functionality.  I am unable to get a second xfce4-desktop, panel or 
window manager running on the second screen.  I have assembled detailed 
screenshots and command output at the following link:

  http://smallthoughts.com/xfce/xfce.html

  I'm using an NVIDIA Quadro K-4000 graphics card and no hardware
  changes were made between 18.04 and 18.10.

  The nvidia-settings tool reports both monitors active (as configured
  in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr
  tools each show only one display (although xrandr can be forced to
  report on the second display.  See full documentation at the above
  link.)

  What changed in the latest release, and what needs to be done to get
  the second monitor running a second desktop once again?  I have been
  struggling with this for many months now and it has severely impacted
  the use of my system.  As a new release of Ubuntu in coming, I would
  appreciate it if this could be prioritized and addressed as quickly as
  possible.

  I will provide additional information upon request.

  P.S.:  There is really no documentation available on running multiple
  desktops on separate screens when Xinerama is not used to tie the
  screens together into a single desktop.  This is a common
  configuration and I would like to request that as part of the solution
  to this problem, the setup steps be documented and this multi-desktop
  configuration be made a standard part of the development and testing
  process for each Ubuntu release.

  13-> lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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


[Desktop-packages] [Bug 1631715] Re: Password required twice returning from suspend

2019-03-25 Thread Theo Linkspfeifer
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Password required twice returning from suspend

Status in light-locker package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Clean install - no updates available.

  Suspend machine and restart.

  Lock screen requiring password - enter password and return to
  suspended desktop.

  Within a few seconds machine locks and password is required once more.

  Appears to depend on how fast I enter the password the first time.

  Using the same hardware I've installed nvidia 340.96 and tried to
  reproduce the issue without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: light-locker 1.7.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Oct  9 09:15:38 2016
  InstallationDate: Installed on 2016-10-09 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Theo Linkspfeifer
No changes were made to xubuntu-core and xubuntu-desktop yet, so the bug
is obviously not fixed yet. However, the part regarding xfce4-session
was fixed (should not pull in xscreensaver anymore).

** Changed in: xfce4-session (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2019-02-15 Thread Theo Linkspfeifer
I assume that adding the exo package to the Affects list should do. The
upstream report has already been linked.

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

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

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in exo:
  Confirmed
Status in exo package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1816027] Re: Aborted Scanning in SimpleScan and later xubuntu freeses

2019-02-15 Thread Theo Linkspfeifer
** Package changed: xfce4-terminal (Ubuntu) => simple-scan (Ubuntu)

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

Title:
  Aborted Scanning in SimpleScan and later xubuntu freeses

Status in simple-scan package in Ubuntu:
  New

Bug description:
  I don't have much information.
  - My xubuntu system 18.04 freeses and the last thing I did was aborting 
scanning while scanning was started some seconds ago. Some time later I could 
not use SimpleScan anymore and soon it was getting worse.
  - The top panel containing my started applications doesn't respond, clicking 
doesn't help
  - Will have to hard reset my system.

  TODO:
  Type Alt + F2 and type ubuntu-bug nameofprogram. ...
  After running one of the above commands, Ubuntu will gather information about 
the bug. ...
  A new web browser tab will open to continue processing the bug data. ...
  After logging in to Launchpad, enter a description of the problem in the 
summary field.

  Result:
  Alt-F2 and selected SimpleScan in drop down
  Nothing happened, no new browser tab with info generated 

  Then I did : ubuntu-bug -x  ===> Don't see extra info

  Got message : Extra debug information will be added to the bug report
  automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfce4-terminal 0.8.7.4-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 15 11:37:20 2019
  ExecutablePath: /usr/bin/xfce4-terminal
  InstallationDate: Installed on 2018-04-15 (305 days ago)
  InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xfce4-terminal
  UpgradeStatus: Upgraded to bionic on 2018-08-02 (196 days ago)

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

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


[Desktop-packages] [Bug 1787989] Re: adwaita icon them not found

2019-02-02 Thread Theo Linkspfeifer
This was fixed upstream.

https://github.com/shimmerproject/elementary-
xfce/commit/25ff77b020be948e6ad8fed783aaa87c1184d839

** Package changed: adwaita-icon-theme (Ubuntu) => elementary-xfce
(Ubuntu)

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

Title:
  adwaita icon them not found

Status in elementary-xfce package in Ubuntu:
  Confirmed

Bug description:
  The installed version is xubuntu 18.04 fully updated

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy kphotoalbum
  kphotoalbum:
Installé : 5.3-1
Candidat : 5.3-1
   Table de version :
   *** 5.3-1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  When launched from shell, kphotoalbum indicate : 
  Icon theme "adwaita" not found.

  As a result, there's missing icons on kphotoalbum
  Expected result is to have all icons displayed on kphotoalbum

  The following package are installed :

  $ apt list --installed | grep adwaita
  adwaita-icon-theme/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-icon-theme-full/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-qt/bionic,now 1.0-2 amd64  [installé]

  $ apt list --installed | grep gtk
  adobe-flash-properties-gtk/bionic,now 1:20180814.1-0ubuntu0.18.04.2 amd64  
[installé, automatique]
  apport-gtk/bionic-security,bionic-security,now 2.20.9-0ubuntu7.1 all  
[installé]
  gir1.2-gtk-3.0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gir1.2-gtkclutter-1.0/bionic,now 1.8.4-3 amd64  [installé]
  gir1.2-gtksource-3.0/bionic,now 3.24.7-1 amd64  [installé, automatique]
  gir1.2-javascriptcoregtk-4.0/bionic-security,now 2.20.5-0ubuntu0.18.04.1 
amd64  [installé]
  greybird-gtk-theme/bionic,bionic,now 3.22.8-1 all  [installé]
  gstreamer1.0-gtk3/bionic,now 1.14.0-1ubuntu1 amd64  [installé, automatique]
  gtk-update-icon-cache/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gtk2-engines-murrine/bionic,now 0.98.2-2ubuntu1 amd64  [installé]
  gtk2-engines-pixbuf/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libcanberra-gtk3-0/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libcanberra-gtk3-module/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libclutter-gtk-1.0-0/bionic,now 1.8.4-3 amd64  [installé]
  libdbusmenu-gtk3-4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  
[installé]
  libdbusmenu-gtk4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  [installé]
  libgtk-3-0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-bin/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-common/bionic,bionic,now 3.22.30-1ubuntu1 all  [installé]
  libgtk2-perl/bionic,now 2:1.24992-1build1 amd64  [installé, automatique]
  libgtk2.0-0/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-bin/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-common/bionic,bionic,now 2.24.32-1ubuntu1 all  [installé]
  libgtk3-perl/bionic,bionic,now 0.032-1 all  [installé]
  libgtkmm-2.4-1v5/bionic,now 1:2.24.5-2 amd64  [installé, automatique]
  libgtkmm-3.0-1v5/bionic,now 3.22.2-2 amd64  [installé]
  libgtksourceview-3.0-1/bionic,now 3.24.7-1 amd64  [installé]
  libgtksourceview-3.0-common/bionic,bionic,now 3.24.7-1 all  [installé]
  libgtkspell0/bionic,now 2.0.16-1.2 amd64  [installé]
  libjavascriptcoregtk-4.0-18/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64 
 [installé]
  libreoffice-gtk3/bionic,now 1:6.0.3-0ubuntu1 amd64  [installé]
  libwebkit2gtk-4.0-37/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64  
[installé]
  libwxgtk3.0-0v5/bionic,now 3.0.4+dfsg-3 amd64  [installé, automatique]
  lightdm-gtk-greeter/bionic,now 2.0.5-0ubuntu1 amd64  [installé]
  lightdm-gtk-greeter-settings/bionic,bionic,now 1.2.2-1 all  [installé]
  numix-gtk-theme/bionic,bionic,now 2.6.7-3 all  [installé]
  pinentry-gtk2/bionic,now 1.1.0-1 amd64  [installé]
  python-gtk2/bionic,now 2.24.0-5.1ubuntu2 amd64  [installé, automatique]
  python3-aptdaemon.gtk3widgets/bionic,bionic,now 1.1.1+bzr982-0ubuntu19 all  
[installé]
  qt5-gtk-platformtheme/bionic,now 5.9.5+dfsg-0ubuntu1 amd64  [installé, 
automatique]
  software-properties-gtk/bionic,bionic,now 0.96.24.32.1 all  [installé]
  transmission-gtk/bionic,now 2.92-3ubuntu2 amd64  [installé]
  ubuntu-release-upgrader-gtk/bionic,bionic,now 1:18.04.17 all  [installé]
  xdg-user-dirs-gtk/bionic,now 0.10-2 amd64  [installé]

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

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


[Desktop-packages] [Bug 1450838] Re: lightdm fails to unlock with serial console configured

2019-02-02 Thread Theo Linkspfeifer
Is this still the case when testing with a currently supported Ubuntu
release?

** Changed in: light-locker (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  lightdm fails to unlock with serial console configured

Status in light-locker package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  With /etc/default/grub configured for serial console output as follows
  (seehttps://help.ubuntu.com/community/SerialConsoleHowto):

  GRUB_DEFAULT=0
  GRUB_TIMEOUT=3
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT=""
  GRUB_CMDLINE_LINUX=""
  GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8"

  #GRUB_TERMINAL=console
  GRUB_TERMINAL="serial console"
  GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no 
--stop=1"

  Lightdm fails to unlock a locked screen. Initial login works fine.
  But, when the screen locks, the correct password is accepted, but the
  screen does not unlock.

  If I disable serial console with the default "GRUB_TERMINAL=console",
  lightdm screen unlock seems to work fine. I don't know if this is a
  problem with lightdm or light-locker.

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

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


[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2019-01-26 Thread Theo Linkspfeifer
** Bug watch added: Xfce Bugzilla #15087
   https://bugzilla.xfce.org/show_bug.cgi?id=15087

** Also affects: exo via
   https://bugzilla.xfce.org/show_bug.cgi?id=15087
   Importance: Unknown
   Status: Unknown

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in exo:
  Unknown
Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1812125] Re: Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-20 Thread Theo Linkspfeifer
Is this meant to be a workaround for bug 1335492?

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

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

  (NOTE: This used a custom version of Xubuntu but the screenshot came
  direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
  amd64.iso")

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

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


[Desktop-packages] [Bug 1812367] Re: Issuing right button click by xdotool does not work as expected

2019-01-20 Thread Theo Linkspfeifer
Probably related to https://bugzilla.xfce.org/show_bug.cgi?id=7845 (key
press vs. key release).

** Bug watch added: Xfce Bugzilla #7845
   https://bugzilla.xfce.org/show_bug.cgi?id=7845

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

Title:
  Issuing right button click by xdotool does not work as expected

Status in xdotool package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  If I run 'xdotool click 3' as a keyboard shortcut (in Xfce at least)
  it does not work as a right button click unless I add short delay by
  sleep command in a script before running xdotool.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xdotool 1:3.20150503.1-2
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 18 11:29:52 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1580 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: xdotool
  UpgradeStatus: Upgraded to xenial on 2018-04-14 (279 days ago)

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

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


[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)

2019-01-12 Thread Theo Linkspfeifer
Maybe related to bug 1760068.

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

Title:
  Can not switch to virtual console (TTY)

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to 
Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker 
is not used).
  This happens with nvidia-340 driver (I am using version 
340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver.

  This bug also breaks light-locker, suspend to RAM, switching user and
  maybe something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 11 16:17:15 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-05 (735 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1808352] Re: Context menus spawn in a way that causes unintended clicks when using Firefox CSD

2018-12-20 Thread Theo Linkspfeifer
As possible workaround try setting ui.context_menus.after_mouseup to
'true' in about:config.

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

Title:
  Context menus spawn in a way that causes unintended clicks when using
  Firefox CSD

Status in firefox package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE
  1 - First, open Firefox, enable Client Side Decoration, restart the program.
  2 - Open some webpage, make sure you navigate a bit, leaving behind pages 
that can be returned to.
  3 - Then right click anywhere on the current page. On my system, the context 
menu 'back' button appears right beneath the mouse cursor, and a click is 
automatically inserted there, making the page 'go back' everytime you right 
click with the mouse.

  Running Xubuntu 18.04.1 LTS
  Firefox 64.0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1420 F pulseaudio
   /dev/snd/controlC0:  dsilva 1420 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Dec 13 12:35:17 2018
  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 2018-12-13 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.0.0.1 dev wlp6s0 proto dhcp metric 600 
   10.0.0.0/24 dev wlp6s0 proto kernel scope link src 10.0.0.102 metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/27/2018:svnDellInc.:pnInspiron5458:pvr:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2018-12-04 Thread Theo Linkspfeifer
It is a library for keyboard layout handling. The Ubuntu package used to
include a patch which apparently fixes the problem with xfce4-keyboard-
settings.

Old upstream report:
https://bugs.freedesktop.org/show_bug.cgi?id=47671

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

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1805197]

2018-11-28 Thread Theo Linkspfeifer
Launchpad report:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1805197

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2018-11-28 Thread Theo Linkspfeifer
** Patch added: "revert-default-group-change.patch"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1805197/+attachment/5216994/+files/revert-default-group-change.patch

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2018-11-27 Thread Theo Linkspfeifer
Building the libxklavier package with the dropped revert-default-group-
change.patch file resolves the problem.

http://launchpadlibrarian.net/282996317/libxklavier_5.4-0ubuntu2_5.4-1.diff.gz

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2018-11-27 Thread Theo Linkspfeifer
This bug is not present anymore after downgrading the libxklavier
package to the version from xenial (5.4-0ubuntu2).

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

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in xfce4-settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  New
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions

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


[Desktop-packages] [Bug 1637073] Re: Intel Xorg Driver and CustomEDID crash

2018-11-21 Thread Theo Linkspfeifer
** Package changed: xfce4-settings (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)

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

Title:
  Intel Xorg Driver and CustomEDID crash

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

Bug description:
  Running MythBuntu 16.04.1 on a Gigibyte Brix N3150 with integrated
  Intel graphics.

  To avoid the xfce bug from
  https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1308105
  I've previously forced the EDID settings via an xorg.conf file with
  NVidia graphics.

  If i use the following xorg.conf file with Intel graphics the mythfe (MythTV 
Frontend) user can't login.
   
  Section "Device"
 Identifier  "Intel Graphics"
 Driver  "intel"
 Option  "AccelMethod" "sna"
 Option  "TearFree" "true"
 Option  "CustomEDID" "HDMI3:/etc/X11/samsung.edid"

  EndSection

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

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


[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-21 Thread Theo Linkspfeifer
Indeed. The log file does not list intel_drv.so, so maybe Xorg has to be
explicitly configured to do so.

Here is an upstream bug report which appears be closely related to the
blanking problem:

https://bugs.freedesktop.org/show_bug.cgi?id=108021

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

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-21 Thread Theo Linkspfeifer
The cause of this issue has to be in Xorg 1.20 then (18.04 comes with
1.19).

I assume that xserver-xorg-video-intel is still installed by default, so
please check if removing this driver package has any effect (the generic
modesetting driver will be used instead).

For reference the greeter code:
https://git.launchpad.net/lightdm-gtk-greeter/tree/src/lightdm-gtk-greeter.c#n2830

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-20 Thread Theo Linkspfeifer
Few more things:

- Does running "dm-tool switch-to-greeter" instead trigger the bug?
- Does simply waiting at the login screen for 10 minutes trigger the bug?
- Can the bug be reproduced after installing and booting an older kernel 
version? I suggest to test with 4.15 (version used in 18.04).

https://wiki.ubuntu.com/KernelMainlineBuilds
http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-19 Thread Theo Linkspfeifer
** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

2018-11-19 Thread Theo Linkspfeifer
You have layers.acceleration.force-enabled set to 'true'. Does changing
it back to 'false' + restart make a difference?

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1799793] Re: Developer tools menu has a black background

2018-11-19 Thread Theo Linkspfeifer
Did you disable Xfce's builtin compositor?

Settings > Windows Manager Tweaks > Compositor

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

Title:
  Developer tools menu has a black background

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I think the background should be transparent.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1697 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Oct 24 22:30:54 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (931 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.20 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (153 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2018-11-11 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1308105 ***
https://bugs.launchpad.net/bugs/1308105

** This bug has been marked a duplicate of bug 1308105
   Xfce resets TV mode to NULL when power cycled

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1802582] Re: Inconsistency in xfce4-mime-settings

2018-11-09 Thread Theo Linkspfeifer
There is no attachment.

** Package changed: xorg-server (Ubuntu) => xfce4-settings (Ubuntu)

** Changed in: xfce4-settings (Ubuntu)
   Status: New => Incomplete

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

Title:
  Inconsistency in xfce4-mime-settings

Status in xfce4-settings package in Ubuntu:
  Incomplete

Bug description:
  This bug report pertains to Xubuntu 16.04.3 LTS. My current kernel is
  4.4.0-116-generic x86_64.

  Mime types can not be changed consistently. My attached bug report
  shows the details with screenshots for which I did not find out how to
  post them here. So look at the attachment, please.

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

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


[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-09 Thread Theo Linkspfeifer
I did not spot anything relevant in your log files either.

Sadly, no idea how to debug this further also.

** Package changed: light-locker (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2018-11-08 Thread Theo Linkspfeifer
Well, as mentioned in comment #10, this bug is not limited to the unlock
screen (which happens to be a second Xorg instance if you use light-
locker).

Does the workaround in bug 1757202 fix the issue for you?

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1783637] Re: light-locker causes tty to change

2018-11-08 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1760068 ***
https://bugs.launchpad.net/bugs/1760068

** This bug has been marked a duplicate of bug 1760068
   Wrong resolution at unlock screen

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

Title:
  light-locker causes tty to change

Status in light-locker package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After upgrading to 18.04, on xfce4 with Display Power Management
  (xfce4-power-manager) enabled, or any of the three sliders set to non-
  zero, then when the time limit is hit after inactivity two monitors
  power down, but then the tty switches to tty8, and the third monitor
  just shows a black with a cursor flashing. Switching back to tty7
  shows text saying that the session is locked, but no amount of
  keyboard or mouse activity brings up a prompt to unlock it.

  Two Xorg logs are created when this happens (see attached). Ctrl-
  Alt-F# will switch to other ttys at this point, but only briefly
  before switching back to the one that is black with a single flashing
  cursor. After a few switchings between ttys, it stops automatically
  going back to tty8.

  This problem also occurs when xscreensaver is used to control the
  display power management as well. However on switching back to tty7 in
  this case, the unlock dialog is presented as expected and things
  continue to work. So it would appear it is something more fundamental
  than xfce4-power-manager that is causing the active tty to change when
  the screens go sleep.

  The screen power off that occurs while the lightdm's graphical login
  is presented (i.e. before logging in) works fine.

  This problem appears to be due to light-locker. If I stop it from
  running the problem goes away.

  (I would expect things to happen as in 17.10, namely that the displays
  blank/switch off as selected, and then when further input is given
  they unblank/switch on.)

  Please let me know what further information I can provide to narrow
  down the problem.

  lsb_release -rd:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apt-cache policy xfce4-power-manager:
  xfce4-power-manager:
    Installed: 1.6.1-0ubuntu1
    Candidate: 1.6.1-0ubuntu1
    Version table:
   *** 1.6.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfce4-power-manager 1.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 25 21:10:33 2018
  InstallationDate: Installed on 2017-05-13 (438 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to bionic on 2018-07-16 (9 days ago)

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

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


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2018-11-08 Thread Theo Linkspfeifer
A new version of nvidia-graphics-drivers-340 is available in -updates.

Please check if it resolves the bug.

https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/340.107-0ubuntu0.18.04.1

** Changed in: light-locker (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1775280] Re: The second user cannot start their session, login screen has low resolution

2018-11-08 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1760068 ***
https://bugs.launchpad.net/bugs/1760068

** This bug has been marked a duplicate of bug 1760068
   Wrong resolution at unlock screen

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

Title:
  The second user cannot start their session, login screen has low
  resolution

Status in lightdm package in Ubuntu:
  New

Bug description:
  The first user can start their session successfully with autologin.
  When I try to switch to the second user, the login screen has very low
  resolution and it cannot start the secondary user session. I tried to
  change the value of the autologin user, than the other user session
  start well, but the original user session failed. That's why I think
  this is not a user related error, always the second user session fail,
  does not matter which one is the first user. The only differences
  between the default settings that passwordless login switch on the pam
  config and use nvidia-340 driver instead of noveau. The strange thing
  that this lightdm config works well with noveau driver, the problem
  with noveau driver that the video playing freeze the computer.
  Previously lightdm and nvidia driver work well on 16.04. This is a
  clean install not an upgrade from 16.04. I think the problem somewhere
  virtual X terminals handled by ligthDm.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun  5 23:07:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631

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

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


[Desktop-packages] [Bug 1802225] Re: LightDM login doesn't display after screen lock

2018-11-08 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1801609 ***
https://bugs.launchpad.net/bugs/1801609

** This bug has been marked a duplicate of bug 1801609
   Fails to deactivate dpms off mode after user initiated wake-up events(not 
system-suspended, just locked and dpms active)

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

Title:
  LightDM login doesn't display after screen lock

Status in lightdm package in Ubuntu:
  New

Bug description:
  When locking the screen via the xfce menu or light-locker tool the
  screen sits at a blank/black screen. Moving the mouse or pressing a
  button on the keyboard does nothing. After searching I found I could
  just enter my password blindly and it would unlock the screen. Also
  going to a console tty and back to the graphical login would then show
  a login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  Uname: Linux 4.19.0-041900-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  8 13:29:14 2018
  InstallationDate: Installed on 2017-11-06 (366 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  LightdmConfig:
   [LightDM]
   logind-check-graphical=true
   display-setup-script=xrandr --output eDP-1 --primary
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)

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

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


[Desktop-packages] [Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

2018-11-06 Thread Theo Linkspfeifer
Your suggestion in comment #8 looks like something that is worth to
forward to the Xfce bug tracker (Xfce Core -> Xfce4-settings).

https://bugzilla.xfce.org/

The new key could be added to the xsettings.xml, and maybe even be
exposed in the keyboard settings dialog too.

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

Title:
  org.gnome.desktop.interface.cursor-blink-timeout not honored

Status in vte2.91 package in Ubuntu:
  New
Status in xfconf package in Ubuntu:
  New

Bug description:
  Xubuntu desktop 18.04.1

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-terminal: 3.28.2-1ubuntu1~18.04.1
  libgtk-3-0: 3.22.30-1ubuntu1
  dconf-editor: 3.28.0-1

  Per workaround instructions in comment #8 on bug 838381 (of which this is not 
a duplicate), I set /org/gnome/desktop/interface/cursor-blink-timeout to a 
large value, less than the stated maximum of 2^31 - 1.
  I saved the change, exited dconf-editor and restarted the computer.

  What I expected to happen:
  Cursor in GTK-based terminal emulators will no longer stop blinking after 10 
seconds.

  What happens instead:
  Cursor in GTK-based terminal emulators continues to stop blinking after 10 
seconds.

  Of note, the cursor-blink-time *is* honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1798481/+subscriptions

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


[Desktop-packages] [Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

2018-11-05 Thread Theo Linkspfeifer
Steve, did you contact the Xfce developers?

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

Title:
  org.gnome.desktop.interface.cursor-blink-timeout not honored

Status in vte2.91 package in Ubuntu:
  New
Status in xfconf package in Ubuntu:
  New

Bug description:
  Xubuntu desktop 18.04.1

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-terminal: 3.28.2-1ubuntu1~18.04.1
  libgtk-3-0: 3.22.30-1ubuntu1
  dconf-editor: 3.28.0-1

  Per workaround instructions in comment #8 on bug 838381 (of which this is not 
a duplicate), I set /org/gnome/desktop/interface/cursor-blink-timeout to a 
large value, less than the stated maximum of 2^31 - 1.
  I saved the change, exited dconf-editor and restarted the computer.

  What I expected to happen:
  Cursor in GTK-based terminal emulators will no longer stop blinking after 10 
seconds.

  What happens instead:
  Cursor in GTK-based terminal emulators continues to stop blinking after 10 
seconds.

  Of note, the cursor-blink-time *is* honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1798481/+subscriptions

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


[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries

2018-10-24 Thread Theo Linkspfeifer
However, it this particular issue still present in 18.04 or 18.10?

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

Title:
  .xsession-errors filled with entries

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

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

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

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


[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries

2018-10-24 Thread Theo Linkspfeifer
https://en.wikipedia.org/wiki/Upstream_(software_development)


The upstream bug tracker for nm-applet is this one:

https://gitlab.gnome.org/GNOME/network-manager-applet/issues

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

Title:
  .xsession-errors filled with entries

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

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-10-20 Thread Theo Linkspfeifer
Debian's xfce4-session package only recommends light-locker, so my
suggestion in comment #26 would be an acceptable solution.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-10-20 Thread Theo Linkspfeifer
** Also affects: xfce4-session (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2018-10-20 Thread Theo Linkspfeifer
You can fix this issue by removing the line "x-scheme-handler/file=exo-
file-manager.desktop" from the following files:

/usr/share/xubuntu/applications/defaults.list (provided by Xubuntu)
~/.config/mimeapps.list (user overrides)
~/.local/share/applications/mimeapps.list (deprecated)

The entry should not be added anymore according to upstream Xfce [1],
and it is the cause for the misbehavior according to the comments in the
linked Debian report [2].

[1] 
https://git.xfce.org/xfce/exo/commit/?id=b74caf97642ae2bf00a7754a5fb193f695b6f3d4
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874003#75

** Also affects: xubuntu-default-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

2018-10-18 Thread Theo Linkspfeifer
Those are VTE based terminal emulators, so I suggest that you forward
this issue to the GNOME developers.

https://gitlab.gnome.org/GNOME/vte/issues

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  org.gnome.desktop.interface.cursor-blink-timeout not honored

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New
Status in xfce4-terminal package in Ubuntu:
  New

Bug description:
  Xubuntu desktop 18.04.1

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-terminal: 3.28.2-1ubuntu1~18.04.1
  libgtk-3-0: 3.22.30-1ubuntu1
  dconf-editor: 3.28.0-1

  Per workaround instructions in comment #8 on bug 838381 (of which this is not 
a duplicate), I set /org/gnome/desktop/interface/cursor-blink-timeout to a 
large value, less than the stated maximum of 2^31 - 1.
  I saved the change, exited dconf-editor and restarted the computer.

  What I expected to happen:
  Cursor in GTK-based terminal emulators will no longer stop blinking after 10 
seconds.

  What happens instead:
  Cursor in GTK-based terminal emulators continues to stop blinking after 10 
seconds.

  Of note, the cursor-blink-time *is* honored.

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-10-14 Thread Theo Linkspfeifer
Can the order be changed so that xubuntu-desktop depends on lightdm-gtk-
greeter, lightdm? The dependencies are listed in alphabetical order, but
that may be not a requirement.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1795144] Re: [xubuntu] thunar is opened when insering usb key even if nautilus is the preferred file manager

2018-10-13 Thread Theo Linkspfeifer
** Package changed: nautilus (Ubuntu) => thunar-volman (Ubuntu)

** Bug watch added: Xfce Bugzilla #9537
   https://bugzilla.xfce.org/show_bug.cgi?id=9537

** Also affects: thunar-volman via
   https://bugzilla.xfce.org/show_bug.cgi?id=9537
   Importance: Unknown
   Status: Unknown

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

Title:
  [xubuntu] thunar is opened when insering usb key even if nautilus is
  the preferred file manager

Status in Thunar Volume Manager:
  Unknown
Status in thunar-volman package in Ubuntu:
  New

Bug description:
  xubuntu bionic (but it seems to me that xenial had the same issue).

  Install nautilus and set as default file manager.

  When an usb key is inserted, thunar is used to open it automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar-volman/+bug/1795144/+subscriptions

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


[Desktop-packages] [Bug 1797032] Re: xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer (nvidia/nouveau)

2018-10-13 Thread Theo Linkspfeifer
The conclusion seems to be that having light-locker or xscreensaver
enabled is a way to prevent this glitch from occurring.

I think it would be best to contact the 'nouveau' driver devs and ask
them how to further debug this issue.

https://nouveau.freedesktop.org/wiki/Bugs/

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

Title:
  xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer
  (nvidia/nouveau)

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

Bug description:
  -- updated info
  I re-booted daily x86 daily on same machine, was able to re-create, but it 
came good on its own (~15+ seconds after screen appeared)

  It only occurs sometimes; more testing & it can occur with `sudo
  systemctl suspend` but if you wait cursor will re-appear usually so my
  conclusion it was [fixed] via whisker-menu may be invalid; maybe I'm
  impatient, or nvidia/nouveau on this card requires time for system to
  display mouse???

  I do think something is wrong, but it's extremely minor, and
  inconsistent!  (would be a pain I suspect to find)

  -- original post

  hp dx6120mt (desktop, pentium 4 dual-core, 3gb ram, nvidia 7600gt)
  xubuntu 18.10 daily ISO x86

  QA test - 2018-10-10 00:26 (current timestamp on QA tracker) of daily
  ISO

  on suspend everything is normal, on wake I've lost my mouse-pointer.

  I can see icons (drives, panel widgets) react & thus can detect where
  cursor is if over something, but no mouse-pointer is visible at all.

  To get mouse back, I select menu (top left), then move mouse over menu
  and pointer re-appears.

  Selecting anything else does not bring mouse back, also selecting menu
  but moving mouse up (not on menu but off screen) allows me to de-
  select menu without pointer being re-drawn.  It returns only if I move
  mouse over the [main] menu when selected.

  I've suspended 4 times this 'live-test', same loss-of-pointer each
  time, each time restored via selection of menu top left (third time I
  didn't have it return as I coughed causing mouse to never thus cross
  menu & select something right causing menu to close without return of
  mouse-pointer; got same reaction on 4th sleep/wake)..

  xubuntu@xubuntu:~$   sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: G73 [GeForce 7600 GT]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nouveau latency=0
     resources: irq:24 memory:f100-f1ff memory:e000-efff 
memory:f200-f2ff ioport:1000(size=128) memory:c-d

  ---
  I looked for duplicates - lots for intel graphics, not nvidia
  Sorry if duplicate; also I know it's a wrong package assigned (unsure to 
assign to)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xubuntu-desktop 2.227
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Wed Oct 10 04:30:18 2018
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181010)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797394] Re: Unable to locate models.dat file

2018-10-11 Thread Theo Linkspfeifer
** Package changed: xfce4-terminal (Ubuntu) => hplip (Ubuntu)

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

Title:
  Unable to locate models.dat file

Status in hplip package in Ubuntu:
  New

Bug description:
  Hp printer worked on 16.04 but it fails after distribution upgrade to
  18.04. Based on solved bug #1744340 I checked libsane-hpaio and hplip
  packages. They were all OK after removing them and reinstalling them -
  just to make sure. However, apt install libsane-hpaio complained about
  missing /etc/hp/hplip.conf (?). Regardless, running hp-setup cannot
  complete the download step because of incorrect checksum. This is when
  I started this ubuntu-bug -w command.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfce4-terminal 0.8.7.4-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Oct 11 15:59:14 2018
  ExecutablePath: /usr/bin/xfce4-terminal
  InstallationDate: Installed on 2016-12-13 (667 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  SourcePackage: xfce4-terminal
  UpgradeStatus: Upgraded to bionic on 2018-10-01 (9 days ago)

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

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


[Desktop-packages] [Bug 1797032] Re: xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer (nvidia/nouveau)

2018-10-11 Thread Theo Linkspfeifer
Does it change anything if you disable light-locker in 18.04, or enable
it in 18.10? Also, can you restore the mouse pointer by switching to
another VT and back?

>From all the information gathered so far this appears to be a Xfce or
Xubuntu specific bug which may have been introduced recently.

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

Title:
  xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer
  (nvidia/nouveau)

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

Bug description:
  -- updated info
  I re-booted daily x86 daily on same machine, was able to re-create, but it 
came good on its own (20-30 seconds after screen appeared)

  It only occurs sometimes; more testing & it can occur with `sudo
  systemctl suspend` but if you wait cursor will re-appear usually so my
  conclusion it was [fixed] via whisker-menu may be invalid; maybe I'm
  impatient, or nvidia/nouveau on this card requires time for system to
  display mouse???

  I do think something is wrong, but it's extremely minor, and
  inconsistent!  (would be a pain I suspect to find)

  -- original post

  hp dx6120mt (desktop, pentium 4 dual-core, 3gb ram, nvidia 7600gt)
  xubuntu 18.10 daily ISO x86

  QA test - 2018-10-10 00:26 (current timestamp on QA tracker) of daily
  ISO

  on suspend everything is normal, on wake I've lost my mouse-pointer.

  I can see icons (drives, panel widgets) react & thus can detect where
  cursor is if over something, but no mouse-pointer is visible at all.

  To get mouse back, I select menu (top left), then move mouse over menu
  and pointer re-appears.

  Selecting anything else does not bring mouse back, also selecting menu
  but moving mouse up (not on menu but off screen) allows me to de-
  select menu without pointer being re-drawn.  It returns only if I move
  mouse over the [main] menu when selected.

  I've suspended 4 times this 'live-test', same loss-of-pointer each
  time, each time restored via selection of menu top left (third time I
  didn't have it return as I coughed causing mouse to never thus cross
  menu & select something right causing menu to close without return of
  mouse-pointer; got same reaction on 4th sleep/wake)..

  xubuntu@xubuntu:~$   sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: G73 [GeForce 7600 GT]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nouveau latency=0
     resources: irq:24 memory:f100-f1ff memory:e000-efff 
memory:f200-f2ff ioport:1000(size=128) memory:c-d

  ---
  I looked for duplicates - lots for intel graphics, not nvidia
  Sorry if duplicate; also I know it's a wrong package assigned (unsure to 
assign to)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xubuntu-desktop 2.227
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Wed Oct 10 04:30:18 2018
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181010)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797032] Re: xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer (nvidia/nouveau)

2018-10-10 Thread Theo Linkspfeifer
In this case I suggest that you test with 18.04.1 also.

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

Title:
  xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer
  (nvidia/nouveau)

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

Bug description:
  -- updated info
  I re-booted daily x86 daily on same machine, was able to re-create, but it 
came good on its own (20-30 seconds after screen appeared)

  It only occurs sometimes; more testing & it can occur with `sudo
  systemctl suspend` but if you wait cursor will re-appear usually so my
  conclusion it was via whisker-menu may be invalid; maybe I'm
  impatient, or nvidia/nouveau on this card requires time for system to
  display mouse???

  I do think something is wrong, but it's extremely minor, and
  inconsistent!  (would be a pain I suspect to find)

  -- original post

  hp dx6120mt (desktop, pentium 4 dual-core, 3gb ram, nvidia 7600gt)
  xubuntu 18.10 daily ISO x86

  QA test - 2018-10-10 00:26 (current timestamp on QA tracker) of daily
  ISO

  on suspend everything is normal, on wake I've lost my mouse-pointer.

  I can see icons (drives, panel widgets) react & thus can detect where
  cursor is if over something, but no mouse-pointer is visible at all.

  To get mouse back, I select menu (top left), then move mouse over menu
  and pointer re-appears.

  Selecting anything else does not bring mouse back, also selecting menu
  but moving mouse up (not on menu but off screen) allows me to de-
  select menu without pointer being re-drawn.  It returns only if I move
  mouse over the [main] menu when selected.

  I've suspended 4 times this 'live-test', same loss-of-pointer each
  time, each time restored via selection of menu top left (third time I
  didn't have it return as I coughed causing mouse to never thus cross
  menu & select something right causing menu to close without return of
  mouse-pointer; got same reaction on 4th sleep/wake)..

  xubuntu@xubuntu:~$   sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: G73 [GeForce 7600 GT]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nouveau latency=0
     resources: irq:24 memory:f100-f1ff memory:e000-efff 
memory:f200-f2ff ioport:1000(size=128) memory:c-d

  ---
  I looked for duplicates - lots for intel graphics, not nvidia
  Sorry if duplicate; also I know it's a wrong package assigned (unsure to 
assign to)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xubuntu-desktop 2.227
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Wed Oct 10 04:30:18 2018
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181010)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797032] Re: xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer (nvidia/nouveau)

2018-10-10 Thread Theo Linkspfeifer
This is a new issue in 18.10?

** Package changed: xubuntu-meta (Ubuntu) => xserver-xorg-video-nouveau
(Ubuntu)

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

Title:
  xubuntu 18.10 daily x86 - suspend, on wake i have no mouse-pointer
  (nvidia/nouveau)

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

Bug description:
  -- updated info
  I re-booted daily x86 daily on same machine, was able to re-create, but it 
came good on its own (20-30 seconds after screen appeared)

  It only occurs sometimes; more testing & it can occur with `sudo
  systemctl suspend` but if you wait cursor will re-appear usually so my
  conclusion it was via whisker-menu may be invalid; maybe I'm
  impatient, or nvidia/nouveau on this card requires time for system to
  display mouse???

  I do think something is wrong, but it's extremely minor, and
  inconsistent!  (would be a pain I suspect to find)

  -- original post

  hp dx6120mt (desktop, pentium 4 dual-core, 3gb ram, nvidia 7600gt)
  xubuntu 18.10 daily ISO x86

  QA test - 2018-10-10 00:26 (current timestamp on QA tracker) of daily
  ISO

  on suspend everything is normal, on wake I've lost my mouse-pointer.

  I can see icons (drives, panel widgets) react & thus can detect where
  cursor is if over something, but no mouse-pointer is visible at all.

  To get mouse back, I select menu (top left), then move mouse over menu
  and pointer re-appears.

  Selecting anything else does not bring mouse back, also selecting menu
  but moving mouse up (not on menu but off screen) allows me to de-
  select menu without pointer being re-drawn.  It returns only if I move
  mouse over the [main] menu when selected.

  I've suspended 4 times this 'live-test', same loss-of-pointer each
  time, each time restored via selection of menu top left (third time I
  didn't have it return as I coughed causing mouse to never thus cross
  menu & select something right causing menu to close without return of
  mouse-pointer; got same reaction on 4th sleep/wake)..

  xubuntu@xubuntu:~$   sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: G73 [GeForce 7600 GT]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:01:00.0
     version: a1
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nouveau latency=0
     resources: irq:24 memory:f100-f1ff memory:e000-efff 
memory:f200-f2ff ioport:1000(size=128) memory:c-d

  ---
  I looked for duplicates - lots for intel graphics, not nvidia
  Sorry if duplicate; also I know it's a wrong package assigned (unsure to 
assign to)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xubuntu-desktop 2.227
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Wed Oct 10 04:30:18 2018
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181010)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1794330] Re: switching users wrong resulution nvidia

2018-10-09 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1760068 ***
https://bugs.launchpad.net/bugs/1760068

** This bug has been marked a duplicate of bug 1760068
   Wrong resolution at unlock screen

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

Title:
  switching users wrong resulution nvidia

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  When i try to switch user it goes to login screen with wrong screen 
resolution and the screen goes scaled, it stays scaled after login to second 
user, but when i go back to first user - resolution is normal. And when i 
logout instead of switching everything is OK.
  Ubuntu-MATE 18.04 nvidia-340 driver(geforce 310m)
  My default resolution is 1366x768

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1794330/+subscriptions

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


[Desktop-packages] [Bug 1783637] Re: light-locker causes tty to change

2018-10-09 Thread Theo Linkspfeifer
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  light-locker causes tty to change

Status in light-locker package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After upgrading to 18.04, on xfce4 with Display Power Management
  (xfce4-power-manager) enabled, or any of the three sliders set to non-
  zero, then when the time limit is hit after inactivity two monitors
  power down, but then the tty switches to tty8, and the third monitor
  just shows a black with a cursor flashing. Switching back to tty7
  shows text saying that the session is locked, but no amount of
  keyboard or mouse activity brings up a prompt to unlock it.

  Two Xorg logs are created when this happens (see attached). Ctrl-
  Alt-F# will switch to other ttys at this point, but only briefly
  before switching back to the one that is black with a single flashing
  cursor. After a few switchings between ttys, it stops automatically
  going back to tty8.

  This problem also occurs when xscreensaver is used to control the
  display power management as well. However on switching back to tty7 in
  this case, the unlock dialog is presented as expected and things
  continue to work. So it would appear it is something more fundamental
  than xfce4-power-manager that is causing the active tty to change when
  the screens go sleep.

  The screen power off that occurs while the lightdm's graphical login
  is presented (i.e. before logging in) works fine.

  This problem appears to be due to light-locker. If I stop it from
  running the problem goes away.

  (I would expect things to happen as in 17.10, namely that the displays
  blank/switch off as selected, and then when further input is given
  they unblank/switch on.)

  Please let me know what further information I can provide to narrow
  down the problem.

  lsb_release -rd:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apt-cache policy xfce4-power-manager:
  xfce4-power-manager:
    Installed: 1.6.1-0ubuntu1
    Candidate: 1.6.1-0ubuntu1
    Version table:
   *** 1.6.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfce4-power-manager 1.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 25 21:10:33 2018
  InstallationDate: Installed on 2017-05-13 (438 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to bionic on 2018-07-16 (9 days ago)

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

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


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2018-10-09 Thread Theo Linkspfeifer
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1497918] Re: File couldn't be moved to trash: Invalid link across device boundaries

2018-10-06 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1638245 ***
https://bugs.launchpad.net/bugs/1638245

** This bug has been marked a duplicate of bug 1638245
   Files in the root of a folder on another partition symlinked to user's home 
cannot be moved to trash because of a patch in this package

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

Title:
  File couldn't be moved to  trash: Invalid link across device
  boundaries

Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed

Bug description:
  1) Xubuntu 15.10 beta 1

  2) Thunar 1.6.10

  3) Dragging in Thunar an external folder (like "/media/user/mountxy" for 
example) to one's home folder creates a linked folder (or is it called: folder 
link?). 
  Now inside this linked folder I try to use Thunar's right-click "delete file" 
menu. It's the "delete to trash" entry.
  When the file is in some sub-folder of the linked folder, everything works.
  When file is in the linked folder's root however, Thunar gives the following 
error:

  4) Thunar complains (roughly translated to English from my localised
  Thunar) :

  »File couldn't be moved to trash.
  Invalid link across device boundaries.«

  (In localised language the message says so:
  »Datei konnte nicht in den Papierkorb verschoben werden.
  Ungültiger Link über Gerätegrenzen hinweg.« )

  P.S. When in this linked folder's root I delete the file without the
  trash-option, i.e. the "delete forever" menu entry, it works.

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

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


[Desktop-packages] [Bug 1775434] Re: Wrong ExecStop in systemd service unit

2018-10-06 Thread Theo Linkspfeifer
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831467

I suggest that you contact the Debian package maintainers.

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

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

Title:
  Wrong ExecStop in systemd service unit

Status in transmission package in Ubuntu:
  New

Bug description:
  ExecStop in /lib/systemd/system/transmission-daemon.service is:

  ExecStop=/bin/kill -s STOP $MAINPID

  when it should be:

  ExecStop=/bin/kill -s TERM $MAINPID

  since SIGSTOP will just suspend the daemon until it received a
  SIGCONT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: transmission-daemon (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 13:47:25 2018
  InstallationDate: Installed on 2018-04-28 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1796183] Re: vpn indicator icon is not appearing

2018-10-05 Thread Theo Linkspfeifer
https://github.com/shimmerproject/elementary-xfce/issues/104

Can you verify that this bug is fixed in 18.10 or by manually adding the
missing icon(s) to 18.04?

** Bug watch added: github.com/shimmerproject/elementary-xfce/issues #104
   https://github.com/shimmerproject/elementary-xfce/issues/104

** Package changed: network-manager-applet (Ubuntu) => xubuntu-artwork
(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/1796183

Title:
  vpn indicator icon is not appearing

Status in xubuntu-artwork package in Ubuntu:
  New

Bug description:
  When network is connected with wired connection and there is active
  VPN connection, network icon does not change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-icon-theme 18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  4 23:09:54 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-03-22 (196 days ago)
  InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: xubuntu-artwork
  UpgradeStatus: Upgraded to bionic on 2018-09-05 (29 days ago)

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

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


[Desktop-packages] [Bug 1796183] Re: vpn indicator icon is not appearing

2018-10-05 Thread Theo Linkspfeifer
** Package changed: xubuntu-artwork (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/1796183

Title:
  vpn indicator icon is not appearing

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

Bug description:
  When network is connected with wired connection and there is active
  VPN connection, network icon does not change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-icon-theme 18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  4 23:09:54 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-03-22 (196 days ago)
  InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: xubuntu-artwork
  UpgradeStatus: Upgraded to bionic on 2018-09-05 (29 days ago)

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

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


[Desktop-packages] [Bug 1773222] Re: screen doesn't switch off when logged out

2018-10-04 Thread Theo Linkspfeifer
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu)

** Also affects: lightdm-gtk-greeter-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  screen doesn't switch off when logged out

Status in lightdm-gtk-greeter package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  New

Bug description:
  setting of screensaver-timeout and "timeout until screen blanks" have no 
effect; when logged in, screen timeout works and follows the settings
  Xubuntu 18.04
  lightdm 1.26.0-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 24 18:34:19 2018
  InstallationDate: Installed on 2018-05-24 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1793222] Re: Mousepad doesn't take input after canceled save dialog

2018-09-26 Thread Theo Linkspfeifer
I have tried to reproduce it in the live session of Xubuntu 18.04.1 and
18.10 (dev release), but I did not encounter the issue.

Maybe there is another component interfering, or some setting needs to
be changed to trigger the bug.

** Package changed: mousepad (Ubuntu) => ibus (Ubuntu)

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

Title:
  Mousepad doesn't take input after canceled save dialog

Status in ibus package in Ubuntu:
  New

Bug description:
  1 Open Mousepad
  2 Write something
  3 Ctrl+S for save 
 -> dialog opens 
  4 Exit dialog with ESC 
 -> Mousepad will not take any keyboard input anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mousepad 0.4.0-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep 19 07:17:27 2018
  InstallationDate: Installed on 2018-02-12 (218 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: mousepad
  UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago)

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

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


[Desktop-packages] [Bug 1605811] Re: x11 crashes

2018-09-23 Thread Theo Linkspfeifer
Was this issue resolved eventually?

** Package changed: xfburn (Ubuntu) => xorg (Ubuntu)

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

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

Title:
  x11 crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  somehow during update or something we have like very unstable x11
  pulled in. also affects stretch upstream.

  the desire is for the video driver, open or else.ABOVE jessie or
  15.10. Well I had the else(force freeze x117), a kernel update to 4.6
  broke it, so I went open. hassle but not a big deal. Obviously this
  means reinstalling x118. Ok. -or so I thought.

  x118 with kernel 4.6 somehow breaks all of the x11 depends, so NO
  driver will load and x11 complains its (now bleeding) head off, and
  wont load. If it loads at all, im impressed.

  vesa-fail
  fbdev-fail
  ati-fail
  radeon-fail

  and a few other drivers --all depends of radeon ati...

  Its not ramdom gibberish to me but what it entails is that X11 CANT
  load as the video driver is broken at every depends level for the ati
  driver at least, mayhaps the entire x11 video driver subsystem.Its
  looks to someone like something didnt get linked correctly. Those
  sorts of errors.

  xyz missing from yada yada...

  X11 cant load...but CANT is never in programmer vocabulary..

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

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


[Desktop-packages] [Bug 1054923] Re: Window raises on click even if set not to raise in window manager settings (in Xfce)

2018-09-18 Thread Theo Linkspfeifer
** Project changed: chromium-browser => xfwm4

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

Title:
  Window raises on click even if set not to raise in window manager
  settings (in Xfce)

Status in Xfwm4:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce: 
  1) Disable "Raise window when clicking inside application window" in Window 
Manager (xfwm?) settings in Xfce (in Focus tab).
  2) Move another window to partly overlap chromium browser window
  3) click on the chromium browser window below title bar
  Result: the window raises
  Expected result: window should not raise

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Sun Sep 23 13:03:55 2012
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to precise on 2012-09-22 (0 days ago)
  chromium-default: CHROMIUM_FLAGS=""

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

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


[Desktop-packages] [Bug 1777848] Re: screen never locks

2018-09-16 Thread Theo Linkspfeifer
Running gnome-screensaver in debug mode led me to bug 864458.

I have only tested it in a live session, so it may not be disabled in a
normal session.

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

Title:
  screen never locks

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Using lockscreen keybord shortcut (Super+L) doesnt lock screen. The
  systm just freezes a few seconds. Putting the system to sleep
  (suspend), after settings are set to  lock screen when screen is
  blank, also does not lock the screen.

  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: GNOME
  Date: Wed Jun 20 11:57:27 2018
  InstallationDate: Installed on 2016-09-28 (629 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (48 days ago)

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

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


[Desktop-packages] [Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Theo Linkspfeifer
Tested in 18.04, and the command did spawn gnome-screensaver --no-
daemon.

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

Title:
  gnome-screensaver-command --lock starts the daemon

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  1) gnome-screensaver not running, light-locker not running
  2) run ` gnome-screensaver-command --lock` 

  What happens: screen locks and the daemon starts and remains running after 
unlocking.
  Expected result: exit with non-zero like `xscreensaver-command -lock` will in 
similar case.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 20 16:41:28 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (59 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1792620] Re: Nautilus fails to open files properly

2018-09-15 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1778069 ***
https://bugs.launchpad.net/bugs/1778069

** This bug has been marked a duplicate of bug 1778069
   [xfce] nautilus don't open files if set as default file manager

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

Title:
  Nautilus fails to open files properly

Status in nautilus package in Ubuntu:
  New

Bug description:
  On my desktop PC with Xubuntu installed Nautilus fails to open files
  properly. Double clicking a file or right click + "Open With
  *preferred application name*" does nothing but bring the animated
  "wait" icon beside the cursor for a rather long time with nothing
  happening after it disappears. Right click + "Open With Other
  Application" however works with whatever program fit to handle the
  file type in question. Interestingly, this behavior occurs only when
  Nautilus is set as the preferred file manager. If I use Nautilus while
  Thunar is set as the preferred file manager, it works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep 14 20:36:39 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+403+390'"
  InstallationDate: Installed on 2018-09-12 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 778801] Re: TERM unconditionally set to "xterm", regardless of config

2018-09-12 Thread Theo Linkspfeifer
https://git.xfce.org/apps/xfce4-terminal/commit/?id=fa9d95c99d3c73c80fc42fbc23b73a5a8d5bae79

The config option was removed in xfce4-terminal also. Like mentioned in
the previous comment, it is TERM=xterm-256color by default now.

** Changed in: vte (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: xfce4-terminal (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  TERM unconditionally set to "xterm", regardless of config

Status in Gnome Virtual Terminal Emulator:
  Invalid
Status in xfce4-terminal:
  Unknown
Status in vte package in Ubuntu:
  Fix Released
Status in xfce4-terminal package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xfce4-terminal

  Xubuntu 11.04 Natty Narwhal

  xfce4-terminal 0.4.7-0ubuntu1
  libvte9 0.27.90

  I wish to enable 256-color support in apps running under
  xfce4-terminal; but even though I've set TERM to this value in the
  config (and verified it in .config/Terminal/terminalrc), the TERM
  variable winds up having the value "xterm".

  Upon digging a little further, xfce4-terminal correctly sets the TERM
  variable in the environment vector that it then passes through to vte
  via vte_terminal_command_full (this takes place within the
  terminal_screen_launch_child function found in terminal/terminal-
  screen.c). However, vte_terminal_fork_command_full copies everything
  from that vector _except_ the TERM variable, unconditionally replacing
  that with a value that should be set by calling vte_pty_set_term (this
  happens in src/pty.c:__vte_pty_merge_environ(), which is called by
  (and gets the TERM value from) src/pty.c:__vte_pty_spawn, which in
  turn is called by src/vte.c:vte_terminal_fork_command_full() ).
  xfce4-terminal doesn't appear to ever call that function anywhere, and
  thus vte defaults to "xterm". So the appropriate fix would seem to be
  to make xfce4-terminal call that function to register the correct TERM
  value.

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

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


[Desktop-packages] [Bug 1776512] Re: switching users under xfce causes permanent 100% xorg cpu usage

2018-09-06 Thread Theo Linkspfeifer
I would check if this bug can be triggered with the live session also.

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

Title:
  switching users under xfce causes permanent 100% xorg cpu usage

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I switch users via the whisker menu (dm-tool switch-to-greeter)
  and login as the second user, I see permanent heavy cpu usage of xorg.

  I have tried the nouveau drivers as well without success.

  I am currently using the latest nvidia from ppa, but with the official
  nvidia drivers from bionic, I had the problem as well.

  Logging out and logging in as another user does of course work.

  Meaning: I cannot switch users anymore...

  Regards,
  Holger

  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..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.67  Fri Jun  1 04:04:27 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Jun 12 18:17:23 2018
  DistUpgraded: 2018-05-05 23:16:32,941 ERROR giving up on fetching after 
maximum retries
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-23-generic, x86_64: installed
   nvidia, 390.67, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 
710] [1462:8c93]
  InstallationDate: Installed on 2017-11-25 (199 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 32282P2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=56904fca-2008-45c6-9012-80c7b14bd698 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (37 days ago)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9AAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NOK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9AAUS:bd02/23/2018:svnLENOVO:pn32282P2:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNOK:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 32282P2
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  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

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

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


[Desktop-packages] [Bug 1775212] Re: Windows not painted completely since 18.04

2018-09-04 Thread Theo Linkspfeifer
** Changed in: xfwm4 (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Incomplete

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

Title:
  Windows not painted completely since 18.04

Status in xfwm4 package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xubuntu 18.04, the graphics on my desktop are
  broken. It seems to affect all windows and menus, which are painted
  incompletely, or with the wrong colours. It seems to get progressively
  worse, to the point of making programs unusable because entire
  sections of the user interface are missing, so this should have high
  priority IMHO. I will attach a few screenshots as examples.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfwm4 4.12.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  5 17:29:02 2018
  InstallationDate: Installed on 2017-03-23 (439 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: xfwm4
  UpgradeStatus: Upgraded to bionic on 2018-05-14 (22 days ago)

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

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


[Desktop-packages] [Bug 1666256] Re: Mouse Pointer flicking and blocked after locked screen with two displays

2018-09-01 Thread Theo Linkspfeifer
** Changed in: light-locker (Ubuntu)
   Status: New => Incomplete

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

** Changed in: xorg-hwe-16.04 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mouse Pointer flicking and blocked after locked screen with two
  displays

Status in light-locker package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete
Status in xorg-hwe-16.04 package in Ubuntu:
  Incomplete
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the HWE (Xubuntu 16.04.2) I am experiencing
  sometimes the following bug:

  When the screen is locked, I wake the displays up. The mouse pointer
  is flicking and cannot be moved. The keyboard is not responsive as
  well regarding the light locker.

  I can change to another terminal (via CTRL+ALT+F1) and quit the
  session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-locker 1.7.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 20 16:51:54 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-10 (893 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  SourcePackage: light-locker
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (133 days ago)

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

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


[Desktop-packages] [Bug 1359248] Re: Sound settings no longer works with Gnome Control Center Sound in Xfce

2018-08-28 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1359249 ***
https://bugs.launchpad.net/bugs/1359249

** This bug has been marked a duplicate of bug 1359249
   Launching PAVUControl works from Xubuntu, but not from Xfce

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

Title:
  Sound settings no longer works with Gnome Control Center Sound in Xfce

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

Bug description:
  In Ubuntu 12.04 I was able to install Gnome Control Center and
  indicator-sound and launch GNOME Control Center's audio options from
  the "Sound Settings" option in Indicator-Sound, but after upgrading to
  14.04 this is no longer possible - it loads GNOME-Control-Center
  showing only one or two icons, the only workaround being to manually
  launch "gksu gnome-control-center sound" which is less than ideal.

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

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


[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2018-08-26 Thread Theo Linkspfeifer
** Bug watch added: Debian Bug tracker #874003
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874003

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

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in nautilus package in Ubuntu:
  Confirmed
Status in nautilus package in Debian:
  Unknown

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1631964] Re: Password required twice returning from suspend

2018-08-26 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1631715 ***
https://bugs.launchpad.net/bugs/1631715

** This bug has been marked a duplicate of bug 1631715
   Password required twice returning from suspend

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

Title:
   Password required twice returning from suspend

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

Bug description:
  Clean install - no updates available. Also present on a previous
  install.

  Suspend machine and restart.

  Lock screen requiring password - enter password and return to
  suspended desktop.

  Within a few seconds machine locks and password is required once more.

  Using the same hardware I've installed nvidia 340.96 and tried to
  reproduce the issue without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 10 14:59:56 2016
  InstallationDate: Installed on 2016-06-11 (120 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1760078] Re: Double login required from suspend

2018-08-26 Thread Theo Linkspfeifer
*** This bug is a duplicate of bug 1631715 ***
https://bugs.launchpad.net/bugs/1631715

** This bug has been marked a duplicate of bug 1631715
   Password required twice returning from suspend

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

Title:
  Double login required from suspend

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Following a suspend.

  Get unlock screen - which then gets me a desktop.

  Returned to unlock screen to enter password a second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 12:09:46 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1515662] Re: Major security issue with light-locker - console switching gives access to other screens for a few seconds

2018-08-25 Thread Theo Linkspfeifer
Thanks for testing it again.

** Changed in: light-locker (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Major security issue with light-locker - console switching gives
  access to other screens for a few seconds

Status in light-locker package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  light-locker is completely insecure for X configurations with multiple
  screens that are not using a single display.

  My setup - 4 monitors, nvidia, each with separate screen.

  If I lock screen and then control-alt-f7 back to X, only one single
  screen is protected. After several seconds, it forces a switch to the
  lock display, but in the mean time, the other three screens are
  COMPLETELY UNPROTECTED.

  It only takes a few seconds to launch a terminal and killall light-
  locker and I have unrestricted access to all.

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

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


[Desktop-packages] [Bug 1515662] Re: Major security issue with light-locker - console switching gives access to other screens for a few seconds

2018-08-25 Thread Theo Linkspfeifer
Now almost three years and several versions later is this security issue
still present when using a multi monitor setup?

** Changed in: light-locker (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Major security issue with light-locker - console switching gives
  access to other screens for a few seconds

Status in light-locker package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  light-locker is completely insecure for X configurations with multiple
  screens that are not using a single display.

  My setup - 4 monitors, nvidia, each with separate screen.

  If I lock screen and then control-alt-f7 back to X, only one single
  screen is protected. After several seconds, it forces a switch to the
  lock display, but in the mean time, the other three screens are
  COMPLETELY UNPROTECTED.

  It only takes a few seconds to launch a terminal and killall light-
  locker and I have unrestricted access to all.

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

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


[Desktop-packages] [Bug 1559618] Re: light-locker appears to incorrectly handle Kerberos ticket cache filenames

2018-08-24 Thread Theo Linkspfeifer
I do not thing that this a bug in light-locker, but in lightdm.

Similar report: bug 1296276

** Package changed: light-locker (Ubuntu) => lightdm (Ubuntu)

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

Title:
  light-locker appears to incorrectly handle Kerberos ticket cache
  filenames

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When unlocking an Ubuntu 16.04 system which is using light-locker as
  the screen saver, Kerberos authentication works for a normal,
  unprivileged user, except that the resulting ticket cache is
  incorrectly named.  Instead of the resulting ticket cache created as a
  result of such successful authentication being named something like:

  krb5cc_1000 (if the UID of the user is 1000)

  ...the cache file is named:

  krb5cc_0 (which would presumably be correct if root were logging in,
  but not a normal, unprivileged user)

  I am willing to help debug this issue, so if there is anything you
  would like me to try, please let me know.

  Thanks,
  Brian

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-locker 1.7.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 22:32:52 2016
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-08-22 Thread Theo Linkspfeifer
Julian, thanks for the detailed comment.

I assume that the only way to somewhat work around this problem is to
change the recommendation orders:

lightdm: recommend lightdm-gtk-greeter | unity-greeter | ...
xfce4-session: recommend light-locker | xscreensaver

This may cause trouble and unexpected behavior for non Xubuntu users
though.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1633522] Re: gnome-control-center is missing items when run from the top ribbon

2018-08-22 Thread Theo Linkspfeifer
** This bug is no longer a duplicate of bug 1754872
   apt install xubuntu-desktop does not resolve dependencies properly

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

** Summary changed:

- gnome-control-center is missing items when run from the top ribbon
+ gnome-control-center is missing items when run from the top ribbon in Xfce

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

Title:
  gnome-control-center is missing items when run from the top ribbon in
  Xfce

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

Bug description:
  I am running an out-of-the-box xubuntu.

  raph@W500:~$ lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  If I click on the clock in the top ribbon and then on 'time and date
  settings' the gnome-control-center that pops up is missing my items.

  If I run 'gksu gnome-control-center' then all the items are  present.

  See attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfce4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Oct 14 16:21:49 2016
  InstallationDate: Installed on 2016-08-07 (67 days ago)
  InstallationMedia: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  SourcePackage: xfce4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1459417] Re: the numeric pad should provide the regional separator

2018-08-21 Thread Theo Linkspfeifer
With fr_FR I do get "." also, but in Calc it is a "," (probably fixed
there).

On the login screen, meaning outside of Xfce, it is still "."!

** Package changed: xfce4-settings (Ubuntu) => xkeyboard-config (Ubuntu)

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

Title:
  the numeric pad should provide the regional separator

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  When I type the "point/delete" key of my numeric pad, then the US "."
  (point) separator is entered instead of my regional "," (comma).

  When entering a lot of numbers in Calc for example, this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfce4 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May 27 22:02:18 2015
  SourcePackage: xfce4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-08-20 Thread Theo Linkspfeifer
** Summary changed:

- gnome-control-center is unusable on xubuntu-desktop, but called from Gear 
(About this Computer, System Settings) icon, Text Entry Settings, clock (Time & 
Date Settings)
+ apt install xubuntu-desktop does not resolve dependencies properly

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-08-20 Thread Theo Linkspfeifer
** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1490337] Re: Doubleclicking some.desktop file returns wrong %k variable

2018-08-20 Thread Theo Linkspfeifer
** Package changed: exo (Ubuntu) => thunar (Ubuntu)

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

Title:
  Doubleclicking some.desktop file returns wrong %k variable

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

Bug description:
  I have the following backup.desktop file on my removable HDD

  [Desktop Entry]
  Type=Application
  Name=Start Backup
  Exec=bash -c '%k/.backup.sh;$SHELL'
  OnlyShowIn=GNOME;Unity;MATE;LXDE;
  Icon=lxterminal
  Terminal=true
  X-KeepTerminal=true
  StartupNotify=true

  as it says here: http://standards.freedesktop.org/desktop-entry-
  spec/latest/ar01s06.html

  %k  The location of the desktop file as either a URI (if for
  example gotten from the vfolder system) or a local filename or empty
  if no location is known.

  doubleclicking it in PcmanFM acts as its expected - it opens
  lxterminal and runs .backup.sh

  while the same in Thunar returns:
  bash: /media/z/ZVs_WHITE/StartBackup.desktop/.backup.sh: Not a directory

  error happens in %k as it should return just path to some.desktop file
  instead it returns path+some.desktop in Thunar.

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

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


[Desktop-packages] [Bug 1490337] Re: Doubleclicking some.desktop file returns wrong %k variable

2018-08-20 Thread Theo Linkspfeifer
** Package changed: thunar (Ubuntu) => exo (Ubuntu)

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

Title:
  Doubleclicking some.desktop file returns wrong %k variable

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

Bug description:
  I have the following backup.desktop file on my removable HDD

  [Desktop Entry]
  Type=Application
  Name=Start Backup
  Exec=bash -c '%k/.backup.sh;$SHELL'
  OnlyShowIn=GNOME;Unity;MATE;LXDE;
  Icon=lxterminal
  Terminal=true
  X-KeepTerminal=true
  StartupNotify=true

  as it says here: http://standards.freedesktop.org/desktop-entry-
  spec/latest/ar01s06.html

  %k  The location of the desktop file as either a URI (if for
  example gotten from the vfolder system) or a local filename or empty
  if no location is known.

  doubleclicking it in PcmanFM acts as its expected - it opens
  lxterminal and runs .backup.sh

  while the same in Thunar returns:
  bash: /media/z/ZVs_WHITE/StartBackup.desktop/.backup.sh: Not a directory

  error happens in %k as it should return just path to some.desktop file
  instead it returns path+some.desktop in Thunar.

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

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


[Desktop-packages] [Bug 1447874] Re: Escaping DQUOTE in text section (VJOURNAL/description)

2018-08-20 Thread Theo Linkspfeifer
Fixed in libical.

Version 1.0.1:
--
* [Bug] issue74: Do not escape double quote character
* ...

https://github.com/libical/libical/blob/master/ReleaseNotes.txt

** Package changed: orage (Ubuntu) => libical (Ubuntu)

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

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

Title:
  Escaping DQUOTE in text section (VJOURNAL/description)

Status in libical package in Ubuntu:
  Fix Released

Bug description:
  When a journal entry is created and a string is added with DQUOTE
  characters in it the RFC5545 says in 3.8.1.5 that the description
  syntax is:

 description = "DESCRIPTION" descparam ":" text CRLF

  'text' is described in 3.3.11 as:

 text   = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
 
  That is DQUOTE is not escaped.

  But when   I create a journal entry (see screenshot) with DQUOTE in it
  the iCalendar file created by Orage (using File->Exchange
  Data->export) has the following

  BEGIN:VJOURNAL
  UID:Orage-20150415T224001Z0-1000@sharron
  CLASS:PUBLIC
  DTSTAMP:20150415T224006Z
  CREATED:20150415T224001Z
  LAST-MODIFIED:20150415T224006Z
  SUMMARY:A Journal Entry Orage
  DESCRIPTION:All day\nCategory \"Foobar\"\n
  CATEGORIES:Foobar
  DTSTART;VALUE=DATE:20150416
  END:VJOURNAL

  
  Note the escaped DQUOTE characters in the description field.  It should be:

  DESCRIPTION:All day\nCategory "Foobar"\n

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

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


[Desktop-packages] [Bug 1513387] Re: spinning wheel when using bridged setup

2018-08-19 Thread Theo Linkspfeifer
I assume that this bug is about nm-applet (network-manager-gnome).

** Package changed: xfce4-indicator-plugin (Ubuntu) => network-manager-
applet (Ubuntu)

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

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

Title:
  spinning wheel when using bridged setup

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  When I setup a bridge, having e.g. my local NIC connected to it and then 
giving the bridge IP information instead of the physical interface itself, the 
indicator just keeps showing this spinning wheel as if it was working or 
searching.
  Actually the interface is up and running without problem.
  Instead the sign of wifi should be displayed telling me about the connection 
quality.

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

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


[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-08-18 Thread Theo Linkspfeifer
Raphael, your comment does not appear to be related to this bug report.

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1785387] Re: Euro sign not working on keyboard (Macbook)

2018-08-18 Thread Theo Linkspfeifer
** Package changed: xfce4-settings (Ubuntu) => xkeyboard-config (Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Euro sign not working on keyboard (Macbook)

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  https://askubuntu.com/q/1059447/21005

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-settings 4.12.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug  4 13:18:18 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-05 (575 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xfce4-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-08-18 Thread Theo Linkspfeifer
Add a caret to the package name to replicate what tasksel does:

sudo apt install xubuntu-desktop^

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-08-18 Thread Theo Linkspfeifer
Explicitly installing light-locker will remove xscreensaver from the
list.

It looks like there are quite some oddities.

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-08-17 Thread Theo Linkspfeifer
xubuntu-desktop depends on lightdm-gtk-greeter, and yet while performing
the test case apt wants to pull in unity-greeter instead (see `apt
depends lightdm`). This will install various indicator- packages plus
gnome-control-center.

Explicitly installing the needed package gives the expected result:

sudo apt install xubuntu-desktop lightdm-gtk-greeter

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

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1775212] Re: Windows not painted completely since 18.04

2018-08-16 Thread Theo Linkspfeifer
I suggest that you download the Xubuntu 18.10 daily ISO, then boot into
live mode and check if the issue with the open source driver is present
too.

Another thing to test is to see if disabling the builtin compositor
(Settings > Windows Manager Tweaks > Compositor) eliminates the glitch.

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

Title:
  Windows not painted completely since 18.04

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

Bug description:
  Since upgrading to Xubuntu 18.04, the graphics on my desktop are
  broken. It seems to affect all windows and menus, which are painted
  incompletely, or with the wrong colours. It seems to get progressively
  worse, to the point of making programs unusable because entire
  sections of the user interface are missing, so this should have high
  priority IMHO. I will attach a few screenshots as examples.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfwm4 4.12.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  5 17:29:02 2018
  InstallationDate: Installed on 2017-03-23 (439 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: xfwm4
  UpgradeStatus: Upgraded to bionic on 2018-05-14 (22 days ago)

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

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


[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2018-08-16 Thread Theo Linkspfeifer
Does this bug still affect Xfce? If yes, please open a separate bug
report.

https://docs.xfce.org/xfce/xfce4-settings/display

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

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix
Status in xfwm4 package in Ubuntu:
  Invalid

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

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

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


[Desktop-packages] [Bug 1706357] Re: Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything

2018-08-14 Thread Theo Linkspfeifer
** Package changed: mousepad (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)

** Also 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 xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1706357

Title:
  Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything

Status in gnome-shell package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Selecting (or turning off) natural scrolling in settings->Mouse and
  Touchpad appears to do nothing, scrolling remains the same using a two
  finger scroll.

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

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


[Desktop-packages] [Bug 1500307] Re: xubuntu does not disable gtk overlay scrollbars (i.e. use solid scrollbars)

2018-08-14 Thread Theo Linkspfeifer
** Also affects: policykit-1 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: policykit-1 via
   https://bugs.freedesktop.org/show_bug.cgi?id=96713
   Importance: Unknown
   Status: Unknown

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  xubuntu does not disable gtk overlay scrollbars (i.e. use solid
  scrollbars)

Status in One Hundred Papercuts:
  Confirmed
Status in PolicyKit:
  Unknown
Status in policykit-1 package in Ubuntu:
  New
Status in xubuntu-default-settings package in Ubuntu:
  Opinion

Bug description:
  xubuntu does not disable gtk overlay scrollbars (i.e. use solid
  scrollbars)

  On this page http://tracker.xubuntu.org/ in the source code, Sean
  Davis is assigned to disable gtk3.16 overlay scrollbars in xubuntu-
  default-settings (i.e. use solid scrollbars) and
  https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-w-development
  shows also that the work is done.

  I am running xubuntu 15.10 beta 2 and this is not the case.

  Opening up ubuntu-modified programmes shows solid scrollbars (like the
  non-csd-ized, non-header-bar-ized evince), but synaptic shows overlay
  scrollbars.

  I find it very annoying. There is no visual clue of a scrollbar until
  I move my mouse over the window, and unlike Android or iOS scrollbars,
  the width changes and the transparency changes depending on how close
  my mouse is.

  Very hard to use.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xubuntu-default-settings 15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.365
  CurrentDesktop: XFCE
  Date: Mon Sep 28 04:43:49 2015
  LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-default-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-08-13 Thread Theo Linkspfeifer
Looks like the next step would be to test with an older NVIDIA driver
version from the Ubuntu repository, and maybe with the slightly newer
version 390.77 from the NVIDIA website also.

** Changed in: xfce4 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions

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


[Desktop-packages] [Bug 1591575] Re: Network Manager (nm-applet) not starting for new users

2018-08-13 Thread Theo Linkspfeifer
nm-applet has been updated in 16.04, so this bug needs to be verified
against the new version (1.2.6-0ubuntu0.16.04.4).

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

** Changed in: xfce4-panel (Ubuntu)
   Status: New => Incomplete

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

Title:
  Network Manager (nm-applet) not starting for new users

Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in xfce4-panel package in Ubuntu:
  Incomplete

Bug description:
  Expected Behavior:

  New system users, after their account is created, will login and have
  access to networking if they have the sufficient privileges.

  Real Behavior:
  Network Manager (nm-applet) is not available in the panel for new user 
accounts, and manually running nm-applet does not start the network manager.

  
  I needed to create 2 accounts for different users, and gave them 
administrator level and also permission to create and connect to networks.
  But nm-applet does not autostart and do not launches running from the 
terminal.  It simply won't say anything after running nm-applet.  There's no 
simple way to make it run.

  I followed the workarounds for previous releases, such:
  * making sure that "indicator plugin" is active on the panel,
  * and, in Application Autostart tab of "session and startup"
  * "network" is configured to autostart, 
  * "Indicator Application" are configured to not autostart,
  * added nm-applet command for it to autostart.

  As a system administrator I can't figure out what else should a user
  do to access networking.

  Network Manager is running for the default (1000) user. (BTW default user is 
connecting to WI-FI without specific permission to do it.)
  The new users accounts were given users ID below 1000 for they to not appear 
on login window.  (My need is to recreate a previously used users scheme, used 
on ubuntu studio 10.10, with the same users ID in order to copy user's files 
directly without messing with file permissions.)

  NOTE: We are running "ubuntu desktop" sessions, after installing
  "ubuntu studio" packages, on a fresh install of Ubuntu 16.04 LTS.  New
  users are being created on "users and gropus" option in the System
  category of the Whisker menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 11 19:22:19 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-06-09 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-08-13 Thread Theo Linkspfeifer
I suggested to test with MATE's compositing window manager "marco" also.
Any results?

Another test case would be to use xfwm4 with disabled compositor plus
"compton" (standalone compositing manager).

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions

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


  1   2   >