[Bug 254906] [NEW] Nautilus Samba connect gives not mounted error

[Vincent Gerris]

Public bug reported:

Binary package hint: nautilus

Similar to bug 198531.
The complete error is:
The specified location is not mounted .

I am using Ubuntu 8.04 Hardy Heron.
and GNOME nautilus 2.22.3

Expected behaviour:
 1. Go to Places menu
 2. Select 'Connect to Server...'
 3. Select Service Type 'Windows Share'
 4. Enter valid value for Server: , User: Share: and Domain:
 5. Press 'Connect'
 6. Fill in password
 7. Window appears containing contents of remote samba share

Behaviour:
Instead of step 7, there is an error:
The specified location is not mounted
There is a link to the share created on the Desktop to the samba share, so 
authentication works.
When clicking that link, another link appears on the Desktop, which is exactly 
the same.

So the problem seems to be an error that says not mounted, while it is mounted.
Also the second mount link appearing on the desktop should not happen.

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

-- 
Nautilus Samba connect gives not mounted error
https://bugs.launchpad.net/bugs/254906
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 254906] Re: Nautilus Samba connect gives not mounted error

[Vincent Gerris]

** Attachment added: screenshot1.png
   http://launchpadlibrarian.net/16554386/screenshot1.png

-- 
Nautilus Samba connect gives not mounted error
https://bugs.launchpad.net/bugs/254906
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

Re: [Bug 339783] Re: Separate X-screen, apps launched from 2nd screen appear on first screen

[Vincent Gerris]

Dear Sebastien,

In my opinion, this is not a duplicate?
This bug is about applications not starting on the right screen, the other
is specificly on loading.
Please don't simply try to close off bugs, although I know that is
important.
I do believe the bugs are related, unfortunately Gnome devs are silent.

regards,
Vincent

On Thu, May 14, 2009 at 12:26 AM, Sebastien Bacher
seb...@ubuntu.comwrote:

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

 could people stop commenting on this duplicate bug?

 --
 Separate X-screen, apps launched from 2nd screen appear on first screen
 https://bugs.launchpad.net/bugs/339783
 You received this bug notification because you are a direct subscriber
 of the bug (via bug 290935).

 Status in “gnome-desktop” source package in Ubuntu: New
 Status in “gnome-panel” source package in Ubuntu: Invalid
 Status in “nvidia-graphics-drivers-180” source package in Ubuntu: New

 Bug description:
 My system is using NVidia's separate X-screen instead of TwinView. If I
 click Places-Home Folder in the 2nd screen it opens in the first screen.
 This is 100% reproducible.

 Same behaviour observed if running
 DISPLAY=:0.1 nautilus --browser
 or if running from Alt-F2

 However, for gnome-terminal, running from the menus opens it in the wrong
 (first) screen, but running
 DISPLAY=:0.1 gnome-terminal
 or running from Alt-F2 opens it in the correct (2nd) screen.

 Firefox/thunderbird open properly in the 2nd screen in all cases.
 Compiz-config settings manager has same behaviour as gnome-terminal. Problem
 seems to be non-app specific.

 http://ubuntuforums.org/showthread.php?t=1089578 shows another user with
 the same problem. May be linked to the binary nvidia, am unable to test
 without since I'm not aware of any way to get separate X with nv or mesa.

 [lspci]
 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960
 Memory Controller Hub [8086:2a00] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:1517]
 01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 9300M
 G [10de:042e] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:17c2]



-- 
Separate X-screen, apps launched from 2nd screen appear on first screen
https://bugs.launchpad.net/bugs/339783
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 87317] Re: Screensaver just detects idle time on one screen

[Vincent Gerris]

I can confirm this bug on my fresh install of 8.04 (Hardy Heron) running dual 
monitors with NVIDIA driver.
Using two seperate screens.

After updating to Ubuntu 8.10 and creating a new xorg.conf , the problem
persists.

Gnome-screensaver seems to be causing more trouble, for example with focus on 
tsclient, but that is another story.
https://bugs.launchpad.net/ubuntu/+source/tsclient/+bug/48108
Thought I'd mention it, it might be related.

My xorg.conf is attached, please pm if you need more info.
For now, I just removed the gnome-screensaver package.

NVidia driver version is 177.80.

** Attachment added: Xorg config file
   http://launchpadlibrarian.net/19590043/xorg.conf

-- 
Screensaver just detects idle time on one screen
https://bugs.launchpad.net/bugs/87317
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

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

[Bug 289241] Re: Gnome-panel freezes when starting an application on the secondary display

[Vincent Gerris]

I can confirm this bug on 8.10 with Nvidia 5500 Graphics card and 1.73 version 
of their driver on a dual X server setup.
It only happens when Visual appaearance is on normal.
When switching it to none and putting it back on normal, the problem does not 
appear.
only workaround on hang is to kill gnome-panel .

If anyone needs more info, i am more than willing to help.

-- 
Gnome-panel freezes when starting an application on the secondary display
https://bugs.launchpad.net/bugs/289241
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

I have the same problem on Ubuntu 9.04 (after upgrade from 8.10).
This might be related to the bug that lets nautilus start on the wrong screen?
Pedro, please be clear in what info you want, i can reproduce this bug.
No use in trying to close bugs all the time, while the idea is to get them 
fixed and enjoy a properly working Ubuntu i think?

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

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

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 290935] Re: dual screen all panels end up on one screen at startup

[Vincent Gerris]

I reported it upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

I also added a link to this post.
I hope it gets solved quickly :)!

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

-- 
dual screen all panels end up on one screen at startup
https://bugs.launchpad.net/bugs/290935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 290935] Re: dual screen all panels end up on one screen at startup

[Vincent Gerris]

the link Idm uses is probably:
http://bugzilla.gnome.org/show_bug.cgi?id=561964

-- 
dual screen all panels end up on one screen at startup
https://bugs.launchpad.net/bugs/290935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

added upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

seems to habe happened before:
http://bugzilla.gnome.org/show_bug.cgi?id=561964


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

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

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 289241] Re: Gnome-panel freezes when starting an application on the secondary display

[Vincent Gerris]

Well, I am on 11.04 now, so impossible for me.
Maybe this bug can be abandoned?

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

Title:
  Gnome-panel freezes when starting an application on the secondary
  display

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

The glibc bug seems to be fixed, a patch is supplied here:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

I have not seen an updated package for ubuntu 9.04 yet.
Does anyone know how to achieve this?

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed = Fix Committed

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

Here is the applied fix.
Can anyone point out how this can be applied to the package?

** Attachment added: glib-fix.patch
   http://launchpadlibrarian.net/30266458/glib-fix.patch

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 339783] Re: Separate X-screen, apps launched from 2nd screen appear on first screen

[Vincent Gerris]

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

It might be a gnome-panel bug:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

For that, a patch is supplied on the bottom of the page.
I have no clue how to get it in a 9.04 package, anyone?

-- 
Separate X-screen, apps launched from 2nd screen appear on first screen
https://bugs.launchpad.net/bugs/339783
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 110899] Re: workspace-switcher needs to work with dualhead setup

[Vincent Gerris]

Might this be related to the glibc bug?
http://bugzilla.gnome.org/show_bug.cgi?id=580103

A patch is supplied at the bottom.
I do not know how to get it applied to current 9.04 package, anyone?

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

-- 
workspace-switcher needs to work with dualhead setup
https://bugs.launchpad.net/bugs/110899
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 339783] Re: Separate X-screen, apps launched from 2nd screen appear on first screen

[Vincent Gerris]

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

Thanks to midnightflash and keepitsimpleengr, here are some pretty nice
instructions to get it fixed.

Why on Earth is this not available in update manager???

https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380

It worked for me, thank you all for your support!

-- 
Separate X-screen, apps launched from 2nd screen appear on first screen
https://bugs.launchpad.net/bugs/339783
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 290935] Re: dual screen all panels end up on one screen at startup

[Vincent Gerris]

Thanks to midnightflash and keepitsimpleengr, here are some pretty nice
instructions to get it fixed.

Why on Earth is this not available in update manager???

https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380

It worked for me, thank you all for your support!

Sebastien, can you explain how this can be pushed to be available in the update 
manager?
It is a PITA bug :)!

-- 
dual screen all panels end up on one screen at startup
https://bugs.launchpad.net/bugs/290935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 157708] Re: terminal gets wrong DISPLAY with dual head xorg

[Vincent Gerris]

Thanks to midnightflash and keepitsimpleengr, here are some pretty nice
instructions to get it fixed.

Why on Earth is this not available in update manager???

https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380

It worked for me, thank you all for your support!

-- 
terminal gets wrong DISPLAY with dual head xorg
https://bugs.launchpad.net/bugs/157708
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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

[Bug 811566] Re: gnome-control-center crashed with SIGSEGV in g_timer_stop()

[Vincent Gerris]

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

ok, thank you!

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

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

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

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

[Bug 1176509] Re: After update to 13.04 Brasero CD write hangs at normalizing tracks

[Vincent Gerris]

same issue on 13.10 64 bit: haning on normalising, works when disabling
it.

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

Title:
  After update to 13.04 Brasero CD write hangs at normalizing tracks

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

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

[Bug 817778] Re: the Brasero Normalize Plugin should Not be enabled by default

[Vincent Gerris]

Totally agree. Besides not being enabled, it should also work before including 
it.
Currently it still hangs on 13.10 with normalising.

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

Title:
  the Brasero Normalize Plugin should Not be enabled by default

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

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

[Bug 1202159] Re: nautilus assert failure: ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark-details-file))

[Vincent Gerris]

for me also when ejecting. if anyone needs more info please let me know
how to acquire it.

-- 
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 assert failure: ERROR:nautilus-
  bookmark.c:350:nautilus_bookmark_connect_file: assertion failed:
  (!nautilus_file_is_gone (bookmark-details-file))

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 62430] Re: rhythmbox doesn't support .pls and .m3u files

[Vincent Gerris]

yeah seriously, WTF?
It's plain freaking stupid that the default association fires an app which does 
nothing with it?

Here is a workaround (works on 15.04):
 - install vlc
 - on opening choose other and select /usr/bin/vlc
 - save it as default
 - enjoy direct playback when clicking on a link like 
http://yp.shoutcast.com/sbin/tunein-station.pls?id=2157097

Ubuntu, please remove the association, add pls association to vlc and install 
that as a default. 
Thank you

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

Title:
  rhythmbox doesn't support .pls and .m3u files

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

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

[Bug 1512743] [NEW] pls link opened but not played by Rhytmbox

[Vincent Gerris]

Public bug reported:

When opening a pls link like 
http://yp.shoutcast.com/sbin/tunein-station.pls?id=2157097 rhythmbox opens but 
does not play the link.
Since it has been reported over 9 years ago here:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/62430
and no fix is issued, I refiled it with ubuntu-bug.

This happens on 14.04 LTS, 15.04 and probably all others too.
There are some suggestions for a fix in the old report.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: rhythmbox 3.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-32.37-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov  3 16:09:42 2015
InstallationDate: Installed on 2014-06-23 (498 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to vivid on 2015-10-07 (27 days ago)

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


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

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

Title:
  pls link opened but not played by Rhytmbox

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

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

[Bug 62430] Re: rhythmbox doesn't support .pls and .m3u files

[Vincent Gerris]

since no progress seems to happen, I refiled it here with ubuntu-bug (apport)
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1512743

Let's hope someone will pick it up.

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

Title:
  rhythmbox doesn't support .pls and .m3u files

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

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

[Bug 156201] Re: gedit handles opening big files badly

[Vincent Gerris]

I have the exact same problem. From a usability point of view, this editor is 
practically useless for big files and I wonder why it is the default editor?
The bug should either be fixed or another editor should be set as default in my 
opinion.
Vim opens the same file in not even a second and LibreOffice includes weird 
encoding and still is many times faster.

the file I use is 20 Mb, my system has 16 gb of memory and gedit really chokes 
in it.
Takes MINUTES to open it.
Sublime text takes about a second. too.

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

Title:
  gedit handles opening big files badly

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

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

[Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,


This is what I get now when I try the dev package from:

https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-
daemon/3.24.2-0ubuntu0.1

sudo dpkg -i gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb 
[sudo] password for ubuntu: 
(Reading database ... 354908 files and directories currently installed.)
Preparing to unpack gnome-settings-daemon_3.24.2-0ubuntu0.1_amd64.deb ...
Unpacking gnome-settings-daemon (3.24.2-0ubuntu0.1) over (3.24.0-0ubuntu2) ...
dpkg: dependency problems prevent configuration of gnome-settings-daemon:
 gnome-settings-daemon depends on gnome-settings-daemon-schemas (= 
3.24.2-0ubuntu0.1); however:
  Version of gnome-settings-daemon-schemas on system is 3.24.0-0ubuntu2.

dpkg: error processing package gnome-settings-daemon (--install):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
 gnome-settings-daemon

so I downloaded that from:
https://launchpad.net/ubuntu/zesty/amd64/gnome-settings-daemon-schemas/3.24.2-0ubuntu0.1
and installed it.

Then I rebooted but there is not difference in behaviour.

Note that I use Unity, not Gnome.

When I installed these packages:
http://people.canonical.com/~khfeng/lp1683445/
it worked.

Thank you all!

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

Title:
  E6430 brightness control not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

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

[Bug 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption

[Vincent Gerris]

I see the same error but do not seem to get a high load on 18.04 dev.
The package name is gnome-power-statistics 3.25.90-2 (at least the gui).

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

Title:
  upowerd/gnome-power-statistics crash; high CPU, memory consumption

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

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

Re: [Bug 1683445] Re: E6430 brightness control not working

[Vincent Gerris]

Hi,

Unfortunately I'm unable to test, I don't have the laptop anymore.

Kind regards,
Vincent


Den mån 9 juli 2018 14:31Łukasz Zemczak <1683...@bugs.launchpad.net> skrev:

> Hello Vincent, or anyone else affected,
>
> Accepted unity-settings-daemon into bionic-proposed. The package will
> build now and be available at https://launchpad.net/ubuntu/+source
> /unity-settings-daemon/15.04.1+18.04.20180413-0ubuntu1.1
> 
> in a few hours,
> and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: unity-settings-daemon (Ubuntu Bionic)
>Status: New => Fix Committed
>
> ** Tags removed: verification-done
> ** Tags added: verification-needed verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683445
>
> Title:
>   E6430 brightness control not working
>
> Status in GNOME Settings Daemon:
>   Fix Released
> Status in Nouveau Xorg driver:
>   Won't Fix
> Status in OEM Priority Project:
>   Confirmed
> Status in gnome-settings-daemon package in Ubuntu:
>   Fix Released
> Status in unity-settings-daemon package in Ubuntu:
>   Fix Released
> Status in gnome-settings-daemon source package in Xenial:
>   Confirmed
> Status in unity-settings-daemon source package in Xenial:
>   Confirmed
> Status in gnome-settings-daemon source package in Zesty:
>   Fix Released
> Status in unity-settings-daemon source package in Zesty:
>   Won't Fix
> Status in unity-settings-daemon source package in Bionic:
>   Fix Committed
>
> Bug description:
>   Impact
>   --
>   It looks like GNOME's brightness control simply used the first backlight
> device it saw instead of one currently in use. This meant that the
> brightness control would not work on some computers with multiple GPUs.
>
>   Test Case
>   -
>   From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
>   Restart.
>   Does the brightness control now work correctly?
>
>   Regression Potential
>   
>   This looks like a minimal fix for this issue. It was accepted as part of
> gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be
> upgrading to.
>
>   Original Bug Report
>   ---
>   The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
> Source Nouveau driver shows the brightness slider moving but does not
> affect the brightness.
>
>   When using the kernel boot option acpi_backlight=vendor , the
>   brightness control works.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: linux-image-4.10.0-19-generic 4.10.0-19.21
>   ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
>   Uname: Linux 4.10.0-19-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu 2081 F pulseaudio
>   CurrentDesktop: Unity:Unity7
>   Date: Mon Apr 17 20:00:56 2017
>   HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
>   InstallationDate: Installed on 2017-04-10 (7 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
>   MachineType: Dell Inc. Latitude E6430
>   ProcFB:
>0 nouveaufb
>1 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed
> root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash
> acpi_backlight=vendor vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-19-generic N/A
>linux-backports-modules-4.10.0-19-generic  N/A
>linux-firmware 1.164
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/18/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A18
>   dmi.board.name: 0H3MT5
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> 

Re: [Bug 156201] Re: gedit handles opening big files badly

[Vincent Gerris]

Nano is not a gui desktop editor. Besides that vim is superior to nano in
my opinion. A viable alternative would be an open source editor like Atom,
but it can be useful to have a lightweight simple editor that doesn't blow
up with a big file and is installed by default.

On Wed, Jan 23, 2019, 21:45 madbiologist <156...@bugs.launchpad.net
wrote:

> This needs to be fixed.  In the meantime, try using nano.  Unfortunately
> nano doesn't have syntax highlighting.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/156201
>
> Title:
>   gedit handles opening big files badly
>
> Status in gedit:
>   Confirmed
> Status in gedit package in Ubuntu:
>   Triaged
>
> Bug description:
>   Binary package hint: gedit
>
>   Opening big text files (400 MB, 750 MB) in gedit is bad
>   - from a usability standpoint
> -> There's no progress bar or cancel button for the action, and the
> load takes a long time.
>   - from a system standpoint:
> -> In earlier versions, gedit would take so much memory until the
> system swapped all other applications to disk, and the system became
> unusable.
> -> Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but
> the message "failed to allocate  bytes" in the console.
>
>
>
>   Original description:
>   I just opened a 400 MB text file (mbox mail file) in gedit, and it my
> system has now been unresponsive for minutes. Other editors can open large
> files without a problem. Also, there's no progress bar or cancel button
> that would make it easy to see how long gedit is loading the file or to
> cancel the load.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions
>

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

Title:
  gedit handles opening big files badly

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

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

[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

So a valid workaround for me, perhaps for others.
It's nice to see other workarounds too, I hope this bug will be fixed in a way 
that this works without any application/terminal settings or hacks, so with 
proprietary driver and fractional scaling.
I don't want to change font size, multiple settings across apps and such, just 
have a single point to change that works, just like in other major OSes :)

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

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

[Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

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

Title:
  Fractional scaling applies to both monitors when you only want it on
  one

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

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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, this machine has not been much customised. I only switched display manager 
because the supplied one did not work. I cannot reinstall and lose data.
Display link does not work on at least 2 of my systems with kernel 5.13 and 
they reopened a bug because I reported it - those drivers are always behind and 
rather unstable in my experience, especially with nouveau currently.

I hope devs can come up with a better answer because I bet a lot of folks will 
run into this issue.
I uninstalled caffeine, removed plugins from /usr/share and the problem remains.
I would say I am rather handy with Linux, that is why I run dev builds 
sometimes and report issues.
If I want buggy drivers and no support I can just install windows, man even 
macOS runs better on both machines.
Please notify the gdm3 devs and gnome-extensions ones, because stuff changed 
there.
You can also close the bug, but I am not gonna waste my time on finding the 
issue anymore then.
Isn´t the whole point of open source software that users make it better :)?

Also, I the time of reporting was right after the update, so it can´t be too 
hard to find.
This issue does not occur on another machine with a recent install of 20.04 and 
having that updated. That said, this machine certainly does not go further back 
than 18.04, I think actually 20.04 too.

How about we try to find the cause? You have not answered the question about 
where to find this plugins that are in the bug report, like xcaffeine.
thanks

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

from the newly installed system with 20.04, warnings came for 
/var/lib/gdm3.config and .local not being empty.
root@ubuntu-inspiron-5482:/var/lib/gdm3# ls -lrta
total 32
drwxr-xr-x   3 root root 4096 feb  5 12:33 .config
drwx--   3 gdm  gdm  4096 feb  5 12:34 .nv
drwx--   4 gdm  gdm  4096 feb  5 12:35 .local
drwx--   6 gdm  gdm  4096 feb  5 12:35 .cache
drwxr-xr-x 101 root root 4096 feb  5 12:37 ..
-rw-r--r--   1 gdm  gdm   feb 13 23:26 greeter-dconf-defaults
drwx--x--x   6 gdm  gdm  4096 feb 13 23:26 .
is what that looks like on the broken system.

On the one with warning, it shows 755 instead of 700 permissions.
There is also no .nv dir.
I will wipe it out, reinstall and see what happens.

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

confirmed that after reinstalling fprintd, the issue returns.
First of all, it creates a delay until the login screen loads.
then when the login screen loads, no user is visible to be clicked, also not 
after the 25000 ms timeout of the fprintd daemon.

So it seems the cause of the issue is the login process in gdm3 is not
handling this properly - ideally the user would get a message like -
fprintd error: timeout xxx etc and the login would skip fingerprint
related stuff and go to normal login.

This is currently broken when the command fprintd-list times out like:
gnome-shell[2622]: Failed to connect to Fprint service: Error calling 
StartServiceByName for net.reactivated.Fprint: Timeout was reached

current work around:
drop to safe login and type:
apt remove fprintd
reboot

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

I tracked down the cause, it has to do with sssd and how gdm3 handles it.
Similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1534873

First I removed kerberos auth, which did not seem to have had an effect.
Then I saw that fprintd was showing errors and fprintd-list was throwing the 
same error as in the logs.

I removed it and after that it worked.
So it seems like a bug in sssd related to fingerprint auth, when that is not 
working properly.

Regarding evdi - as you wrote, can be addressed separately. As I wrote ,
it does NOT work properly for me, not the beta driver, not even on 5.13
with beta driver. I just installed 5.12 kernel and latest release driver
because the beta does not work properly on my system - I use a D6000
Dell dock.

Regarding this bug - I will try to see if I can get frintd to work. I
still have Ubuntu sessions showing that do not work, not sure where they
came from, this is even after I purged gnome gnome-shell and gnome-
session. can login now with gdm3 and gnome session.

Is there anything else you need to pursue this ?

** Bug watch added: Red Hat Bugzilla #1534873
   https://bugzilla.redhat.com/show_bug.cgi?id=1534873

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen when fprintd crashes

[Vincent Gerris]

Hi,

I think the most obvious is to have the fprintd bug tracked in the appropriate 
bug, and have this one track login not working.
I looked at the link and do not understand what you need.
There are some files in /var/crash that end in uploaded, I presume they are 
uploaded?

The last one for fprintd is attached here.


** Attachment added: "fprint crash report"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+attachment/5562099/+files/_usr_libexec_fprintd.0.uploaded

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

Title:
  No login screen when fprintd crashes

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


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

[Bug 1960336] Re: No login screen when fprintd is installed

[Vincent Gerris]

hi, it seems it does not start. 
output from terminal:

ubuntu@ubuntu-inspiron-5482:~$ sudo apt install fprintd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  fprintd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/97,4 kB of archives.
After this operation, 680 kB of additional disk space will be used.
Selecting previously unselected package fprintd.
(Reading database ... 424549 files and directories currently installed.)
Preparing to unpack .../fprintd_1.94.1-1_amd64.deb ...
Unpacking fprintd (1.94.1-1) ...
Setting up fprintd (1.94.1-1) ...
fprintd.service is a disabled or a static unit not running, not starting it.
Processing triggers for dbus (1.12.20-2ubuntu2) ...
Processing triggers for man-db (2.10.1-1) ...
ubuntu@ubuntu-inspiron-5482:~$ systemctl restart fprintd.service 
Job for fprintd.service failed because a fatal signal was delivered to the 
control process.
See "systemctl status fprintd.service" and "journalctl -xeu fprintd.service" 
for details.
ubuntu@ubuntu-inspiron-5482:~$ systemctl status fprintd.service
× fprintd.service - Fingerprint Authentication Daemon
 Loaded: loaded (/lib/systemd/system/fprintd.service; static)
 Active: failed (Result: signal) since Thu 2022-02-17 00:20:25 CET; 15s ago
   Docs: man:fprintd(1)
Process: 33083 ExecStart=/usr/libexec/fprintd (code=killed, signal=SEGV)
   Main PID: 33083 (code=killed, signal=SEGV)
CPU: 531ms

feb 17 00:20:23 ubuntu-inspiron-5482 systemd[1]: Starting Fingerprint 
Authentication Daemon...
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=killed, status=11/SEGV
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'signal'.
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint 
Authentication Daemon.
ubuntu@ubuntu-inspiron-5482:~$ journalctl -xeu fprintd.service
░░ 
░░ The job identifier is 2235.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process 
exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit fprintd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 11.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with 
result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit fprintd.service has entered the 'failed' state with result 'signal'.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint 
Authentication Daemon.
░░ Subject: A start job for unit fprintd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit fprintd.service has finished with a failure.
░░ 
░░ The job identifier is 2235 and the job result is failed.

there is also a bug here :
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633 that may
be related?

Thanks for the heads up, hope these things will be solved.

Still seems like a good idea in the context of this bug to handle
fprintd not working gracefully?

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

Title:
  No login screen when fprintd is installed and not starting

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


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

[Bug 1960336] Re: No login screen when fprintd is installed and not starting

[Vincent Gerris]

** Summary changed:

- No login screen when fprintd is installed
+ No login screen when fprintd is installed and not starting

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

Title:
  No login screen when fprintd is installed and not starting

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


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

[Bug 1960336] [NEW] no login screen on Wayland with gdm3 after recent update

[Vincent Gerris]

Public bug reported:

After a recent update, when using gdm3 as login manager, there is no account 
visible and it is not possible to login. 
When switching to lightdm I can login but sleep is broken and some 
notifications do not work.
Running the latest 22.04 dev branch with Wayland and Nvidia driver.
Had to select kernel 5.12 to have display link working.
This issue occurs with and without external displays attached.
A recent attempt to switch back to gdm3 gave me just a black screen.

I tried to reinstall gdm3 to no avail.
This seems like a quite serious issue, hence this report for the dev version.

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

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

Title:
  no login screen on Wayland with gdm3 after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

ran apport and added files, thank you.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+attachment/5559964/+files/prevboot.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

lspci output

** Attachment added: "lspci -k output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+attachment/5559965/+files/lspci.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] ProcCpuinfoMinimal.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559960/+files/ProcCpuinfoMinimal.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] ProcEnviron.txt

[Vincent Gerris]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559961/+files/ProcEnviron.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  After a recent update, when using gdm3 as login manager, there is no account 
visible and it is not possible to login. 
  When switching to lightdm I can login but sleep is broken and some 
notifications do not work.
  Running the latest 22.04 dev branch with Wayland and Nvidia driver.
  Had to select kernel 5.12 to have display link working.
  This issue occurs with and without external displays attached.
  A recent attempt to switch back to gdm3 gave me just a black screen.
  
  I tried to reinstall gdm3 to no avail.
  This seems like a quite serious issue, hence this report for the dev version.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu76
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: lightdm
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2019-12-17 (784 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ NonfreeKernelModules: nvidia_modeset wl nvidia
+ Package: gnome-shell 41.3-1ubuntu1
+ PackageArchitecture: amd64
+ RelatedPackageVersions: mutter-common 41.3-1ubuntu1
+ Tags: third-party-packages jammy
+ Uname: Linux 5.12.19-051219-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559958/+files/Dependencies.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] GsettingsChanges.txt

[Vincent Gerris]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559959/+files/GsettingsChanges.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] ShellJournal.txt

[Vincent Gerris]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559962/+files/ShellJournal.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] monitors.xml.txt

[Vincent Gerris]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1960336/+attachment/5559963/+files/monitors.xml.txt

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, I did :
ubuntu@ubuntu-inspiron-5482:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  gdm3   41.3-1ubuntu2 amd64GNOME Display Manager

The extensions do not show up in the extensions app, I cannot find a trace 
anywhere.
A screenshot is attached from the app ( that in fact does not seem to follow 
the theme :) ).

Also no extensions show on extensions.gnome.org/local.
Thank you again for the quick reply!

** Attachment added: "gnome extensions screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+attachment/5560236/+files/Screenshot%20from%202022-02-10%2009-18-38.png

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

hi, I tried, same problem.

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

Title:
  No login screen after recent update

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


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

[Bug 1960336] Re: No login screen after recent update

[Vincent Gerris]

Hi Daniel,

Where can I find these extensions?
They are not in apt search, .local/share/gnome-shell/extensions or in 
extensions app.

I did an apt get update and installed the new gdm3 version you mention.
Then sudo dpkg-reconfigure gdm3 and now it actually showed me the choice 
between lightdm and gdm3 ( did not do that on previous version).

Unfortunately, the result is the same.
I get a black screen. If I try other ttys, some show a flashing cursor, but I 
can´t do anything.
The off button responds so the system is not hanging.

Also did a reinstall of gnome-shell package, no success.
So a photo would just be a black screen :).

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

Title:
  No login screen after recent update

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


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