[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2020-05-20 Thread Eugene Lazutkin
@~seb128 After resuming from the lock screen. Ubuntu 20.04, upgraded from 19.10. BTW, Alt-F2 "r" doesn't help me because after that all windows become blurry and I have to reboot the computer, which is clearly unacceptable. -- You received this bug notification because you are a member of Ubuntu

[Bug 1799293] Re: gnome session: Must ask twice to lock the screen

2018-11-23 Thread Eugene Lazutkin
It affects me as well. But: 1) I have no auto-login. 2) I have no Dash to Dock installed, so I cannot even try the workaround from #7. 3) It is 100% reproducible. 4) If I don't lock the screen manually (that is with Win+L) everything works properly. In general, I have a feeling that after locki

[Bug 1726205] [NEW] gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

2017-10-22 Thread Eugene Lazutkin
Public bug reported: Cannot boot 17.10 in the lowlatency kernel (with nomodeset and no Wayland as recommended by some), but was able to boot in generic. Picture quality on the screen is very low, hard to read. In lowlatency it seems as the displays are trying to be set periodically, but nothing ha

[Bug 1029289] Re: Need to authorize my google account each time I boot the computer

2017-03-20 Thread Eugene Lazutkin
This bug has started to appear for me in 16.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the

[Bug 1313283] Re: gedit always prints in black and white on color printer

2014-05-27 Thread Eugene Lazutkin
Status of this ticket is incomplete: "Cannot be verified, the reporter needs to give more info" --- what kind of info is required? I submitted everything I was asked for in the manner it was requested. Please let me know what is missing, and I'll give more info. -- You received this bug notificat

[Bug 1313283] [NEW] gedit always prints in black and white on color printer

2014-04-27 Thread Eugene Lazutkin
Public bug reported: gedit shows syntax highlighting (with default Classic color scheme) properly, yet prints/previews text as black-and-white for a color printer (Xerox Phaser 6180DN in this case). Before 14.04 it used to print properly in color. ProblemType: Bug DistroRelease: Ubuntu 14.04 Pack

[Bug 1303122] [NEW] evolution-source-registry crashed with SIGSEGV in g_slice_alloc()

2014-04-05 Thread Eugene Lazutkin
*** This bug is a duplicate of bug 1235177 *** https://bugs.launchpad.net/bugs/1235177 Public bug reported: Crashed when I was away, and the workstation was locked. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution-data-server 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13

[Bug 833595] Re: gnome-settings-daemon crashed with SIGFPE in backlight_get_percentage()

2011-09-07 Thread Eugene Lazutkin
$ /usr/lib/gnome-settings-daemon/gsd-backlight-helper --get-max-brightness No backlights were found on your system $ /usr/lib/gnome-settings-daemon/gsd-backlight-helper --get-brightness No backlights were found on your system This is a real hardware, desktop with two LCD monitors and NVIDIA card.

[Bug 205415] Re: nautilus crashed with SIGSEGV in strlen()

2008-04-16 Thread Eugene Lazutkin
I wanted to share a directory, and was asked to install (Samba). When I clicked "Install" nautilus crashed. I tried to repeat it, and it crashed again. Interesting thing is I used to share those directories before the upgrade from 7.10 to 8.04, but somehow Samba was uninstalled during the upgrade.

[Bug 205415] Re: nautilus crashed with SIGSEGV in strlen()

2008-04-16 Thread Eugene Lazutkin
When I installed Samba using Synaptic I was able to share directories without any problems. -- nautilus crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/205415 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop