date:20171028

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  systemd RestartSec does not seem to work consistently

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

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

[Bug 1713363] Re: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package systemd 232-21ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

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

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

[Bug 1727057] Re: Drag and Drop Malfunction

2017-10-28 Thread Jeremy Bicha

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

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

** Tags added: wayland

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

Title:
  Drag and Drop Malfunction

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

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

[Bug 1727057] [NEW] Drag and Drop Malfunction

You have been subscribed to a public bug:

After upgrading from Ubuntu 17.04 64bit to 17.10 transferring a file
from one folder to another fails with drag and drop. The grab will move
the file but not drop it. It is as if the mouse-up does not register.
The grab remains but mouse will not release until I log out of my
account and log in again. The right click "move to" will work to move
files.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe   10841 F pulseaudio
 /dev/snd/controlC1:  joe   10841 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 13:31:02 2017
HibernationDevice: RESUME=UUID=8aeb251b-127a-4963-905c-dda8e223e0ba
InstallationDate: Installed on 2015-11-20 (703 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=159fdd5e-4a8b-4a5b-850f-5dabb27d2be3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
dmi.bios.date: 03/26/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: H67MA-USB3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/26/2012:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H67MA-USB3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful wayland-session
-- 
Drag and Drop Malfunction
https://bugs.launchpad.net/bugs/1727057
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to nautilus in Ubuntu.

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

[Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

This bug was fixed in the package gnome-software - 3.26.1-0ubuntu5

---
gnome-software (3.26.1-0ubuntu5) bionic; urgency=medium

  [ Jeremy Bicha ]
  * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch:
- Fix empty Addons > Shell Extensions category (LP: #1722809)

  [ Michael Biebl ]
  * Cherry-pick upstream fixes to make gnome-software build against fwupd 1.0.
(Closes: #879006)

 -- Jeremy Bicha   Sat, 28 Oct 2017 09:47:27 -0400

** Changed in: gnome-software (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

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

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

[Bug 1728332] [NEW] Files and documents get mounted on desktop during drag drop.

2017-10-28 Thread Frogs Hair

Public bug reported:

Release:Bionic Beaver Development release (18.04)

Session: Ubuntu/Wayland

Package: 1:3.26.0 0ubuntu1

Files get stuck on the desktop during drag & drop. The expected behavior
would be that the file would be able to move from the file manager to
the desktop and back. What is occurring is the file,document or pictures
get mounted and can't be moved or opened.

Work around: Use Ubuntu on Xorg session for desktop file operations.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 21:03:13 2017

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


** Tags: amd64 apport-bug bionic third-party-packages wayland-session

** Description changed:

  Release:Bionic Beaver Development release (18.04)
  
  Session: Ubuntu/Wayland
  
  Package: 1:3.26.0 0ubuntu1
  
  Files get stuck on the desktop during drag & drop. The expected behavior
  would that file would be able to move from the file manager to the
  desktop and back. What is occurring is the file,document or pictures get
  mounted and can't be moved or opened.
- 
  
  Work around: Use Ubuntu on Xorg session for desktop file operations.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:03:13 2017
- InstallationDate: Installed on 2017-10-15 (13 days ago)
- InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: nautilus
- UpgradeStatus: Upgraded to bionic on 2017-10-15 (13 days ago)

** Description changed:

  Release:Bionic Beaver Development release (18.04)
  
  Session: Ubuntu/Wayland
  
  Package: 1:3.26.0 0ubuntu1
  
  Files get stuck on the desktop during drag & drop. The expected behavior
- would that file would be able to move from the file manager to the
- desktop and back. What is occurring is the file,document or pictures get
- mounted and can't be moved or opened.
+ would be that the file would be able to move from the file manager to
+ the desktop and back. What is occurring is the file,document or pictures
+ get mounted and can't be moved or opened.
  
  Work around: Use Ubuntu on Xorg session for desktop file operations.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:03:13 2017

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

Title:
  Files and documents get mounted on desktop during drag  drop.

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Sorry, there were many different solutions posted so I wasn’t sure which
was the correct one.

So just to be clear, is the solution:

$ sudo apt purge gdm3

??

What’s the exact list of steps to resolve this?

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1728323] Re: totem crashed with SIGSEGV in cogl_renderer_connect()

2017-10-28 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1681210

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGSEGV in cogl_renderer_connect()

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

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

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

2017-10-28 Thread Had

I got this bug running a live CD after I switched the video drivers from
nouveau to nVidia's proprietary driver

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

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

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

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

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-28 Thread Vadim Peretokin

See the steps we've already posted to alleviate the issue. Remove gdm

On Sat, 28 Oct 2017, 11:00 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Sorry to spam the comments, there's no edit feature. Once again I have a
> black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
> get to a shell. How do I troubleshoot this?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

2017-10-28 Thread Felipe Figueiredo

Please see bug #228077 for information on the report upstream rejected
for gnome-control-center.

Leandro, I don't have a US keyboard anymore (nor did a read all the
comments here), but if this is still an issue, I don't think a fix will
appear anytime soon.

Good luck on this.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (46226).
https://bugs.launchpad.net/bugs/518056

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

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

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

[Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

2017-10-28 Thread Felipe Figueiredo

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

** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/228077

Title:
  libgtk2 immodules has cedilla disabled in en locales

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

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

[Bug 46226] Re: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

2017-10-28 Thread Felipe Figueiredo

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

** This bug is no longer a duplicate of bug 228077
   libgtk2 immodules has cedilla disabled in en locales
** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

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

Title:
  It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

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

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

[Bug 1727758] Re: Duplicated icon when application started

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

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  Duplicated icon when application started

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

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

[Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)

** Changed in: mutter
   Status: In Progress => Fix Released

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

Title:
  Shell font is blurry under Wayland (panels, menus and login screen
  too)

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

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

[Bug 1728311] [NEW] Ubuntu as default and Ubuntu n Xorg as default in 18.04 at login

2017-10-28 Thread desilvachan...@gmail.com

Public bug reported:

After today's upgrade, the default Ubuntu 18.04 login screen shows both
Ubuntu and Ubuntu on Xorg as default. (This 18.04 dev install uses
lightdm instead of gdm.) The screenshot is available at
https://ubuntuforums.org/showthread.php?t=2375934

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

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

Title:
  Ubuntu as default and Ubuntu n Xorg as default in 18.04 at login

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

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

[Bug 1131571] Re: Nautilus properties window "Content" number continuously counting

2017-10-28 Thread oddentity

Still a problem with stock Ubuntu 17.10.

Contrary to suggestions in the gnome bug report, I see this problem even
when none of the directories are or contain files that are symlinks.

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

Title:
  Nautilus properties window "Content" number continuously counting

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

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

[Bug 1727758] Re: Duplicated icon when application started

2017-10-28 Thread Nicolò Chieffo

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=789602
   Importance: Unknown
   Status: Unknown

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

Title:
  Duplicated icon when application started

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

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

[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

2017-10-28 Thread Jimmy Merrild Krag

Bummer. It just did it again after automatically shutting the screen
off.

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

Title:
  Screen blanking and/or screen lock crashes gnome-shell user session on
  wayland - Ubuntu 17.10 beta

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

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

[Bug 1728305] [NEW] Mouse (cursor) Mirroring

2017-10-28 Thread Rafael Bijos Faidiga

Public bug reported:

I have a 3 screen setup on a notebook with intel graphics. The left one is in 
portrait view, the center one is in normal view and right is in normal view 
(buildin).
When the mouse is in left side of the center monitor it shows on the left 
monitor bottom. 

The same problem is better described here:
https://askubuntu.com/questions/964239/ubuntu-17-10-cursor-mirrored-on-
second-screen. And since this isn't my post, it affects multiple users.

Thanks

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

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

Title:
  Mouse (cursor) Mirroring

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

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

[Bug 1574383] Re: Allow one to search through the "Installed" apps section

** Changed in: gnome-software
   Status: Incomplete => Expired

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

Title:
  Allow one to search through the "Installed" apps section

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

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

** Changed in: gvfs
   Status: Unknown => Invalid

** Changed in: gvfs
   Importance: Unknown => Critical

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

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 872876] Re: terminal window resizes when moving around window in awesome window manager

** Changed in: awesome (Debian)
   Status: New => Fix Released

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

Title:
  terminal window resizes when moving around window in awesome window
  manager

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Sorry to spam the comments, there's no edit feature. Once again I have a
black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
get to a shell. How do I troubleshoot this?

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Update: Went into a recovery shell as root, ran "dpkg-reconfigure
xserver-xorg". I got no output, no prompts, nothing. Rebooted, things
are OK now.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1726464] Re: Add option to disable sticky edges

2017-10-28 Thread Rasmus Eneman

I realized that this is only when I have the dock set to auto hide. With
always visible it's possible to move the cursor to the other screen
without issues.

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

Title:
  Add option to disable sticky edges

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

I take that back. Just rebooted, and I have a black screen with a
blinking cursor. Ugh.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1728295] Re: nautilus crashed with SIGSEGV

2017-10-28 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1726494
   nautilus crashed with SIGSEGV in stop_cache_selection_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV

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

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

[Bug 1727868] Re: New windows are unfocused and go below current window

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

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

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

Title:
  New windows are unfocused and go below current window

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Just wanted to weigh in: simply adding "nomodeset" to my kernel command
line worked! I was able to use the proprietary NVidia drivers, no
problem. I'm on a ThinkPad T570.

It looks like due to this change, I'm using X11 instead of Wayland. I
don't know if I care either way, everything works great and the graphics
are snappy. Hopefully Wayland will be ready by the time 18.04 launches.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

2017-10-28 Thread Jimmy Merrild Krag

I had the same issue in an Intel integrated graphics card (Core
i3-2120T). My whole session would just die.

My system is in Danish, so I am unsure if it is the power saving option
mentioned by @emanuel-pirsch I have disabled, but I went to the power
settings and disabled the second option that translated says something
like "Dim monitor on inactivity". This makes no sense enabling on my
computer since it is a desktop system with an external monitor.

The result is that it seems to have helped.

It makes me wonder if there is some sort of hardware detection that has
a bug?

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

Title:
  Screen blanking and/or screen lock crashes gnome-shell user session on
  wayland - Ubuntu 17.10 beta

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

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

[Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

2017-10-28 Thread Ragnar Dunbar

The above mentioned darker window edges in 17.10 do not appear in all
windows. They appear in Firefox, Thunderbird and e.g. the Gnome Terminal
(maybe this has to do with gnome-terminal being at 2.24). The window
decorations in for example the file-manager are not affected.

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

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

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

[Bug 1670089] Re: gnome-shell Crashes shortly after login

2017-10-28 Thread claudio@ubuntu

I think this is a gnome-shell-extension-dashtodock + gnome-shell-
extension-ubuntu-dock, at least in my case.

Removing gnome-shell-extension-dashtodock and reinstalling gnome-shell-
extension-ubuntu-dock allows me to login, however the dock is not
visible (it's not auto-hidden either, only visible with the meta key).

C.

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

Title:
  gnome-shell Crashes shortly after login

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

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

[Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  GTK3 menus don't work over SSH forwarding

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

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

[Bug 1724185] Re: Xwayland leaves no core dump or .crash file when crashing

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

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

Title:
  Xwayland leaves no core dump or .crash file when crashing

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

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

[Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

2017-10-28 Thread Jeremy Bicha

** Description changed:

- The Shell Extensions subcategory in GNOME Software is empty. I am using
- the latest (3.26.1-0ubuntu1) GNOME Software package.
+ Impact
+ ==
+ In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is 
empty. This makes it really difficult to browse for GNOME Shell extensions.
+ 
+ Test Case
+ =
+ Install the update.
+ Run Ubuntu/GNOME Software
+ It should prompt your to reload the Software app itself since it has been 
updated. (Or log out and log back in.)
+ On the home screen, click Addons. Click Shell Extensions.
+ It should show a list of available extensions after a few moments.
+ 
+ Regression Potential
+ 
+ This minimal patch was cherry-picked from the gnome-3-26 stable branch. 
Fedora 27 applies the patch.
+ 
+ Other Info
+ ==
+ The issue is that GNOME Software limited results to 500 but there are more 
than 800 Shell Extensions now. Maybe in the future, there should be some 
pagination or organization instead of a massive alphabetical list of extensions.
+ 
+ Workaround
+ ==
+ You can still look up and install a special GNOME Shell extension if you 
search for it.
+ 
+ Original Bug Report
+ ===
+ The Shell Extensions subcategory in GNOME Software is empty. I am using the 
latest (3.26.1-0ubuntu1) GNOME Software package.

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

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

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

[Bug 1726464] Re: Add option to disable sticky edges

2017-10-28 Thread Rasmus Eneman

>Is this the sticky edges feature, or generally a cursor barrier
problem?

I don't know if it's the correct name. But the cursor "sticks" on the
edge between the monitors. It should move just like it does when I drag
it on a single monitor.

>Are you dragging a window when the problem happens?

No, just normal mouse movement without any window, file or other thing
"picked up"

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

Title:
  Add option to disable sticky edges

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

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

2017-10-28 Thread Norbert

There is no bug in GVFS. The problem is old Android, which does not
support MTP i/o extensions. Android 5.0 and higher is not affected. On
4.0 - 4.4 user must copy file/folder from MTP-device to the local
storage and then open it from here.

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

** Tags removed: amd64

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

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 1728235] Re: Keyboard shortcut mapping side effect

2017-10-28 Thread Gunnar Hjalmarsson

I doubt that the keyboard shortcut feature is designed to work with a
single character as the shortcut. Try to involve some modifier key, e.g.
,  or  similarly as the predefined shortcuts.

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

Title:
  Keyboard shortcut mapping side effect

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

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

[Bug 1728246] [NEW] Apport shows the window without details, regularly

2017-10-28 Thread Александр

Public bug reported:

Apport shows the window without details, on a regular basis. Missing the 
ability to hide the replay and report an error. The program automatically shuts 
down without sending error report.
When you try to use ubuntu-bug -w displays a message "cannot report a problem: 
this package is installed not correctly"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 20:02:54 2017
InstallationDate: Installed on 2015-08-27 (792 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Apport shows the window without details, regularly

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

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

[Bug 1728055] Re: GDM3 hangs, if local home directory is not accessible

2017-10-28 Thread Michal Kukuča

This bug seems not to be related to GDM at all. This is a problem either
with automount, or mount.nfs4.

I did spend some time today digging around this and found out that the
hang lasts for several minutes, but then the system springs back to life
and the user list in the greeter will get populated.

Related stuff from journald (user testuser is an LDAP user, remote home; user 
localadmin is local - his home is not accessible):
okt 28 16:07:17 paulus systemd[1]: Starting GNOME Display Manager...
okt 28 16:07:17 paulus systemd[1]: Started Regular background program 
processing daemon.
okt 28 16:07:17 paulus automount[1566]: Starting automounter version 5.1.2, 
master map /etc/auto.master
okt 28 16:07:17 paulus automount[1566]: using kernel protocol version 5.02
okt 28 16:07:17 paulus automount[1566]: lookup_nss_read_master: reading master 
file /etc/auto.master
okt 28 16:07:17 paulus automount[1566]: do_init: parse(sun): init gathered 
global options: (null)
okt 28 16:07:17 paulus systemd[1]: Started GNOME Display Manager.
okt 28 16:07:17 paulus automount[1566]: lookup_read_master: lookup(file): read 
entry /home
okt 28 16:07:17 paulus automount[1566]: master_do_mount: mounting /home
okt 28 16:07:17 paulus automount[1566]: automount_path_to_fifo: fifo name 
/var/run/autofs.fifo-home
okt 28 16:07:17 paulus automount[1566]: lookup_nss_read_map: reading map file 
/etc/auto.home
okt 28 16:07:17 paulus automount[1566]: do_init: parse(sun): init gathered 
global options: (null)
okt 28 16:07:18 paulus automount[1566]: mounted indirect on /home with timeout 
300, freq 75 seconds
okt 28 16:07:18 paulus automount[1566]: st_ready: st_ready(): state = 0 path 
/home
okt 28 16:07:18 paulus systemd[1]: Started Automounts filesystems on demand.
okt 28 16:07:18 paulus systemd[1]: Reached target Multi-User System.
okt 28 16:07:18 paulus systemd[1]: Reached target Graphical Interface.
SNIP
okt 28 16:07:37 paulus automount[1566]: handle_packet: type = 3
okt 28 16:07:37 paulus automount[1566]: handle_packet_missing_indirect: token 
2, name testuser, request pid 1805
okt 28 16:07:37 paulus automount[1566]: attempting to mount entry /home/testuser
okt 28 16:07:37 paulus automount[1566]: lookup_mount: lookup(file): looking up 
testuser
okt 28 16:07:37 paulus automount[1566]: lookup_mount: lookup(file): testuser -> 
-fstype=nfs4,rw,intr,sec=krb5 petrus.(REDACTED):/home/&
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): expanded 
entry: -fstype=nfs4,rw,intr,sec=krb5 petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): gathered 
options: fstype=nfs4,rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): 
dequote("petrus.(REDACTED):/home/testuser") -> petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): core of entry: 
options=fstype=nfs4,rw,intr,sec=krb5, loc=petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: sun_mount: parse(sun): mounting root 
/home, mountpoint testuser, what petrus.(REDACTED):/home/testuser, fstype nfs4, 
options rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): root=/home 
name=testuser what=petrus.(REDACTED):/home/testuser, fstype=nfs4, 
options=rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): nfs 
options="rw,intr,sec=krb5", nobind=0, nosymlink=0, ro=0
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: called with host 
petrus.(REDACTED)(10.0.1.98) proto 6 version 0x40
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: nfs v4 rpc ping time: 
0.00
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: host petrus.(REDACTED) 
cost 0 weight 0
okt 28 16:07:37 paulus automount[1566]: prune_host_list: selected subset of 
hosts that support NFS4 over TCP
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): calling 
mkdir_path /home/testuser
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): calling mount 
-t nfs4 -s -o rw,intr,sec=krb5 petrus.(REDACTED):/home/testuser /home/testuser
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): mounted 
petrus.(REDACTED):/home/testuser on /home/testuser
okt 28 16:07:37 paulus automount[1566]: dev_ioctl_send_ready: token = 2
okt 28 16:07:37 paulus automount[1566]: mounted /home/testuser
okt 28 16:07:37 paulus automount[1566]: st_readmap: state 1 path /home
okt 28 16:07:37 paulus automount[1566]: re-reading map for /home
okt 28 16:07:37 paulus automount[1566]: lookup_nss_read_map: reading map file 
/etc/auto.home
okt 28 16:07:37 paulus automount[1566]: do_init: parse(sun): init gathered 
global options: (null)
okt 28 16:07:37 paulus automount[1566]: st_ready: st_ready(): state = 4 path 
/home
okt 28 16:07:37 paulus automount[1566]: handle_packet: type = 3
okt 28 16:07:37 paulus automount[1566]: handle_packet_missing_indirect: token 
3, name localadmin, request pid 1805
okt 28 16:07:37 paulus

[Bug 1728235] Re: Keyboard shortcut mapping side effect

2017-10-28 Thread Ragusa

I just discovered that with the Maj+§ shortcut (Corresponding to °), if
I try to insert an equal sign (=), guake opens too.

As the journalctrl command failed, you will find it as an attached file.


** Attachment added: "journalctl -b --priority=warning --lines=1000"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1728235/+attachment/4998741/+files/journal.txt

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

Title:
  Keyboard shortcut mapping side effect

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

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

[Bug 1728237] [NEW] After locking the screen to log in again does not work.

2017-10-28 Thread Александр

Public bug reported:

After locking the screen to log in again does not work. A window appears enter 
password after entering the password, the login attempt is made and re-enter 
the password. When trying to change user input in turn the standard interface 
login, enter the password and everything is repeated again.
However, you can get to the console login and reboot the computer. After the 
reboot, log normal.

Oct 28 18:48:02 aspire kernel: [  132.845148] Could not find key with 
description: [734b90750c0c1853]
Oct 28 18:48:02 aspire kernel: [  132.845155] process_request_key_err: No key
Oct 28 18:48:02 aspire kernel: [  132.845157] Could not find valid key in user 
session keyring for sig specified in mount option: [734b90750c0c1853]
Oct 28 18:48:02 aspire kernel: [  132.845159] One or more global auth toks 
could not properly register; rc = [-2]
Oct 28 18:48:02 aspire kernel: [  132.845162] Error parsing options; rc = [-2]
Oct 28 18:48:25 aspire kernel: [  155.805449] EXT4-fs (sdb1): mounted 
filesystem with ordered data mode. Opts: (null)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 19:15:03 2017
InstallationDate: Installed on 2015-08-27 (792 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  After locking the screen to log in again does not work.

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

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

[Bug 1728235] [NEW] Keyboard shortcut mapping side effect

2017-10-28 Thread Ragusa

Public bug reported:

I have defined a custom shortcut (/usr/bin/guake -t) on the key "§".
The shortcut § works fine, but if I press the letter "s" on my keyboard, Guake 
is opened as well.


What do I expect:
> That the letter s writes an s.
What's happening:
> Everytime I press "s", guake opens, but I can't use the letter "s" anymore.


I had to map a different shortcut (Maj §) and the "s" works fine.
PS: I am using the Swiss French keyboard configuration

Ubuntu 17.10
gnome-control-center:
  Installed: 1:3.26.1-0ubuntu4

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 16:12:21 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-05-21 (160 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-23 (4 days ago)

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


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

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

Title:
  Keyboard shortcut mapping side effect

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

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

[Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

This bug was fixed in the package accountsservice - 0.6.42-0ubuntu4

---
accountsservice (0.6.42-0ubuntu4) bionic; urgency=medium

  * debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
  ~/.pam_environment syntax (LP: #1722151).

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 22:02:00
+0200

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

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

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

[Bug 1728233] Re: gnome-control-center crashed with SIGSEGV in g_settings_get_value()

2017-10-28 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1725646
   gnome-control-center crashed with SIGSEGV in g_settings_get_value()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

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

[Bug 1728234] [NEW] zooming with mouse wheel seems dysfunctional in Ubuntu's eye of GNOME

2017-10-28 Thread Muelli

Public bug reported:

I cannot zoom in and out of pictures using the wheel.  Similarly, space bar for 
going to the next picture doesn't work.
The documentation claims that it should work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: eog 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 15:09:19 2017
InstallationDate: Installed on 2017-10-13 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  zooming with mouse wheel seems dysfunctional in Ubuntu's eye of GNOME

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

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

[Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

2017-10-28 Thread Dmitrii Shcherbakov

Hmm, for my installation upgraded from 17.04 it got fixed - I no longer
experience the issue.

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

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

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

[Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

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

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

[Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

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

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

[Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

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

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

[Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

2017-10-28 Thread Egmont Koblinger

This is a bug in GTK+, just recently fixed in git. For details, see
https://bugzilla.gnome.org/show_bug.cgi?id=789356
https://bugzilla.gnome.org/show_bug.cgi?id=789357


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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

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

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

[Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

2017-10-28 Thread Jeremy Bicha

** Also affects: gnome-software (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Artful)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

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

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

[Bug 1728232] [NEW] Nautilus misbehaviour under "unity-session" in Ubuntu 17.10

2017-10-28 Thread blue239

Public bug reported:

When the first opened instance of Nautilus is on Home folder and you try
to open a second instance with the middle click on the Nautilus icon,
nothing happens.

Under "ubuntu-session" there is no such deviation - another Nautilus instance 
is normally opened 
with the middle click no matter first one being opened at the Home folder.

Under "unity-session" with the first instance being opened on the Home folder, 
second instance can
be repeatedly opened only in two ways:
- by right clik on Nautilus icon and selecting something from context menu
- when the first open instance is opened in any other folder than Home, midlle 
click
  opens second instance of Nautilus normally

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

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

Title:
  Nautilus misbehaviour under "unity-session" in Ubuntu 17.10

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

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

[Bug 1728053] Re: Copy to USB is very slow

Some more info:
$ cat /proc/vmstat | egrep "dirty|writeback"
nr_dirty 0
nr_writeback 0
nr_writeback_temp 0
nr_dirty_threshold 0
nr_dirty_background_threshold 0

Each "0" ... Is that OK? (Original values!)

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

Title:
  Copy to USB is very slow

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

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

[Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

This bug was fixed in the package language-selector - 0.181

---
language-selector (0.181) bionic; urgency=medium

  * LanguageSelector/LocaleInfo.py:
Adapt to changed syntax in ~/.pam_environment (LP: #1722151).
  * LanguageSelector/ImConfig.py:
Prevent crash if LC_CTYPE is 'C' (LP: #1723318).
  * debian/control:
Bump Standards-Version to 4.1.1.

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 19:40:00
+0200

** Changed in: language-selector (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

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

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

[Bug 1707554] Re: Scrolling performance in gnome-logs is poor

** Changed in: gnome-logs
   Status: Confirmed => Fix Released

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

Title:
  Scrolling performance in gnome-logs is poor

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

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

[Bug 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode

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

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

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

Title:
  VLC under Wayland causes system freezes in fullscreen mode

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

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

[Bug 1719128] Re: Automatic login works only for wayland session

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

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

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

Title:
  Automatic login works only for wayland session

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

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

[Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

2017-10-28 Thread Kent Gibson

Logout.  Then at the login screen click on the gear icon next to the
Sign On button and select "Ubuntu on Xorg" and login.  (the default
selection "Ubuntu" uses Wayland now).

It's not absolutely critical to test this - I just thought it would be a
useful data point to show we're both seeing the same problem with totem
on Wayland.  But, if it works, then it is a viable workaround until it
gets fixed.

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

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

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

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

[Bug 1299604] Re: evolution keeps asking for password

2017-10-28 Thread Nic Knox

Staggering that this problem persists. I'm still running Ubuntu 14.04 [LTS!!]. 
Seems to re-emerge for me with updates [as of yesterday].
Just posting this in case there's a developer out there still monitoring this 
bug.
I expect to be told to move up from 14.04 ... but then what's the point of 
opting for LTSs?

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

Title:
  evolution keeps asking for password

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

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

[Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-28 Thread Nevet Dnulho

This bug has not occurred since removing the iio-sensor-proxy package.
Opening a bug report at https://github.com/hadess/iio-sensor-proxy/.

** Package changed: linux (Ubuntu) => iio-sensor-proxy (Ubuntu)

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1726160/+subscriptions

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

[Bug 1728223] Re: Mouse cursor visible on both screens in multiple monitor setup

2017-10-28 Thread Thomas Krause

Video of the two moving mouse cursors. The axis seems to be switched,
which could be caused by my rotated secondary screen.

** Attachment added: "Video of the two mouse cursors moving"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728223/+attachment/4998680/+files/two_mouse_cursors_moving.mp4

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

Title:
  Mouse cursor visible on both screens in multiple monitor setup

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

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

[Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

2017-10-28 Thread Calin

Is not clear to me if this was fixed or not?

I have the same issue on a brand new 17.10 installation.

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

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

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

[Bug 1728223] Re: Mouse cursor visible on both screens in multiple monitor setup

2017-10-28 Thread Thomas Krause

** Attachment added: "Monitor layout"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728223/+attachment/4998679/+files/two_mouse_cursors_monitor_layout.png

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

Title:
  Mouse cursor visible on both screens in multiple monitor setup

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

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

[Bug 1728223] [NEW] Mouse cursor visible on both screens in multiple monitor setup

2017-10-28 Thread Thomas Krause

Public bug reported:

When using two monitors (where the primary is on the right side and the
secondary is attached to the left), I can see two mouse cursors when the
cursor is near the left edge on the primary screen. Only the cursor on
the primary screen can click things, but it is still very confusing.

Also, the second cursor is moving with inverted axis.
Since the screenshot only captures the primary mouse cursor, I took a photo of 
the situation.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 13:09:49 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-19 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful third-party-packages wayland-session

** Attachment added: "Photo of the two mouse cursors"
   
https://bugs.launchpad.net/bugs/1728223/+attachment/4998674/+files/two_mouse_cursors.jpg

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

Title:
  Mouse cursor visible on both screens in multiple monitor setup

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

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

[Bug 1726160] [NEW] On login, display rotates to wrong orientation [HP Pavilion]

You have been subscribed to a public bug:

I'm using a laptop, and on 17.04 the display always showed correctly,
but after upgrading to 17.10,  when I log in the display rotates to the
right (portrait), and I have to open a terminal and run 'xrandr -o 1' to
get it back to the correct (landscape) orientation. In previous versions
'xrandr -o 0' was landscape, and '1' was portrait the other way.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:15:08 2017
DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
 nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
InstallationDate: Installed on 2017-01-11 (284 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
dmi.bios.date: 10/05/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1D
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 363C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 039D222412102
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: iio-sensor-proxy (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: amd64 apport-bug artful nvidia ubuntu
-- 
On login, display rotates to wrong orientation [HP Pavilion]
https://bugs.launchpad.net/bugs/1726160
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to iio-sensor-proxy in Ubuntu.

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

[Bug 1728222] [NEW] display updates are errornous during scrolling after starting search

2017-10-28 Thread Karl-Philipp Richter

Public bug reported:

Display updates are errornous during scrolling after starting search
when using LXDE desktop, see attached screenshot for details.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: LXDE
Date: Sat Oct 28 13:01:06 2017
InstallationDate: Installed on 2015-12-12 (685 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gedit
UpgradeStatus: Upgraded to artful on 2017-10-19 (8 days ago)

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


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

** Attachment added: "Bildschirmfoto vom 2017-10-28 13-00-33.png"
   
https://bugs.launchpad.net/bugs/1728222/+attachment/4998669/+files/Bildschirmfoto%20vom%202017-10-28%2013-00-33.png

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

Title:
  display updates are errornous during scrolling after starting search

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

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

[Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)

Launchpad has imported 21 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=984913.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-07-16T11:07:49+00:00 markm wrote:

Description of problem:

When trying to copy files from the camera using any software relaying on
gvfs-gphoto2, I get the following error: "Operation not supported by
backend"

Version-Release number of selected component (if applicable):

gvfs-ghoto2-1.16.3-2.fc19.x86_64

How reproducible:

always (on two different machines, tested with Caja, Nautilus, Thunar)

Steps to Reproduce:
1. Install gvfs-gphoto2
2. Connect camera
3. Browse images
4. Attempt to copy images

Actual results:

A popup error message appears "Operation not supported by backend"

Expected results:

Files copied without error message

Additional info:

$ gphoto2 -P
downloads all files with no issues

also installing any software capable of importing images (darktable,
shotwell) will import them without any issues too, though none of these
apps are installed by default on MATE Desktop, separate bug was filled
for it: https://bugzilla.redhat.com/show_bug.cgi?id=984908 ).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/0


On 2013-07-22T13:45:40+00:00 Jeff wrote:

Created attachment 776906
screenshot of error message

"Me too..."

Here's a screenshot showing the error. Marking with a priority of "high"
due to wife grief factor ;).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/1


On 2013-07-26T13:57:43+00:00 Paul wrote:

Ditto.

Opening the files directly in various editing packages and there is no
issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/2


On 2013-07-30T10:11:50+00:00 Cornelia wrote:

I have the same problem now, but only with a Canon Power Shot SX 260 HS,
while I don't have this problem with the old Nikon Coolpix 4100.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/3


On 2013-09-07T06:46:57+00:00 smanocch wrote:

Same problem with canon 50d

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/11


On 2013-09-18T04:47:14+00:00 Denis wrote:

Same problem with iPhone 5. The gvfs mount works fine in a terminal, but
copying the files in nautilus, which used to be the easiest way to
download the photos on F17, now just gives "Operation not supported by
backend" after upgrading to F19.

I am pretty sure the problem is with either gvfs or nautilus, not with
specific cameras. In fact, I am also not completely sure but I think the
iPhone uses gvfs-afc, not gvfs-gphoto2 -- so this may be a general
problem that affects more than one backend. gvfs-gphoto2 is probably not
the main culprit -- I'd look at the nautilus/gvfs interaction.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/14


On 2013-09-18T04:58:32+00:00 Denis wrote:

Ah, in fact, here's a lower-level manifestation of the same problem,
still on iPhone -- no nautilus or other file manager involved, it's
clearly 100% a gvfs problem. Someone with a camera with a gvfs-gphoto2
mount could try to confirm whether the same issue happens with gvfs-
gphoto2 as with gvfs-afc -- I suspect that's probably the case.

~ > gvfs-ls afc://e545[...]c3df/DCIM/100APPLE/
[...]
IMG_0462.JPG
IMG_0463.JPG
~ > gvfs-copy afc://e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG .
Error copying file afc://e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG: Operation 
not supported by backend
~ > ls /run/user/500/gvfs/afc:host=e545[...]c3df/DCIM/100APPLE/
[...]
IMG_0462.JPG
IMG_0463.JPG
~ > cp /run/user/500/gvfs/afc:host=e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG .
[file copies successfully]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/15


On 2013-09-26T15:04:57+00:00 Ejner wrote:

I have the same problem in Thunar filemanager.

Connecting a camera (eg. canon 50d) shows up immediately in Thunar
device list, and browsing images on the camera is possible, even
thumbnails are created. Trying to open an image in eg. Geeqie, by
double-clicking it in the filemanager, does not work however, and
neither does copy/paste from the gphoto2 location via the

[Bug 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell

2017-10-28 Thread sojusnik

Still in English in Ubuntu 17.10 ...

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

Title:
  System language isn't applied to gnome-control-center in Gnome-Shell

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

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

[Bug 1227440] Re: Nautilus' Format option doesn't actually work

** Changed in: gnome-disk-utility (Fedora)
   Status: Unknown => Fix Released

** Changed in: gnome-disk-utility (Fedora)
   Importance: Unknown => Medium

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

Title:
  Nautilus' Format option doesn't actually work

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

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

[Bug 893859] Re: gnome-shell doesn't support subpixel smoothing

** Changed in: gnome-shell
   Status: In Progress => Fix Released

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

Title:
  gnome-shell doesn't support subpixel smoothing

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

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

[Bug 1168662] Re: [PATCH] full screen flash not working in GNOME Shell

** Changed in: mutter (Fedora)
   Status: Unknown => Won't Fix

** Changed in: mutter (Fedora)
   Importance: Unknown => Undecided

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

Title:
  [PATCH] full screen flash not working in GNOME Shell

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

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

[Bug 1724703] Re: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_widget_translate_coordinates()

** Changed in: gnome-shell
   Status: Confirmed => Fix Released

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

Title:
  gnome-shell-extension-prefs crashed with SIGSEGV in
  gtk_widget_translate_coordinates()

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

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

[Bug 1727168] Re: Only use a header bar in GNOME shell

2017-10-28 Thread Khurshid Alam

@blue29

That's a separate issue. org.gnome.Nautilus can't be launched like that because 
'DBusActivatable=true' is set in 
/usr/share/applications/org.gnome.Nautilus.deskt
op

Please open a separate bug for that.

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

Title:
  Only use a header bar in GNOME shell

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

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

[Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

2017-10-28 Thread Ernest Kudron

how do I enter an xorg session?

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

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

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

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

[Bug 1103394] Re: [raring] History dialog does not decode UTF-8 (displays Ð·Ð° symbols)

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=964411.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2013-05-18T09:14:11+00:00 Igor wrote:

Description of problem:
history uses wrong encoding to show utf8 logs.

Version-Release number of selected component (if applicable):
since 3.6.3
empathy-3.8.1-2.fc19.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Send e.g. "Привет" ("Hello" in Russian)
2. Open Previous conversations

Actual results:
The last entry is "ÐÑÐ¸Ð²ÐµÑ"

Expected results:
Last entry will be "Привет"

Additional info:
I have checked that my logs in ~/.local/share/TpLogger/ are in utf8. Then I
downgrade empathy up to 3.6.2 and restart gnome-session. This is fixed my
problem. I have checked several times and can confirm that with empathy 3.6.2
the bug is not reproducible, but reproducible since 3.6.3.

The problem here is that g_strescape changed its specifications over time -
from the UTF-8-compatible "double every backslash" to ASCII-only "escape
everything except 0x20 through 0x7E". Would it be right to invent a new
backslash-doubling function for empathy-log-window.c specifically? Not pretty,
but passing a 128-character exception string to g_strescape is even less so.

This commit created this bug:
https://git.gnome.org/browse/empathy/commit/?h=gnome-3-6=1e7449f5a14e2f031389808206c9991f65d3ade7

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/5

On 2013-05-24T14:41:00+00:00 Fedora wrote:

empathy-3.8.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/empathy-3.8.3-1.fc19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/6

On 2013-05-24T19:49:05+00:00 Fedora wrote:

Package empathy-3.8.3-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing empathy-3.8.3-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9093/empathy-3.8.3-1.fc19
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/7

On 2013-05-26T03:44:40+00:00 Fedora wrote:

empathy-3.8.3-1.fc19 has been pushed to the Fedora 19 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/8

On 2013-06-26T15:06:04+00:00 Igor wrote:

Add patch as downstream (there will be no new releases in 3.8 branch)
https://git.gnome.org/browse/empathy/commit/?id=6bace22f3ffb9695870267e2a59858b3feeaa83e

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/9

On 2013-08-01T19:09:42+00:00 Fedora wrote:

empathy-3.8.3-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/empathy-3.8.3-2.fc19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/10

On 2013-08-02T21:59:25+00:00 Fedora wrote:

Package empathy-3.8.3-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing empathy-3.8.3-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14109/empathy-3.8.3-2.fc19
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/11

On 2013-08-06T00:12:30+00:00 Fedora wrote:

empathy-3.8.3-2.fc19 has been pushed to the Fedora 19 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1103394/comments/12

** Changed in: empathy (Fedora)
Status: Unknown => Fix Released

** Changed in: empathy (Fedora)
Importance: Unknown => Undecided

--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.

[Bug 1158307] Re: [bluetooth]: gnome-control-center crashed with SIGSEGV in bluetooth_chooser_get_selected_device_data()

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=965366.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-05-21T03:34:57+00:00 vinesh wrote:

Version-Release number of selected component:
control-center-3.8.2-1.fc19

Additional info:
reporter:   libreport-2.1.4
backtrace_rating: 4
cmdline:gnome-control-center sound
crash_function: bluetooth_chooser_get_selected_device_data
executable: /usr/bin/gnome-control-center
kernel: 3.9.2-301.fc19.x86_64
runlevel:   N 5
uid:1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 bluetooth_chooser_get_selected_device_data at bluetooth-chooser.c:231
 #1 bluetooth_chooser_get_selected_device at bluetooth-chooser.c:250
 #2 connect_done at cc-bluetooth-panel.c:176
 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #4 complete_in_idle_cb at gsimpleasyncresult.c:789
 #8 g_main_context_iteration at gmain.c:3762
 #9 g_application_run at gapplication.c:1623

Potential duplicate: bug 804857

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/6


On 2013-05-21T03:35:03+00:00 vinesh wrote:

Created attachment 750817
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/7


On 2013-05-21T03:35:08+00:00 vinesh wrote:

Created attachment 750818
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/8


On 2013-05-21T03:35:12+00:00 vinesh wrote:

Created attachment 750819
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/9


On 2013-05-21T03:35:18+00:00 vinesh wrote:

Created attachment 750820
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/10


On 2013-05-21T03:35:23+00:00 vinesh wrote:

Created attachment 750821
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/11


On 2013-05-21T03:35:27+00:00 vinesh wrote:

Created attachment 750822
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/12


On 2013-05-21T03:35:33+00:00 vinesh wrote:

Created attachment 750823
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/13


On 2013-05-21T03:35:39+00:00 vinesh wrote:

Created attachment 750824
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/14


On 2013-05-21T03:35:43+00:00 vinesh wrote:

Created attachment 750825
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/15


On 2013-05-21T03:35:48+00:00 vinesh wrote:

Created attachment 750826
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/16


On 2013-08-14T15:43:00+00:00 Olivier wrote:

Trying to connect to a another Fedora 19 machine using bluetooth

reporter:   libreport-2.1.6
backtrace_rating: 4
cmdline:gnome-control-center bluetooth
crash_function: bluetooth_chooser_get_selected_device_data
executable: /usr/bin/gnome-control-center
kernel: 3.9.9-302.fc19.x86_64
package:control-center-3.8.3-2.fc19
reason: Process /usr/bin/gnome-control-center was killed by signal 11 
(SIGSEGV)
runlevel:   N 5
uid:500

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
bluetooth/+bug/1158307/comments/17


On 2015-01-09T18:09:48+00:00 Fedora wrote:

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.

[Bug 1232419] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=967087.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-05-24T16:19:45+00:00 sam wrote:

Version-Release number of selected component:
gnome-settings-daemon-3.8.1-1.fc19

Additional info:
reporter:   libreport-2.1.4
backtrace_rating: 4
cmdline:/usr/libexec/gnome-settings-daemon
crash_function: notify_have_shell
executable: /usr/libexec/gnome-settings-daemon
kernel: 3.9.0-301.fc19.x86_64
runlevel:   N 5
uid:42

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 notify_have_shell at gsd-xsettings-manager.c:719
 #1 call_in_idle_cb at gdbusnamewatching.c:180
 #6 gtk_main at gtkmain.c:1156

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/0


On 2013-05-24T16:19:49+00:00 sam wrote:

Created attachment 752765
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/1


On 2013-05-24T16:19:53+00:00 sam wrote:

Created attachment 752766
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/2


On 2013-05-24T16:19:56+00:00 sam wrote:

Created attachment 752767
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/3


On 2013-05-24T16:20:00+00:00 sam wrote:

Created attachment 752768
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/4


On 2013-05-24T16:20:03+00:00 sam wrote:

Created attachment 752769
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/5


On 2013-05-24T16:20:10+00:00 sam wrote:

Created attachment 752770
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/6


On 2013-05-24T16:20:14+00:00 sam wrote:

Created attachment 752771
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/7


On 2013-05-24T16:20:18+00:00 sam wrote:

Created attachment 752772
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/8


On 2013-05-24T16:20:21+00:00 sam wrote:

Created attachment 752773
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/9


On 2013-05-24T16:20:25+00:00 sam wrote:

Created attachment 752774
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1232419/comments/10


On 2015-01-09T18:12:49+00:00 Fedora wrote:

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-

[Bug 1217916] Re: While editing main menu, xfce4-panel crashed with SIGSEGV in fast_validate()

** Changed in: alacarte (Fedora)
   Status: Unknown => Won't Fix

** Changed in: alacarte (Fedora)
   Importance: Unknown => Undecided

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

Title:
  While editing main menu, xfce4-panel crashed with SIGSEGV in
  fast_validate()

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

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

[Bug 1728053] Re: Copy to USB is very slow

The previously "dirty" values are original. Are these values normal?

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

Title:
  Copy to USB is very slow

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

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

[Bug 1067876] Re: Missing "Safely Remove Drive" option from Quicklists. Only have "Eject".

Launchpad has imported 25 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=919194.

On 2013-03-07T19:57:33+00:00 Nrbrtx wrote:

Removing powered device from USB port is unsafe operation. It is not
sufficient to unmount/eject drive, it must be completely powered off
before removal.

Please bring back "Safely remove" to Nautilus.

I tried 4 Transcend flashes, 1 ADATA, 2 no-name (SMI and ChipsBnk). They remain
powered after eject - it's DANGEROUS for my (and anybody's) data.
I tried external USB-SATA Tsunami HDD - Disks does not spin down (stop) it -
It's DANGEROUS for my (and anybody's) data.

This bug come from Nautilus. Ubuntu is affected by this bug too (see
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876,
https://bugs.launchpad.net/nautilus/+bug/1127135).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/59

On 2013-03-07T20:05:58+00:00 Nrbrtx wrote:

I can detach USB-flash or HDD from console with "udisks --detach
/dev/sdX", but it is not simple way for linux-newbies.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/60

On 2013-03-10T18:24:53+00:00 Nrbrtx wrote:

On other laptop (Asus T101MT) Transcend flash is remounted automatically
by Nautilus (?) after "udisks --detach /dev/sdX".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/62

On 2013-03-12T17:23:12+00:00 Nrbrtx wrote:

I tested 4 flashes and 1 USB HDD - you can read my test report
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHJBalI2b09TQ2ZNOHJOQnhFbEVXaXc).
The conclusion is very bad: I tested Ubuntu 12.04 LTS, Ubuntu 13.04, Fedora
18, OpenSuse 12.3. All they can't remove power from USB drives like it was in
GNOME 2 and previous versions of GNOME 3.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/66

On 2013-03-13T08:30:54+00:00 Martin wrote:

I reported that to https://bugzilla.gnome.org/show_bug.cgi?id=695281
some days ago. It seems to me that either many USB sticks are lying and
claim that they have removable media, or it's a bug in the kernel driver
that sets "removable=1" for them.

Nrbtx, note that it's not quite dangerous -- devices are still
"eject"ed, which means unmounting everything and releasing the media.
The actual USB device remains powered up, but that's not a concern for
data safety.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/68

On 2013-03-13T08:42:16+00:00 Nrbrtx wrote:

I don't think so.
Removing a powered device is not a good idea anyway (especially rotating
USB-HDD).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/69

On 2013-03-21T19:43:49+00:00 Nrbrtx wrote:

Safely remove is partially working under Fedora 19 alpha (from
http://fedorapeople.org/groups/qa/20130320-gnome/20130320-gnome-i686.iso).
Nautilus showed Safely remove option for 1 of my 5 flashes and USB-HDD.
It powered off 1 of my 5 flashes, but USB-HDD did not spin down.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/75

On 2013-03-21T20:56:38+00:00 Cosimo wrote:

-> gvfs

As Martin says in comment #4, Nautilus' behavior didn't change here
anytime recently, but gvfs/udisks apply different heuristics now, which
are reflected in the options available to the GIO clients like Nautilus.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/77

On 2013-04-27T14:14:52+00:00 Nrbrtx wrote:

Bug still exists in Fedora 18 with latest updates.
Please inform GNOME developers and fix this bug using joint efforts.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/89

On 2013-04-28T17:16:52+00:00 Nrbrtx wrote:

Bug exists in Gnome 3.8 (Fedora 19).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/comments/92

On 2013-05-23T14:41:50+00:00 Fedora wrote:

This package has changed

[Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=923349.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-03-19T16:05:11+00:00 nicu wrote:

When you don't use the mouse for a long enough time, the mouse
disconnects and won't reconnect. I have to go into bluetooth settings,
remove it, and re-pair it.

This is the same bug as here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744

I have bluez-4.101-6.fc18.x86_64


How reproducible:
every time

Steps to Reproduce:
1. wait to enter standby
2. exit standby by pressing any key
3. try to move mouse, mouse is disconnected
  
Expected results:
mouse pointer should move


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/7


On 2013-03-19T16:32:19+00:00 nicu wrote:

dmesg output when first connecting:

[25476.140823] hid-generic 0005:045E:077C.000A: unknown main item tag 0x0
[25476.141156] input: Microsoft Sculpt Touch Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input26
[25476.141905] hid-generic 0005:045E:077C.000A: input,hidraw0: BLUETOOTH HID 
v1.1e Mouse [Microsoft Sculpt Touch Mouse] on 9c:b7:0d:ab:1c:ee

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/8


On 2013-03-20T19:34:57+00:00 nicu wrote:

I have observed that the pairing is also lost when a new device is
inserted, like a usb stick. Otherwise, the pairing lasts 20 minutes
max...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/9


On 2013-06-28T02:06:38+00:00 Dimitris wrote:

I see what I think is the same problem with:

bluez-4.101-8.fc19.x86_64.rpm
kernel 3.9.5-301.fc19.x86_64
Thinkpad Laser Mouse

- [Re-]discover mouse and pair:

Jun 27 18:48:45 gaspode bluetoothd[10091]: bluetoothd[10091]: Discovery session 
0x7f898f20a5c0 with :1.453 activated
Jun 27 18:48:45 gaspode bluetoothd[10091]: Discovery session 0x7f898f20a5c0 
with :1.453 activated
Jun 27 18:48:47 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:47 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:50 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:50 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:54 gaspode bluetoothd[10091]: bluetoothd[10091]: Stopping discovery
Jun 27 18:48:54 gaspode bluetoothd[10091]: Stopping discovery
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: unknown main 
item tag 0x0
Jun 27 18:48:56 gaspode kernel: input: ThinkPad Bluetooth Laser Mouse as 
/devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input22
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: input,hidraw3: 
BLUETOOTH HID v2.00 Mouse [ThinkPad Bluetooth Laser Mouse] on 00:27:13:96:48:a
Jun 27 18:48:56 gaspode /etc/gdm/Xsession[1422]: ** Message: has_config_widget 
F0:65:DD:67:A2:B9 HumanInterfaceDeviceService

- After using the mouse for a little, bit, turn it off (hardware
switch); then, a little while later:

Jun 27 18:49:35 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:49:40 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Adapter 
/org/bluez/10091/hci0 has been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: Adapter /org/bluez/10091/hci0 has 
been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0
Jun 27 18:51:22 gaspode bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0

- Turn mouse back on; Nothing happens (was expecting it to reconnect).  The 
machine is a Thinkpad X200s using a:
Bus 004 Device 009: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
built-in adapter.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/24


On 2013-12-21T12:17:56+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open

[Bug 1202159] Re: Nautilus crashes when reconnecting to network file server

** Changed in: nautilus (Fedora)
   Status: Unknown => Won't Fix

** Changed in: nautilus (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Nautilus crashes when reconnecting to network file server

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

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

[Bug 1196523] Re: gedit crashed with SIGSEGV in magazine_chain_pop_head()

Launchpad has imported 21 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=957434.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-04-28T07:01:54+00:00 Cheng-Chia wrote:

Description of problem:
1. I use gedit to edit a existing file ( I am upload it later)
2. I selected one of Chinese characters
3. I pressed Super + Space to switch to ibus-chewing input engine which I set 
with GNOME Settings.
4. I pressed "j" key with ibus-chewing
5. gedit crashed

Version-Release number of selected component:
gedit-3.8.1-1.fc19

Additional info:
backtrace_rating: 4
cmdline:gedit /home/zerng07/Translations/anjuta.gnome-3-8.zh_TW.po
crash_function: magazine_chain_pop_head
executable: /usr/bin/gedit
kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64
runlevel:   N 5
uid:1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 pango_attr_list_new at pango-attributes.c:1113
 #4 pango_attr_list_filter at pango-attributes.c:1992
 #5 filter_no_shape_attributes at pango-layout.c:3812
 #6 pango_layout_check_lines at pango-layout.c:3872
 #7 pango_layout_get_extents_internal at pango-layout.c:2534
 #8 pango_layout_get_extents at pango-layout.c:2729
 #9 gtk_text_layout_get_line_display at gtktextlayout.c:2438

Potential duplicate: bug 750087

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/0


On 2013-04-28T07:02:07+00:00 Cheng-Chia wrote:

Created attachment 741062
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/1


On 2013-04-28T07:02:10+00:00 Cheng-Chia wrote:

Created attachment 741063
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/2


On 2013-04-28T07:02:17+00:00 Cheng-Chia wrote:

Created attachment 741064
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/3


On 2013-04-28T07:02:21+00:00 Cheng-Chia wrote:

Created attachment 741065
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/4


On 2013-04-28T07:02:25+00:00 Cheng-Chia wrote:

Created attachment 741066
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/5


On 2013-04-28T07:02:27+00:00 Cheng-Chia wrote:

Created attachment 741068
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/6


On 2013-04-28T07:02:43+00:00 Cheng-Chia wrote:

Created attachment 741069
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/7


On 2013-04-28T07:02:48+00:00 Cheng-Chia wrote:

Created attachment 741070
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/8


On 2013-04-28T07:02:50+00:00 Cheng-Chia wrote:

Created attachment 741071
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/9


On 2013-04-28T07:02:55+00:00 Cheng-Chia wrote:

Created attachment 741072
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/10


On 2013-04-28T07:50:55+00:00 Cheng-Chia wrote:

Created attachment 741083
The file which I edited from.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/11


On 2013-07-01T16:15:58+00:00 Jiro wrote:

Steps to reproduce
==
1. Launch gedit
2. Open a file in any format whose syntax gedit can recognize to highlight the 
text
3. Move the cursor to any position where strings highlighted
4. Input Japanese characters through ibus and try to convert them with the 
space key there, and gedit cranshes

reporter:   libreport-2.1.5

[Bug 1202768] Re: Cannot play DVB

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=920962.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-03-13T07:49:29+00:00 tomas wrote:

Description of problem:
when totem is starting, it stay without dvd or dvb in menu. if totem starts dvd 
from nautilus, it run ok. 

Version-Release number of selected component (if applicable):
3.8.2-206.fc18.x86_64
totem 3.6.3
How reproducible:
write totem on commanline

Steps to Reproduce:
1.
2.
3.
  
Actual results:

totem

(totem:8090): Grilo-WARNING **: [registry] grl-registry.c:330: Failed to
initialize plugin: '/usr/lib64/grilo-0.2/libgrlflickr.so'

(totem:8090): Grilo-WARNING **: [registry] grl-registry.c:330: Failed to
initialize plugin: '/usr/lib64/grilo-0.2/libgrltmdb.so'

(totem:8090): Grilo-WARNING **: [registry] grl-registry.c:787: Failed to open 
module: '/usr/lib64/grilo-0.2/libgrlpodcasts.so'
Failed activating DVB DBus service 'NoneType' object has no attribute 
'set_image'
Traceback (most recent call last):
  File "/usr/lib64/totem/plugins/dvb-daemon/dvb-daemon.py", line 680, in 
_on_group_loaded
self._configure_mode()
  File "/usr/lib64/totem/plugins/dvb-daemon/dvb-daemon.py", line 481, in 
_configure_mode
self.single_group = self.channels[group_iter][self.channels.COL_GROUP]
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 782, in 
__getitem__
aiter = self._getiter(key)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 776, in 
_getiter
aiter = self.get_iter(key)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 798, in 
get_iter
path = TreePath(path)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1209, in 
__new__
if len(path) == 0:
TypeError: object of type 'NoneType' has no len()

** (totem:8090): WARNING **: Error creating GUPnP context: Failed to
find IP of interface ttyUSB0


Expected results:


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1202768/comments/0


On 2013-07-16T21:56:16+00:00 Sylvain wrote:

I get this bug with Fedora 19.
Same stacktrace.
totem-3.8.2-1.fc19.x86_64
gnome-dvb-daemon-0.2.10-2.fc19.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1202768/comments/1


On 2013-12-15T21:20:59+00:00 Stefano wrote:

Same bug on Fedora 19.

totem-3.8.2-1.fc19.x86_64
gnome-dvb-daemon-0.2.10-2.fc19.x86_64

$ totem
Failed activating DVB DBus service 'NoneType' object has no attribute 
'set_image'
Traceback (most recent call last):
  File "/usr/lib64/totem/plugins/dvb-daemon/dvb-daemon.py", line 680, in 
_on_group_loaded
self._configure_mode()
  File "/usr/lib64/totem/plugins/dvb-daemon/dvb-daemon.py", line 481, in 
_configure_mode
self.single_group = self.channels[group_iter][self.channels.COL_GROUP]
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 767, in 
__getitem__
aiter = self._getiter(key)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 755, in 
_getiter
aiter = self.get_iter(key)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 789, in 
get_iter
path = self._coerce_path(path)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 764, in 
_coerce_path
return TreePath(path)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1114, in 
__new__
path = ":".join(str(val) for val in path)
TypeError: 'NoneType' object is not iterable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1202768/comments/5


On 2013-12-21T12:06:40+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora

[Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

2017-10-28 Thread Ragnar Dunbar

In the attached screenshot one can see that there is a difference in the
color of the outer pixels of the screen edge. In 17.10 there is a darker
grey. Both windows were in the front, when the screenshots were taken.
To me, due to the less smooth transition of colors, the screen edges in
17.10 look somewhat rough, ripped.

** Attachment added: "window_edges.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+attachment/4998650/+files/window_edges.png

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

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

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

[Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

2017-10-28 Thread Kent Gibson

You can exit mpv by pressing "q" - that one caught me as well.

Does totem work for you in an xorg session?

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

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

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

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

Re: [Bug 1727330] Re: is not adjusted for natural scrolling in the mouse control panel

2017-10-28 Thread Александр

2017-10-27 8:18 GMT+05:00 Daniel van Vugt
:

> Sorry the image in comment #3 seems to have gone missing.
>
> Please open:  Settings > Devices > Mouse & Touchpad
> Now take a screenshot with Alt+PrtScn and attach it here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1727330
>
> Title:
>   is not adjusted for natural scrolling in the mouse control panel
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   is not adjusted for natural scrolling in the mouse control panel.
>   Change the position of the switch does not change the settings.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-shell 3.26.1-0ubuntu4
>   ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
>   Uname: Linux 4.10.0-33-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Oct 25 17:57:58 2017
>   DisplayManager: lightdm
>   GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2015-08-27 (789 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   SourcePackage: gnome-shell
>   UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1727330/+subscriptions
>


** Attachment added: 
"=?UTF-8?B?0KHQvdC40LzQvtC6INGN0LrRgNCw0L3QsCDQvtGCIDIwMTctMTAtMjggMTQtMTItMjYucG5n?="
   
https://bugs.launchpad.net/bugs/1727330/+attachment/4998607/+files/%3D%3FUTF-8%3FB%3F0KHQvdC40LzQvtC6INGN0LrRgNCw0L3QsCDQvtGCIDIwMTctMTAtMjggMTQtMTItMjYucG5n%3F%3D

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

Title:
  is not adjusted for natural scrolling in the mouse control panel

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

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

[Bug 613809] Re: [FFe] gnomeradio NO SOUND, no /dev/mixer present

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=904775.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-01-27T13:49:46+00:00 triniton wrote:

Description of problem:

When will alsa support to gnomeradio?
Currently, you can not use the up and down arrow keys for volume management.
The new systems, throwing the OSS, and there is no /dev/mixer.

It possible like someone implement alsa support ( including alsa mixer )
like in tvtime.

Thanks

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/42


On 2013-01-29T18:05:54+00:00 POJAR wrote:

I write a patch ( ubuntu gnomeradio version ) to support for looping
back audio through alsa devices ( including mixer control ).

Should be tested in several types of tv/fm tuners and then all the work
will be made public.

Package for ubuntu is here:
https://launchpad.net/~geoubuntu/+archive/test

Best regards.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/43


On 2013-01-30T01:20:52+00:00 Raymond wrote:

post the output of alsa-info.sh


did you connect your radio to line in or aux of your onboard sound ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/45


On 2013-01-30T07:34:40+00:00 POJAR wrote:

My radio tuner is connected to line in.

In function of your tuner, change "Mixer Source" from "Preference" to:

default/Line or
default/CD or
hw:0/Line or
etc.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/46


On 2013-01-30T07:45:24+00:00 POJAR wrote:

Created attachment 690203
alsa info

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/47


On 2013-01-30T08:27:03+00:00 Raymond wrote:

you have to unmute  line playback switch and change line playback volume
using alsamixer -c0

no need to change capture source to line since you are using the analog
mixer of AC97 codec to mix the input signal from line in to line out

set line playback to 0dB

amixer -c 0 set Line playback 72% unmute


the output volume is controlled by master playback volume and switch


Simple mixer control 'Line',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive penum
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]


control.18 {
iface MIXER
name 'Line Playback Switch'
value false
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.19 {
iface MIXER
name 'Line Playback Volume'
value.0 0
value.1 0
comment {
access 'read write'
type INTEGER
count 2
range '0 - 31'
dbmin -3450
dbmax 1200
dbvalue.0 -3450
dbvalue.1 -3450
}
}

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/48


On 2013-03-27T15:33:03+00:00 POJAR wrote:

Probably one of the most popular questions I see new users ask about
gnomeradio is along the lines of the following:

"It looks like gnomeradio is working (showing me gui), but for some
reason I am not hearing any audio. What is wrong with my tuner?"

Unfortunately, in the vast majority of cases, there is nothing wrong
with the tuner. The problem is that gnomeradio was originally designed
to be used with older tuner cards that have a dedicated audio output
cable, which you are expected to connect to speakers. Most newer tuner
products deliver their audio via an ALSA device, for which gnomeradio
has no mechanism to route the audio to soundcard.

As a result, users end to run sox or arecord/aplay in a separate
terminal window (which always seemed like a rather ridiculous
workaround).

Solution: Added support for

[Bug 1069757] Re: [Upstream] Libreoffice: problems with saving docs to directories of Windows networks (through samba-connection)

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=895690.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-01-15T19:18:25+00:00 Grosswiler wrote:

Description of problem:

When saving a file in libreoffice, using the mounted gvfs-path, the
following error occurs. Libreoffice cannot get closed then and needs to
be killed in the shell.

Errors:
"Error saving this document: the file doesn't exist" and then after OK, this
"Error saving this document: general error. general i/o-error"

-> Saving to /run/user/[userno.]/gvfs/ works!!

Version-Release number of selected component (if applicable):
Version 3.6.3.2 (Build ID: 3.6.3.2-8.fc1


How reproducible:
Always

Steps to Reproduce:
1. Open Libreoffice, create any new file
2. save file to a share using gvfs (preferable on a samba-share)
3. Get the error
  
Actual results:
Cannot save file to this path.


Expected results:
Saving File to the Path indicated in the save-as-path-dialogue to the left.


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/20


On 2013-02-28T15:32:35+00:00 Caolan wrote:

caolanm->sberg: is the a dup of the X-GIO-NoFuse=true issue or something
else ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/37


On 2013-02-28T15:54:23+00:00 Stephan wrote:

Does the problem go away when you select "Tools - Options... -
LibreOffice - General - Open/Save dialogs - Use LibreOffice dialogs"
first?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/38


On 2013-02-28T17:10:07+00:00 Grosswiler wrote:

i have changed this in libreoffice, now 2 situations occure:

Prerequisite: i saved the samba-share as a favourite within libreoffice
in the open/save-dialogue

i always open a file within nautilus and want to save it.

1) i save clicking on the favourite folder and type a filename: The
error comes up as described above

2) i use the path, which libreoffice seems to have and points to the
local resource /run/user/100n/gvfs/[share] - this works

and if i open the file within libreoffice without nautilus, both
described situations

1) the same, it won't save

2) the same, it saves.

it works always using the path from /run...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/39


On 2013-02-28T17:11:06+00:00 Grosswiler wrote:

and no, it doesn't go away.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/40


On 2013-03-13T11:08:02+00:00 Stephan wrote:

(upstream fix is

"rhbz#895690: Make GIO UCP less brittle, so saving docs works again")

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/45


On 2013-03-14T10:39:16+00:00 Fedora wrote:

libreoffice-3.6.5.2-7.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/libreoffice-3.6.5.2-7.fc18

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/47


On 2013-03-15T00:08:46+00:00 Fedora wrote:

Package libreoffice-3.6.5.2-7.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-3.6.5.2-7.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3868/libreoffice-3.6.5.2-7.fc18
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/53


On 2013-03-15T13:40:10+00:00 Grosswiler wrote:

Installed, tested and left posivite karma.

Thx!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757/comments/55


On 2013-03-15T20:07:45+00:00 Fedora wrote:

libreoffice-3.6.5.2-8.fc18 has been submitted as an update for Fedora 18.

[Bug 1235446] Re: evolution-calendar-factory crashed with SIGSEGV in socket_connected()

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=908465.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-02-06T18:43:32+00:00 Andrea wrote:

Version-Release number of selected component:
evolution-data-server-3.4.4-4.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:/usr/libexec/evolution-calendar-factory
crash_function: socket_connected
kernel: 3.7.3-101.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 socket_connected at soup-socket.c:675
: #1 soup_socket_connect_sync at soup-socket.c:829
: #2 soup_connection_connect_sync at soup-connection.c:664
: #3 get_connection at soup-session-sync.c:209
: #4 process_queue_item at soup-session-sync.c:297
: #5 send_message at soup-session-sync.c:390
: #6 send_and_handle_redirection at e-cal-backend-caldav.c:1010
: #7 caldav_server_list_objects at e-cal-backend-caldav.c:1343
: #8 synchronize_cache at e-cal-backend-caldav.c:1951
: #9 caldav_synch_slave_loop at e-cal-backend-caldav.c:2310

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/0


On 2013-02-06T18:43:36+00:00 Andrea wrote:

Created attachment 694090
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/1


On 2013-02-06T18:43:38+00:00 Andrea wrote:

Created attachment 694091
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/2


On 2013-02-06T18:43:41+00:00 Andrea wrote:

Created attachment 694092
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/3


On 2013-02-06T18:43:44+00:00 Andrea wrote:

Created attachment 694093
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/4


On 2013-02-06T18:43:46+00:00 Andrea wrote:

Created attachment 694094
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/5


On 2013-02-06T18:43:49+00:00 Andrea wrote:

Created attachment 694095
File: smolt_data

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/6


On 2013-02-06T18:43:51+00:00 Andrea wrote:

Created attachment 694096
File: executable

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/7


On 2013-02-06T18:43:54+00:00 Andrea wrote:

Created attachment 694097
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/8


On 2013-02-06T18:43:57+00:00 Andrea wrote:

Created attachment 694098
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/9


On 2013-02-06T18:43:59+00:00 Andrea wrote:

Created attachment 694099
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/10


On 2013-02-06T18:44:01+00:00 Andrea wrote:

Created attachment 694100
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/11


On 2013-02-06T18:44:04+00:00 Andrea wrote:

Created attachment 694101
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/12


On 2013-02-07T08:17:31+00:00 Milan wrote:

Thanks for a bug report. There had been reported a similar bug report
already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 892913 ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/13


** Changed in: evolution-data-server

[Bug 1728053] Re: Copy to USB is very slow

Note: Previously there were no such anomalies at 16.04... After many updates 
and patches to the LTS version come in, I'm not sure what to do with the 
phenomenon.
But it is a fact that several weeks exist

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

Title:
  Copy to USB is very slow

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

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

[Bug 1728053] Re: Copy to USB is very slow

Typically, e.g. Select a file (desktop) > drag and drop copying / moving > 
target USB flash drive / external USB hard disk
I do not typically use a command line

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

Title:
  Copy to USB is very slow

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

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

2017-10-28 Thread Norbert

** Description changed:

  Steps to reproduce:
  1. Connect MTP-device to laptop
  2. Caja file browser opens
  3. Navigate to the needed file on MTP-device with Caja
  
  4a. Try to open text file with Pluma from Caja or from terminal:
  Unexpected error: libmtp error: Unknown error.
  
  4b. Try to open text file with `cat`:
  
  $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
  cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error
  
  4c. Try to open video file with `vlc` from Caja or from terminal:
  
  $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
  card/video.mkv
  
  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f00c4000f48] filesystem access error: read error: Input/output error
  [7f00c4001408] core stream error: cannot pre fill buffer
  
  4d. Try to open Markdown file with ReText from Caja or from terminal:
  Retext opens with empty document
  
  4e. Try to open docx-file with LibreOffice from Caja or from terminal:
  get error window with text "General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx."
  
  4f. Try to open ppt, pptx, xls, xlsx, odp, odt, or doc-file with LibreOffice 
from Caja or from terminal:
  get error window with text "General Error.
- The seek operation could not be run." 
+ The seek operation could not be run."
  or empty document
  
  4g. Try to open png- or jpg- image file with Eye of MATE from Caja or from 
terminal:
  "libmtp error: Unknown error."
+ 
+ Note: tested with two Android devices - with Android 4.1.2 and 4.4.4.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 28 00:35:42 2017
  InstallationDate: Installed on 2014-02-07 (1358 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

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

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 1064394] Re: User already logged in error message sometimes, after login fails

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=868220.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-10-19T09:58:11+00:00 Jens wrote:

Description of problem:
After an authentication error, when I login using fallback GDM
I am now longer able to start a desktop session.

Version-Release number of selected component (if applicable):
gdm-3.6.0-1.fc18
gdm-3.6.1-1.fc18

How reproducible:
100%

Steps to Reproduce:
1. install f18 with gdm
2. remove gnome-shell (if necessary)
3. login with gdm fallback
4. logout
5. authenticate in gdm with wrong password
6. try to login again and wait for desktop session to start
  
Actual results:
6. login succeeds but gdm hangs after authentication
   showing last login failure message and/or last login info.
   User is shown as logged in with green check icon
   but desktop session does not start.
   Pressing cancel reverts to gdm login but repeating
   gives same result.

Expected results:
6. desktop session to start normally.

Additional info:
Does not happen with gnome-shell GDM.
"Workaround" is to restart gdm.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1064394/comments/3


On 2012-10-30T02:29:54+00:00 Matthias wrote:

sounds similar to the earlier problems where the old session is not
quite ending and keeping gdm from creating a new one.

What does loginctl list-sessions say after the logout ?
If the session you just ended still shows up, what does loginctl session-status 
say for it ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1064394/comments/4


On 2012-11-01T04:55:16+00:00 Jens wrote:

Yeah somewhat similar but this happens with no prior X desktop session.

After the failed authentication, no hanging session:

# loginctl list-sessions 
 1 42 gdm  seat0   
 2  0 root seat0

2 sessions listed.

After successful login (see screenshot attached below):

# loginctl list-sessions 
 1 42 gdm  seat0   
 2  0 root seat0   
 3   1000 petersen seat0 

3 sessions listed.
# loginctl session-status 3
3 - petersen (1000)
   Since: Wed, 31 Oct 2012 21:55:35 -0400; 1min 13s ago
  Leader: 1013 (gdm-session-wor)
Seat: seat0; vc1
 Display: :0
 Service: gdm-password; type x11; class user
   State: online
  CGroup: name=systemd:/user/petersen/3
  ├ 1013 gdm-session-worker [pam/gdm-password]
  └ 1022 /usr/bin/gnome-keyring-daemon --daemonize --login
# loginctl show-session 3
Id=3
Timestamp=Wed, 31 Oct 2012 21:55:35 -0400
TimestampMonotonic=275751659
DefaultControlGroup=name=systemd:/user/petersen/3
VTNr=1
Display=:0
Remote=no
Service=gdm-password
Leader=1013
Audit=3
Type=x11
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=petersen

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1064394/comments/5


On 2012-11-01T04:56:28+00:00 Jens wrote:

Created attachment 636460
screenshot of gdm hanging around after login

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1064394/comments/6


On 2012-11-01T05:00:06+00:00 Jens wrote:

Pressing Cancel goes back to gdm login, but repeating the process
it is not possible to login as that user without restarting gdm.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1064394/comments/7


On 2012-11-30T19:11:24+00:00 Tim wrote:

There has been no movement on this in almost a month and no new reports.
Is this still happening with F18 beta? Does it happen if fallback is
forced via preferences instead of removing shell?

I'm -1 blocker, though. While it could be seen as a violation of the
following F18 beta release criterion:

All release-blocking desktops' offered mechanisms (if any) for shutting
down, logging out and rebooting must work.

If I'm understanding correctly, the user is logged out. They just can't
log back in afterwards. I realize that I might be splitting hairs here
but it wouldn't affect lives as users wouldn't usually be logging out
from a live session (thus fixable with an update post-install) and
sounds like it could be worked around with a system reboot or restarting
gdm. I can't see blocking release

[Bug 1082232] Re: gnome-screensaver 3.6 does not unlock

** Changed in: gnome-screensaver (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gnome-screensaver (Fedora)
   Importance: Unknown => Undecided

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

Title:
  gnome-screensaver 3.6 does not unlock

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

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

[Bug 1127777] Re: nautilus 3.6 SIGSEGV in g_str_has_suffix()