[Bug 1796265] Re: Ubuntu Dock is missing after unlocking screen

[prasanna]

I have exactly the same issue. Started recently. All my gnome extensions
including the lock symbol disappear after returning from an unlock.

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

Title:
  Ubuntu Dock is missing after unlocking screen

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

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

[Bug 1796265] Re: Ubuntu Dock is missing after unlocking screen

[prasanna]

Another odd behavior. If I unlock the screen using a  on the
keyboard, things come back fine. But if I click on the screen with the
mouse, then the desktop does not return to its normal settings.

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

Title:
  Ubuntu Dock is missing after unlocking screen

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

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

[Bug 1195725] Re: Nautilus window jumping with dual monitors

[Prasanna Kannappan]

I want to add that I am experiencing the same behavior with chromium-
browser too. When I open a browser window on my external monitor and
start typing into the address bar, it moves the window to my other
monitor (laptop monitor) in a dual monitor configuration.

It doesn't look like a nautilus bug. It looks more like a windows
manager bug.

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

Title:
  Nautilus window jumping with dual monitors

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

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

[Bug 1195725] Re: Nautilus window jumping with dual monitors

[Prasanna Kannappan]

I flipped the configuration of my monitors so that the leftmost part of
my display configuration is my external monitor and to the right is the
laptop screen. Now I see that the windows opened in my laptop screen
moving to my external monitor after the first double click on maximized
nautilus or typing into the address bar of the maximized chrome-browser.
This brings me to the conclusion that the window is forced to the
leftmost monitor.

Let me know if you need any more information.

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

Title:
  Nautilus window jumping with dual monitors

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

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

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Prasanna Kumar]

Updated from Ubuntu 13.10 to 14.04. Keyboard input is sluggish. When
typing one letter appears after I type the next one.

While changing brightness using fn + brightness key notification appears
but the brightness change after a long time or does not change at all. I
am using a Lenovo ThinkPad L430.

Note: I did not have any such problem with Ubuntu 13.10 or previous
version in the same laptop.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

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

[Bug 1450812] [NEW] Dragging image in original resolution in eog package leads to lightdm restart

[Prasanna Kannappan]

Public bug reported:

When open an image. eog displays it in its original resolution. If I
accidentally click on the image and drag it, it leads to restart of
lightdm in ubuntu 12.04. I do not have this problem in ubuntu 14.04.

I found a similar question in askubuntu
http://askubuntu.com/questions/590240/image-viewer-eog-causes-lightdm-to-restart

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: eog 3.4.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-82.119-generic 3.2.68
Uname: Linux 3.2.0-82-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Fri May  1 10:39:30 2015
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eog
UpgradeStatus: Upgraded to precise on 2014-11-19 (163 days ago)

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


** Tags: amd64 apport-bug precise running-unity third-party-packages

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

Title:
  Dragging image in original resolution in eog package leads to lightdm
  restart

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

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

[Bug 1633825] [NEW] System goes to emergency mode as /boot/efi could not be mounted

[Prasanna Kumar]

Public bug reported:

System was booting normally with 16.04. Upgraded to 16.10, system goes
to emergency console on every boot. This happened due to timeout in
mounting /boot/efi. Commented out /boot/efi entry in /etc/fstab. System
boots after that. But wifi, bluetooth and sound does not start
automatically now. I have to load iwlwifi module to start wifi,
snd_hda_intel to get sound working. I am using a Lenovo G50-80 laptop.
Everything was working fine in 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sun Oct 16 15:22:05 2016
InstallationDate: Installed on 2015-11-20 (330 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:07dc Intel Corp. 
 Bus 001 Device 003: ID 0c45:6513 Microdia 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80E5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=e3865c00-93d9-4ed7-a9a4-35f9a0d1b16f ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)
dmi.bios.date: 07/23/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: B0CN93WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo G50-80
dmi.board.vendor: LENOVO
dmi.board.version: 31900059 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
dmi.product.name: 80E5
dmi.product.version: Lenovo G50-80
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

Title:
  System goes to emergency mode as /boot/efi could not be mounted

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

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

[Bug 136740] Re: Eye of Gnome displays images in incorrect order

[Kevin Selva Prasanna]

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

2016 and still no solution

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

Title:
  Eye of Gnome displays images in incorrect order

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

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

[Bug 1679226] [NEW] gedit consumes 100% of cpu when left minimised

[Kevin Selva Prasanna]

Public bug reported:

When left minimised, gedit on ubuntu takes up 30 to 50% of CPU. When I
maximise it to use it again, the CPU usage drops to zero. I tried
purging and reinstalling gedit many times. But it doesn't help. The
issue starts a few seconds after opening gedit. But the issue is so
serious, that I cannot use it more than a few seconds without heating up
my computer.

OS
==
Description:Ubuntu 16.04.2 LTS

INSTALLED VERSION
=
gedit:
  Installed: 3.18.3-0ubuntu4

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

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

Title:
  gedit consumes 100% of cpu when left minimised

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

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

[Bug 1812753] Re: gnome-control-center crash

[Prasanna V. Loganathar]

Hi Sebastien, I'm afraid I'm not entirely sure. I had this crash dump
again and again in a clean installed laptop that's up to date for the
last couple of weeks. So, thought I'll file it. Please do feel free to
close it if you think it may be redundant.

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

Title:
  gnome-control-center crash

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

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

[Bug 1834748] Re: shotwell crashed with SIGSEGV in library_window_switch_to_page

[Prasanna V. Loganathar]

** Summary changed:

- shotwell crash on startup
+ shotwell crashed with SIGSEGV in library_window_switch_to_page

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

Title:
  shotwell crashed with SIGSEGV in library_window_switch_to_page

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

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

[Bug 1834748] Re: shotwell crash on startup

[Prasanna V. Loganathar]

Here's the gdb stack trace:

```
$ gdb /usr/bin/shotwell ./core.3036 
GNU gdb (Ubuntu 8.2.91.20190405-0ubuntu3) 8.2.91.20190405-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/shotwell...
Reading symbols from 
/usr/lib/debug/.build-id/de/5ef1027f855c42246be8090cc8484e5f2123ac.debug...
[New LWP 3036]
[New LWP 3051]
[New LWP 3088]
[New LWP 3084]
[New LWP 3085]
[New LWP 3087]
[New LWP 3134]
[New LWP 3089]
[New LWP 3086]
[New LWP 3049]
[New LWP 3093]
[New LWP 3094]
[New LWP 3091]
[New LWP 3090]
[New LWP 3110]
[New LWP 3095]
[New LWP 3092]
[New LWP 3074]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `shotwell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f306a883d40 in g_menu_model_get_n_items () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
[Current thread is 1 (Thread 0x7f3066bb1b00 (LWP 3036))]
(gdb) where
#0  0x7f306a883d40 in g_menu_model_get_n_items () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1  0x7f3069e60c31 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x7f3069e615ab in gtk_application_window_set_show_menubar () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x558796026d17 in library_window_switch_to_page 
(self=self@entry=0x558798503f70, page=page@entry=0x5587987ef8c0) at 
../src/library/LibraryWindow.vala:1310
#4  0x558796029065 in library_window_switch_to_import_queue_page 
(self=0x558798503f70) at ../src/library/LibraryWindow.vala:951
#5  0x5587960c42b6 in run_system_pictures_import 
(external_exclusion_manifest=) at ../src/main.vala:246
#6  0x5587960c42b6 in run_system_pictures_import 
(external_exclusion_manifest=) at main.c:1837
#7  0x5587960c4de7 in library_exec (mounts=, 
mounts_length1=) at ../src/main.vala:205
#8  0x5587960c5654 in _vala_main (args=, 
args_length1=) at ../src/main.vala:460
#9  0x558795fba3f0 in main (argc=, argv=) at 
../src/main.vala:347
(gdb) thread apply all bt

Thread 18 (Thread 0x7f3064a34700 (LWP 3074)):
#0  0x7f30692f8729 in __GI___poll (fds=0x5587981858f0, nfds=1, 
timeout=25000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f306a678bf6 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a678d1c in g_main_context_iteration () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3064d35ffd in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f30477fe700 (LWP 3092)):
#0  0x7f30692fe2e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f306a6c393f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a64a0db in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f306a6a2217 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f3045ffb700 (LWP 3095)):
#0  0x7f30692fe2e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f306a6c393f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a64a0db in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f306a6a2217 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f300700 (LWP 3110)):
#0  0x7f30692f8729 in __GI___poll (fds=0x7f3004007030, nfds=3, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f304c0569f1 in  () at /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f304c048260 in pa_mainloop_poll () at 
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f304c0488ae in pa_mainloop_iterate () at 
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f304c048960 in pa_mainloop_run () at 

[Bug 1834748] Re: shotwell crash on startup

[Prasanna V. Loganathar]

Ok, looks my core dump is corrupted. Marking as "incomplete", as there's
nothing actionable here without it.

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

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

Title:
  shotwell crash on startup

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

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

[Bug 1834748] [NEW] shotwell crash on startup

[Prasanna V. Loganathar]

Public bug reported:

Random crash on startup

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: shotwell 0.30.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 29 22:37:24 2019
InstallationDate: Installed on 2019-06-23 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  shotwell crash on startup

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

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