Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

[Alberts Muktupāvels]

Hi,

Look at this - https://wiki.gnome.org/Initiatives/SystemdUser and related
merge requests. As far as I understand, current behaviour is expected one
when a session is started/managed by systemd --user. You already confirmed
that with --builtin / --systemd test.

And this confirms above:
https://github.com/systemd/systemd/issues/12399

> services forked off "systemd --user" belong to no session. or if you so
> will are shared by them all.


On Tue, Jul 18, 2023 at 12:14 PM Nikolaus Rath  wrote:

> Hi Alberts,
>
> One example of a real problem is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040917.
>
>
> https://manpages.ubuntu.com/manpages/impish/man5/org.freedesktop.login1.5.html
> also seems pretty clear to me:
>
> *GetSessionByPID()* and *GetUserByPID()* get the session/user object the 
> specified PID belongs to if there is any.
>
>
> In other words, if this DBus request fails then the specified PID is not
> part of any logind session.
>
> Does that help?
>
> Best,
> -Nikolaus
>
>
>
> On Mon, 17 Jul 2023, at 21:48, Alberts Muktupāvels wrote:
>
> Hi,
>
> I just logged into the Ubuntu GNOME x11 session. The XDG_SESSION_ID
> environment variable is not set there either. Also GetSessionByPID for
> gnome-shell returns the same error at least for me.
>
> Sorry but you will have to link to relevant documentation if you think
> that there are real problems. Also I don't think there is much I can do
> from gnome-flashback to change anything...
>
>
> On Mon, Jul 17, 2023 at 11:15 PM Nikolaus Rath  wrote:
>
>
> Hi Alberts,
>
> I believe that way you can get *a session id*. However, the fact that the
> dbus query returns an error means that the various X11 processes (those
> started by gnome-session as well as those started by the user) are actually
> not part of that session (or any session, for that matter).
>
> It's not a matter of determining the session id (even though I first
> thought that), the problem is that the entire gnome flashback session is
> not associated with a logind session.
>
> Best,
> -Nikolaus
>
> On Mon, 17 Jul 2023, at 21:02, Alberts Muktupāvels wrote:
>
> Can not you get session id from logind manager using
> /org/freedesktop/login1/session/auto path?
>
> dbus-send --system --print-reply --dest=org.freedesktop.login1
> /org/freedesktop/login1/session/auto org.freedesktop.DBus.Properties.Get
> string:org.freedesktop.login1.Session string:Id
>
> On Sun, Jul 16, 2023 at 2:27 PM Nikolaus Rath  wrote:
>
> retitle 1040920 "Gnome flashback breaks out of logind session"
> thanks
>
> Upon closer examination, the problem is not that GNome flashback unsets
> XDG_SESSION_ID, but that it breaks out of the active logind session (so
> unsetting the variable is, in some way, correct).
>
> In other desktop environments (vanilla i3 as well as regular Gnome), the
> desktop environment is correctly associated with a logind session:
>
> nikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> method return time=1689506142.664977 sender=:1.6 -> destination=:1.1126
> serial=2461 reply_serial=2
>object path "/org/freedesktop/login1/session/_342"
>
> When running Gnome Flashback, however:
>
> ikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> Error org.freedesktop.login1.NoSessionForPID: PID 858156 does not belong
> to any known session
>
>
> I don't think this is intentional.. or is it?
>
> Best,
> -Nikolaus
>
>
>
> --
> Alberts Muktupāvels
>
>
>
>
> --
> Alberts Muktupāvels
>
>
>

-- 
Alberts Muktupāvels

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

[Alberts Muktupāvels]

Hi,

I just logged into the Ubuntu GNOME x11 session. The XDG_SESSION_ID
environment variable is not set there either. Also GetSessionByPID for
gnome-shell returns the same error at least for me.

Sorry but you will have to link to relevant documentation if you think that
there are real problems. Also I don't think there is much I can do from
gnome-flashback to change anything...


On Mon, Jul 17, 2023 at 11:15 PM Nikolaus Rath  wrote:

> Hi Alberts,
>
> I believe that way you can get *a session id*. However, the fact that the
> dbus query returns an error means that the various X11 processes (those
> started by gnome-session as well as those started by the user) are actually
> not part of that session (or any session, for that matter).
>
> It's not a matter of determining the session id (even though I first
> thought that), the problem is that the entire gnome flashback session is
> not associated with a logind session.
>
> Best,
> -Nikolaus
>
> On Mon, 17 Jul 2023, at 21:02, Alberts Muktupāvels wrote:
>
> Can not you get session id from logind manager using
> /org/freedesktop/login1/session/auto path?
>
> dbus-send --system --print-reply --dest=org.freedesktop.login1
> /org/freedesktop/login1/session/auto org.freedesktop.DBus.Properties.Get
> string:org.freedesktop.login1.Session string:Id
>
> On Sun, Jul 16, 2023 at 2:27 PM Nikolaus Rath  wrote:
>
> retitle 1040920 "Gnome flashback breaks out of logind session"
> thanks
>
> Upon closer examination, the problem is not that GNome flashback unsets
> XDG_SESSION_ID, but that it breaks out of the active logind session (so
> unsetting the variable is, in some way, correct).
>
> In other desktop environments (vanilla i3 as well as regular Gnome), the
> desktop environment is correctly associated with a logind session:
>
> nikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> method return time=1689506142.664977 sender=:1.6 -> destination=:1.1126
> serial=2461 reply_serial=2
>object path "/org/freedesktop/login1/session/_342"
>
> When running Gnome Flashback, however:
>
> ikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> Error org.freedesktop.login1.NoSessionForPID: PID 858156 does not belong
> to any known session
>
>
> I don't think this is intentional.. or is it?
>
> Best,
> -Nikolaus
>
>
>
> --
> Alberts Muktupāvels
>
>
>

-- 
Alberts Muktupāvels

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

[Alberts Muktupāvels]

Can not you get session id from logind manager using
/org/freedesktop/login1/session/auto path?

dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1/session/auto org.freedesktop.DBus.Properties.Get
string:org.freedesktop.login1.Session string:Id

On Sun, Jul 16, 2023 at 2:27 PM Nikolaus Rath  wrote:

> retitle 1040920 "Gnome flashback breaks out of logind session"
> thanks
>
> Upon closer examination, the problem is not that GNome flashback unsets
> XDG_SESSION_ID, but that it breaks out of the active logind session (so
> unsetting the variable is, in some way, correct).
>
> In other desktop environments (vanilla i3 as well as regular Gnome), the
> desktop environment is correctly associated with a logind session:
>
> nikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> method return time=1689506142.664977 sender=:1.6 -> destination=:1.1126
> serial=2461 reply_serial=2
>object path "/org/freedesktop/login1/session/_342"
>
> When running Gnome Flashback, however:
>
> ikratio@vostro ~> dbus-send --system --print-reply
> --dest=org.freedesktop.login1 /org/freedesktop/login1
> org.freedesktop.login1.Manager.GetSessionByPID uint32:$fish_pid
> Error org.freedesktop.login1.NoSessionForPID: PID 858156 does not belong
> to any known session
>
>
> I don't think this is intentional.. or is it?
>
> Best,
> -Nikolaus
>
>

-- 
Alberts Muktupāvels

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

[Alberts Muktupāvels]

Maybe... Why do you need that variable?

On Wed, Jul 12, 2023 at 3:12 PM Nikolaus Rath  wrote:

> Could this be an unintended side effect of
> https://salsa.debian.org/gnome-team/gnome-session/-/commit/6f5c3c80be8f92ababd8d6201c5c58e732b47f54
> ?
>
>

-- 
Alberts Muktupāvels

Bug#1040920: gnome-flashback: Gnome flashback unsets XDG_SESSION_ID

[Alberts Muktupāvels]

GNOME Flashback does not do that!

That variable is blacklisted by gnome-session:
https://gitlab.gnome.org/GNOME/gnome-session/-/blob/main/gnome-session/gsm-util.c#L38

On Wed, Jul 12, 2023 at 2:51 PM Nikolaus Rath  wrote:

> Package: gnome-flashback
> Version: 3.46.0-1
> Severity: normal
>
>
> When starting a Gnome Flashback session, the XDG_SESSION_ID environment
> variable is not set. This results on applications that rely on logind to
> not behave properly.
>
> Debugging this more closely, I found that XDG_SESSION_ID is still
> set in ~/.xsession, but seemingly disappears somewhere in this call:
>
> exec gnome-session --systemd --session=gnome-flashback
> --disable-acceleration-check
>
> -- System Information:
> Debian Release: 12.0
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages gnome-flashback depends on:
> ii  gnome-flashback-common 3.46.0-1
> ii  libasound2 1.2.8-1+b1
> ii  libatk1.0-02.46.0-5
> ii  libc6  2.36-9
> ii  libcairo2  1.16.0-7
> ii  libcanberra-gtk3-0 0.30-10
> ii  libcanberra0   0.30-10
> ii  libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1
> ii  libgdm143.0-3
> ii  libglib2.0-0   2.74.6-2
> ii  libgnome-bluetooth-3.0-13  42.5-3
> ii  libgnome-desktop-3-20  43.2-2
> ii  libgnome-panel03.46.0-1+b1
> ii  libgtk-3-0 3.24.37-2
> ii  libibus-1.0-5  1.5.27-5
> ii  libpam0g   1.5.2-6
> ii  libpango-1.0-0 1.50.12+ds-1
> ii  libpangocairo-1.0-01.50.12+ds-1
> ii  libpolkit-agent-1-0122-3
> ii  libpolkit-gobject-1-0  122-3
> ii  libpulse-mainloop-glib016.1+dfsg1-2+b1
> ii  libpulse0  16.1+dfsg1-2+b1
> ii  libsystemd0252.6-1
> ii  libx11-6   2:1.8.4-2+deb12u1
> ii  libx11-xcb12:1.8.4-2+deb12u1
> ii  libxcb-randr0  1.15-1
> ii  libxext6   2:1.3.4-1+b1
> ii  libxfixes3 1:6.0.0-2
> ii  libxi6 2:1.8-1+b1
> ii  libxkbfile11:1.1.0-1
> ii  libxrandr2 2:1.5.2-2+b1
> ii  libxxf86vm11:1.1.4-1+b2
> ii  nautilus   43.2-1
>
> Versions of packages gnome-flashback recommends:
> ii  dbus   1.14.6-1
> ii  gnome-settings-daemon  43.0-4
> ii  libpam-gnome-keyring   42.1-1+b2
>
> Versions of packages gnome-flashback suggests:
> pn  gnome-power-manager  
>
> -- no debconf information
>
>

-- 
Alberts Muktupāvels

Bug#744755:

[Alberts Muktupāvels]

Can anyone confirm if this still happens with gnome-panel 3.38 or newer?

Bug#742807:

[Alberts Muktupāvels]

Can anyone confirm if this still happens with gnome-panel 3.38 or newer?

Bug#989139: gnome-flashback segfaults on login

[Alberts Muktupāvels]

Can you get stacktrace?

Maybe this helps?:
https://gitlab.gnome.org/GNOME/gnome-flashback/-/commit/7676c3a243aad62150b1108dd126132b5f91f8d7


On Wed, May 26, 2021 at 6:03 PM Grzegorz Szymaszek 
wrote:

> Package: gnome-session-flashback
> Version: 3.38.0-1
>
> When I login to a GNOME Flashback session from GDM3, it fails with a
> “something has gone wrong” screen. When I click “Log Out”, I am able to
> see the GNOME Flashback desktop, but I get logged out anyway. Relevant
> dmesg fragment:
>
> gnome-flashback[…]: segfault at fff0 ip 00486734 sp bf9fd99c error
> 5 in gnome-flashback[47e000+9]
> Code: 00 5b 5e c3 66 90 83 c4 04 31 c0 5b 5e c3 8d b4 26 00 00 00 00
> 90 e8 84 fb ff ff 05 6f 93 0f 00 8b 54 24 04 8b 80 38 18 00 00 <8b> 04 02
> c3 8d b4 26 00 00 00 00 90 e8 64 fb ff ff 05 4f 93 0f 00
>
> This is an old Intel Atom‐based netbook with Debian bullseye. All other
> GNOME sessions—the default Wayland session, the alternative X11 session,
> as well as the X11 “Classic” session—work correctly.
>


-- 
Alberts Muktupāvels

Bug#961332: Fwd: Bug#961332: gnome-flashback: System indicators (volume, bluetooth, ...) do not appear

[Alberts Muktupāvels]

On Fri, Jun 5, 2020 at 2:36 PM Timothy Allen  wrote:

> On 5/6/20 21:02, Alberts Muktupāvels wrote:
> > I do know that gnome-flashback is used with i3, but it is not really
> > supported. Doesn't i3 have its own indicators or something like that?
>
> i3 has a "bar" which is a bit like GNOME's mini-commander applet - it
> displays output of a command (that by default shows things like battery
> charge and system load), but it doesn't have any interactive bits other
> than a system tray. In particular, it doesn't include a volume control,
> so I really appreciated the one from gnome-flashback.
>

https://github.com/muktupavels/sound-applet

Quick version based on code from gnome-flashback before it was converted to
System Indicators applet.

-- 
Alberts Muktupāvels

Bug#961332: Fwd: Bug#961332: gnome-flashback: System indicators (volume, bluetooth, ...) do not appear

[Alberts Muktupāvels]

On Sun, May 24, 2020 at 5:33 PM Timothy Allen  wrote:

> I feel like this change could have been announced a more loudly, but
> thank you for explaining - I've switched from i3's built-in status-bar
> to gnome-panel, and now I've got my volume slider back.
>

I do know that gnome-flashback is used with i3, but it is not really
supported. Doesn't i3 have its own indicators or something like that?

If someone really wants the same indicators that were provided by
gnome-flashback then it should not be hard to create them as separate
applications with one exception - input sources. It would need to use the
D-Bus interface provided by gnome-flashback.

How do you install / configure your session? Do you use something like
Regolith? If so I would suggest to open issue to discuss this problem with
project maintainers.

-- 
Alberts Muktupāvels

Bug#961332: gnome-flashback: System indicators (volume, bluetooth, ...) do not appear

[Alberts Muktupāvels]

On Sat, May 23, 2020 at 1:33 PM Timothy Allen  wrote:

> Recently (and I'm afraid I don't have an exact date, although
> I'm pretty user it was the 3.34 → 3.36 upgrade) gnome-flashback's
> standard system indicators (the volume control, Bluetooth,
> the battery charging indicator, etc.) have stopped appearing in the
> notification area. Other indicators (VLC, Network Manager) appear
> just fine, but the system indicators are missing. This is still
> true after logging out and back in, and after rebooting.
>

Mentioned things where turned into gnome-panel applet - System Indicators.

Full disclosure: I normally use gnome-flashback with the i3
> window manager rather than Metacity, according to the instructions in
> https://zork.net/~st/jottings/gnome-i3.html - although the only
> difference between gnome-flashback's stock
> `gnome-flashback-metacity.session`
> file and mine is that I've swapped `metacity` for
> `i3` and removed `gnome-panel`.


There is nothing wrong with session files. GNOME Flashback simply no longer
provides system tray icons.

Nevertheless, the missing system
> indicators are still missing if I log into a standard "GNOME Flashback
> (Metacity)" session rather than my custom one.
>

Existing users needs to add new applet to panel.

-- 
Alberts Muktupāvels

Bug#742888:

[Alberts Muktupāvels]

Is this still problem or can be closed?

-- 
Alberts Muktupāvels

Bug#645734:

[Alberts Muktupāvels]

Are you still using gnome-panel? Is this still valid bug?

-- 
Alberts Muktupāvels

Bug#383952: closed by Alberts Muktupāvels ()

[Alberts Muktupāvels]

That bug has not been touched for 8 years. I just checked if new project
dialog still does not have maximize button and if that is metacity bug. If
that is still problem to you then please reassign back to kdevelop.

On Fri, Nov 23, 2018 at 4:45 PM Olaf van der Spek 
wrote:

> Op vr 23 nov. 2018 om 15:30 schreef Debian Bug Tracking System
> :
> > 0x26 == 0b00100110 - Enabled functions are close, move and resize.
> Maximize bit is not set so metacity correctly does not show maximize
> button. Closing.
>
> Closing doesn't solve this does it?
> Shouldn't it be reassigned to another package?
>
>

-- 
Alberts Muktupāvels

Bug#870700: [gnome-flashback] gnome-session-flashback segfaults after login

[Alberts Muktupāvels]

Hi,

can you look at these bug reports?:
- https://bugzilla.gnome.org/show_bug.cgi?id=785227
- https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1706572

Might be same bug, if not could you try to get stacktrace?


On Fri, Aug 4, 2017 at 1:37 PM, anne.li...@free.fr <anne.li...@free.fr>
wrote:

> Package: gnome-flashback
> Version: 3.22.0-3
> Severity: critical
>
> --- Please enter the report below this line. ---
>
> Dear Maintainer,
>
> problem with gnome-flashback gnome-flashback-common gnome-session-flashback
>
> After entering my login, nothing happens.
>
> I find the following log line:
>
> in log kernel
> Aug  4 09:15:26 pc-00105 kernel: [   33.669264] gnome-flashback[991]:
> segfault at 40 ip 557131fc4ea0 sp 7ffeecaff5c8 error 4 in
> gnome-flashback[557131f94000+9f000]
>
> in log messages
> Aug  4 09:15:25 pc-00105 gnome-session[783]: gnome-session-binary[783]:
> WARNING: Application 'gnome-flashback.desktop' killed by signal 11
> Aug  4 09:15:25 pc-00105 kernel: [   33.597220] gnome-flashback[924]:
> segfault at 40 ip 562307475ea0 sp 7ffd0eea2538 error 4 in
> gnome-flashback[562307445000+9f000]
> Aug  4 09:15:26 pc-00105 kernel: [   33.669264] gnome-flashback[991]:
> segfault at 40 ip 557131fc4ea0 sp 7ffeecaff5c8 error 4 in
> gnome-flashback[557131f94000+9f000]
> Aug  4 09:15:26 pc-00105 gnome-session[783]: gnome-session-binary[783]:
> WARNING: Application 'gnome-flashback.desktop' killed by signal 11
> Aug  4 09:15:26 pc-00105 gnome-session[783]: gnome-session-binary[783]:
> WARNING: App 'gnome-flashback.desktop' respawning too quickly
> Aug  4 09:15:26 pc-00105 gnome-session[783]: Unable to init server: Could
> not connect: Connection refused
>
> Any idea how to fix that?
>
> Anne
>
>
> --- System information. ---
> Architecture: Kernel:   Linux 4.9.0-3-amd64
>
> Debian Release: 9.1
>   500 stable  www.deb-multimedia.org   500 stable
> security.debian.org   500 stable  ftp.fr.debian.org
> --- Package information. ---
> Depends   (Version) | Installed
> ===-+-
> gnome-flashback-common (= 3.22.0-3) | 3.22.0-3
> libatk1.0-0 (>= 1.12.4) | 2.22.0-1
> libc6 (>= 2.14) | 2.24-11+deb9u1
> libcairo2   (>= 1.10.0) | 1.14.8-1
> libcanberra-gtk3-0(>= 0.25) | 0.30-3
> libgdk-pixbuf2.0-0  (>= 2.22.0) | 2.36.5-2
> libglib2.0-0(>= 2.44.0) | 2.50.3-2
> libgnome-bluetooth13(>= 3.12.0) | 3.20.1-1
> libgnome-desktop-3-12  (>= 3.17.92) | 3.22.2-1
> libgtk-3-0 (>= 3.19.12) | 3.22.11-1
> libibus-1.0-5(>= 1.5.2) | 1.5.14-3
> libpango-1.0-0  (>= 1.14.0) | 1.40.5-1
> libpangocairo-1.0-0 (>= 1.14.0) | 1.40.5-1
> libpolkit-agent-1-0   (>= 0.99) | 0.105-18
> libpolkit-gobject-1-0 (>= 0.99) | 0.105-18
> libpulse-mainloop-glib0 (>= 0.99.1) | 10.0-1+deb9u1
> libpulse0   (>= 0.99.1) | 10.0-1+deb9u1
> libupower-glib3 (>= 0.99.0) | 0.99.4-4+b1
> libx11-6| 2:1.6.4-3
> libx11-xcb1 | 2:1.6.4-3
> libxcb-randr0  (>= 1.1) | 1.12-1
> libxext6| 2:1.3.3-1+b2
> libxi6  (>= 2:1.2.99.4) | 2:1.7.9-1
> libxkbfile1 | 1:1.0.9-2
> libxrandr2 (>= 2:1.5.0) | 2:1.5.1-1
>
>
> Recommends  (Version) | Installed
> =====-+-
> dbus  | 1.10.18-1
> gnome-settings-daemon (>= 3.15.4) | 3.22.2-2+deb9u2
>
>
> Suggests (Version) | Installed
> ==-+-===
> gnome-power-manager| 3.22.2-2
>
>


-- 
Alberts Muktupāvels

Bug#853205: (no subject)

[Alberts Muktupāvels]

On Tue, 7 Feb 2017 10:58:33 +0100 Ksamak  wrote:
> On Mon, Jan 30, 2017 at 03:35:21PM +, Hugh Morris wrote:
> > Subject: compiz: Window Decoration Problem
> > Package: compiz
> > Version: 1:0.9.13.0+16.10.20160818.2-4
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I, too, was surprised and pleased to see Compiz back in the Debian
repositories.
> > I have installed it on a Debian Unstable installation with MATE on a
fairly old
> > AMD64 desktop system with a nvidia GeForce 6200 video card with the
nvidia driver.
> >
> > The problem I am having is with the window decorations. Decorations do
appear,
> > but they are not the normal ones for the theme I am using (BlackMATE).
> > It's the same with any other theme.
> >
> > The error messages I am getting are:
> > compiz (decor) - Warn: failed to bind pixmap to texture
> > compiz (decor) - Warn: No default decoration found, placement will not
be correct
> >
> > gtk-window-decorator is running.
> >
> > I used Compiz for years in the past, so I am quite familiar with it and
CCSM.
> >
> > Can you give me a clue to help me fix this? I would be very grateful.
> >
> I think it's got something to do with the metacity themes (build flag
> USE_METACITY), which are dependent on a old version of gnome-desktop,
> which has not been updated or ported since mate.

It does not depend on old version of gnome-desktop...

> the cmake of compiz says so:
> No package 'gnome-window-settings-2.0' found
> No package 'gnome-desktop-2.0' found
>
> and in the summary:
> "metacity theme support : No"

Metacity support was disabled, because gtk-window-decorator does not
support libmetacity 3.22 in current compiz version available in debian:
https://anonscm.debian.org/cgit/compiz/compiz.git/commit/?h=1_0.9.13.0%2b16.10.20160818.2-5=c36fa3cf661eb363f75ca54fe642bad0f0377f40

> I guess it could be updated/ported like every other mate package,
> although it's not confirmed it would fix the problem.

There is no need to port anything, compiz should be updated to newer
version.

> thanks for your interest!
> --
> Ksamak
> Free software hacktivist

Bug#864196: gnome-session-flashback: Nautilus' header-bar user interface reqires access to gnome-shell top panel to change preferences.

[Alberts Muktupāvels]

CSD windows under GNOME Flashback should have appmenu button... Is that
missing for you?

- gsettings get org.gnome.gnome-flashback workarounds
- gsettings get org.gnome.gnome-flashback.workarounds fix-app-menu
- gsettings get org.gnome.gnome-flashback.workarounds fix-button-layout

All should return true.


On Mon, Jun 5, 2017 at 9:25 AM, Walter Irion <wir...@yahoo.com> wrote:

> Package: gnome-session-flashback
> Version: 3.22.0-3
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
> I tried to change nautilus preferences from a flashback session but
> couldn't
> because the menu with the "preferences" option exists only in the
> GNOME-Shell
> top panel.
>
> The only workaround I could find was to log out of the flashback session,
> start a GNOME-Shell session and change my nautilus preferences from there.
>
> Actually, I expected that the flashback session would do away with this
> -- in my opinion -- ill-conceived header-bar user interface.
>
> I do see the neccessity to shield novice users from un-needed complexity,
> but as soon as they start working with office applications they will
> have to learn using traditional drop-down menus anyway. So, in my opinion,
> the header-bar interface is throwing out the baby with the bath water.
>
> I know you folks put a hell of an effort into GNOME and I wish to thank
> all of you for that, even the header-bar programmers. But please try to
> see the point that sometimes tradition has its merits.
>
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64
>  (x86_64)
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-session-flashback depends on:
> ii  gnome-flashback3.22.0-3
> ii  gnome-panel3.20.1-1+b2
> ii  gnome-session-bin  3.22.3-1
> ii  gnome-session-common   3.22.3-1
> ii  gnome-settings-daemon  3.22.2-2
> ii  metacity   1:3.22.1-1
> ii  nautilus   3.22.3-1
>
> Versions of packages gnome-session-flashback recommends:
> ii  gnome-power-manager  3.22.2-2
> ii  gnome-screensaver    3.6.1-7+b2
>
> Versions of packages gnome-session-flashback suggests:
> ii  desktop-base  9.0.2
> ii  gnome-keyring 3.20.0-3
> ii  gnome-user-guide  3.22.0-1
>
> -- no debconf information
>
>


-- 
Alberts Muktupāvels

Bug#804150: gnome-flashback: windows move very slowly

[Alberts Muktupāvels]

Hi,

has something improved with 3.18.4 or 3.20.0 version of metacity?

On Tue, Nov 10, 2015 at 2:21 PM, Joachim Schmidt <jschm...@arcor.de> wrote:

> Hi  Alberts Muktupāvels,
>
> this is not very useful... Please try to provide more info so we can
>> understand what is going on.
>>
> I try to move a window to an other position on screen with left mouse
> button down. The window takes several seconds to reach the new position.
> There are no intermediate mouse positions lost.
> Thats, what I meant with "the window follows very slowly the mouse"
>
>>
>> 1) What video card do you have / video drivers?
>>
> Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300]
>
>> 2) Do you have same problem when you disable compositing manager?:
>> gsettings set org.gnome.metacity compositing-manager false
>>
> yes
>
>> 3) Which version was last that did not have this problem?
>>
> stable Version - jessie I switched a few days ago
>
>> 4) Do you have this problem only with server side decorations
>> (gnome-terminal) and/or also with csd windows (nautilus)?
>>
> no, with terminal, with nautilus, with every window
>
> Joachim
>



-- 
Alberts Muktupāvels

Bug#824656: gnome-flashback: Crash in update_bubble (gf-bubble.c:331)

[Alberts Muktupāvels]

')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-flashback depends on:
> ii  gnome-flashback-common   3.20.0-2
> ii  libatk1.0-0  2.20.0-1
> ii  libc62.22-7
> ii  libcairo21.14.0-2.1+deb8u1
> ii  libcanberra-gtk3-0   0.30-2.1
> ii  libgdk-pixbuf2.0-0   2.34.0-1
> ii  libglib2.0-0 2.48.0-1
> ii  libgnome-bluetooth13 3.18.3-1
> ii  libgnome-desktop-3-123.20.1-1
> ii  libgtk-3-0   3.20.3-2
> ii  libibus-1.0-51.5.9-1
> ii  libpango-1.0-0   1.40.1-1
> ii  libpangocairo-1.0-0  1.40.1-1
> ii  libpolkit-agent-1-0  0.105-15
> ii  libpolkit-gobject-1-00.105-15
> ii  libpulse-mainloop-glib0  5.0-13
> ii  libpulse05.0-13
> ii  libupower-glib3  0.99.1-3.2
> ii  libx11-6 2:1.6.2-3
> ii  libx11-xcb1  2:1.6.2-3
> ii  libxcb-randr01.10-3+b1
> ii  libxext6 2:1.3.3-1
> ii  libxkbfile1  1:1.0.8-1
> ii  libxrandr2   2:1.5.0-1
>
> Versions of packages gnome-flashback recommends:
> ii  dbus   1.10.8-1
> ii  gnome-settings-daemon  3.20.1-1
>
> Versions of packages gnome-flashback suggests:
> ii  gnome-power-manager  3.20.0-1
>
> - -- no debconf information
>
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCAAGBQJXPG2pAAoJENILQgJc2ie5DAIP/02gLEgq5s6ynUrEDXotxQCd
> KoPLj+8Maa+mi94S1rJHnakWUw1YanNsz5oV04oN8WibqYr9QW++oqY8wxoW2+Xy
> biy5slkgG7/xSoyOVIar3MjEc4IWMLdTzZ3Rjj4vXf5zq40K2zHfR84zdbr98x4X
> ImR4O7aJWj9NJtZosCEeXTcasohbzDeLMKuk2rDqhzWuH4W4rQYotb+N6wfkEqMo
> bRhp6zMCVAz9USKaXctLQLxReGW4BL0J4v1bMivE3ydpfg/9wKmsyH7wg6e/Mz/8
> 7ozVj4vQoD994GNyFD9ipLJCzzdN3I5+4UKsrlRWXOXN2XgCbCXWtn+24A7/9X1o
> RT87ibBERrJY+KJx43RIOhF+dTZFwuub5T8btbiBrCNul68Qpd5FirWYC2t7bcOf
> lMIh3fjsDlgNpP75O2xt7FpzCGub3d5yhG50kMzawbnhnEwo1Md4RsCLU7cCcH2+
> xs/lH6r+5g/VORCt8PO9jFy1Qbu4siQtmaYar20fU9FM6RsmfpPl1HOpM9ggicAG
> Uo3PgB67bxPJKVL7KqiJ5CZfHYG2Pw8KBsF3RidYgMqiLUHXIvxv9hHPV+BdE+3c
> qzgZisgftakc2qnEeVU2u/gzuSckLnW1wqYGeDZRVZvS2LBa2MMfR11WSUHjo1cn
> Q4FFYtvwb/tH0Cadkxe9
> =lWRh
> -END PGP SIGNATURE-
>
>


-- 
Alberts Muktupāvels

Bug#820205: gnome-flashback: NetworkManager fails to auth password with gnome-flashback

[Alberts Muktupāvels]

That is very old version... Any chance you could test version from
unstable? Just to know if this is still problem.

Don't know, but this might be fixed by adding extra autostart file for
polkit-gnome or by adding it as RequiredComponent. Dmitry?

Chris, do you have polkit-gnome installed? Try to start it manually
polkit-gnome-authentication-agent-1 (it is installed in libexecdir so you
will need to use full path).

On Wed, Apr 6, 2016 at 6:04 PM, Chris Burrooughs <chris.burrou...@gmail.com>
wrote:

> Package: gnome-flashback
> Version: 3.10.0-3
> Severity: important
>
> When attempting to connect to a (vpnc) VPN using gnome flashback on
> jessie the following error occurs in the daemon log:
>
> Apr  2 16:21:09 yt530 NetworkManager[2000]:  [1459628469.628285]
> [vpn-manager/nm-vpn-connection.c:1778] get_secrets_cb(): Failed to request
> VPN secrets #2: (6) No agents were available for this request.
>
> And no connection is established. With a classic session, the same VPN
> connection works without any known trouble.  I believe this report is
> substantially similar to:
>  *
> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1440009
>  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784896
>
> The debian bug suggested that the proper course of action was to open
> a bug against gnome-fashback instead of network-manager-pptp-gnome.
>
> -- System Information:
> Debian Release: 8.3
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-flashback depends on:
> ii  gnome-flashback-common   3.10.0-3
> ii  libc62.19-18+deb8u3
> ii  libcairo21.14.0-2.1
> ii  libcanberra-gtk3-0   0.30-2.1
> ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u4
> ii  libglib2.0-0 2.42.1-1
> ii  libgnome-desktop-3-103.14.1-1
> ii  libgtk-3-0   3.14.5-1+deb8u1
> ii  libpulse-mainloop-glib0  5.0-13
> ii  libpulse05.0-13
> ii  libx11-6 2:1.6.2-3
> ii  libxext6 2:1.3.3-1
>
> Versions of packages gnome-flashback recommends:
> ii  dbus  1.8.20-0+deb8u1
>
> gnome-flashback suggests no packages.
>
> -- no debconf information
>
>


-- 
Alberts Muktupāvels

Bug#814949: notification-daemon: /etc/xdg/autostart file only starts for "GNOME-Flashback"

[Alberts Muktupāvels]

On Thu, Feb 18, 2016 at 8:12 PM, Kevin J. McCarthy <ke...@8t8.us> wrote:

> On Thu, Feb 18, 2016 at 12:07:58PM +0200, Alberts Muktupāvels wrote:
> > Openbox is window manager, why should it start something?
>
> Openbox runs the XDG autostart programs because it is helpful.  This way
> when I install, say, parcimonie or hplip-gui or notification-daemon, all
> those packages need to do is create an /etc/xdg/autostart file, and they
> are launched for my X session.
>

Don't know anything about openbox, but in GNOME applications are not
started by window managers but by gnome-session.

> On Wed, Feb 17, 2016 at 12:26 AM, Kevin McCarthy <ke...@8t8.us> wrote:
> > > It seems like the notifications would be useful for all desktop
> > > environments.  Would it be unreasonable to remove the "OnlyShowIn"
> > > line from the autostart file, or would this cause problems in some
> > > desktops?
> >
> > GNOME does not use notification-daemon so starting it in all desktop
> > environments is not solution. Also I plan to stop using
> notification-daemon
> > for GNOME-Flashback, so autostart file will be removed.
>
> I see.  I wasn't aware that notification-daemon was a Gnome project
> package.  Perhaps it should have been named gnome-notification-daemon to
> make this clearer?  Will the package be removed now that GNOME-Flashback
> isn't using it either?
>

It was used by GNOME, now it is used by GNOME Flashback. In 3.20 it will
not be used by GNOME-Flashback too, I have already pushed needed changes to
notification-daemon and gnome-flashback master branches.

It is up to debian packagers/maintainers if it will be removed. I was
responding only as current upstream maintainer.

In any case, I will install another implementation, such as dunst.
>

If you want you can add autostart file for notification-daemon in your home
dir:
~/.config/autostart

Please feel free to close this bug out.
>
> > If your desktop environment uses notification-daemon then it must install
> > autostart file for it.
>
> Just to correct this misunderstanding, my "desktop environment" isn't
> using notification-daemon.  Debian packages that I have installed,
> e.g. profanity, depend on libnotify4, which in turn recommends
> notification-daemon.  However, I mistakenly installed the actual
> "notification-daemon" package, thinking it was a generic solution.
>

There is nothing specific to GNOME in notification-daemon so you can use it
generic solution if you want.

-- 
Alberts Muktupāvels

Bug#814949: notification-daemon: /etc/xdg/autostart file only starts for "GNOME-Flashback"

[Alberts Muktupāvels]

On Wed, Feb 17, 2016 at 12:26 AM, Kevin McCarthy <ke...@8t8.us> wrote:

> Package: notification-daemon
> Version: 3.18.1-1
> Severity: normal
>
> Dear Maintainer,
>
> I use the openbox window manager.  In jessie, notifications from
> applications using libnotify would display, but I recently updated to
> stretch and discovered the notifications were no longer displaying.
>
> After some poking around, I found it was because there is a
> "OnlyShowIn=GNOME-Flashback" line in
> /etc/xdg/autostart/notification-daemon-autostart.desktop, which causes
> openbox not to start the daemon.
>

Openbox is window manager, why should it start something?

It seems like the notifications would be useful for all desktop
> environments.  Would it be unreasonable to remove the "OnlyShowIn"
> line from the autostart file, or would this cause problems in some
> desktops?
>

GNOME does not use notification-daemon so starting it in all desktop
environments is not solution. Also I plan to stop using notification-daemon
for GNOME-Flashback, so autostart file will be removed.

If your desktop environment uses notification-daemon then it must install
autostart file for it.

-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

Debian has patched at-spi2-core to autostart it always:
http://anonscm.debian.org/cgit/pkg-a11y/at-spi2-core.git/commit/?id=e049804d87fab6c1209f2470cd53acb772885eb7

So only problem here was that at-spi-bus-launcher failed to register with
session manager. And that is fixed by patch I linked previously.

If you don't want that at-spi-bus-launcher is autostarted then it is/will
be separate bug and must be reported against at-spi2-core package.

P.S. This bug could be moved to that package too... But I hope that Dmitry
will make sure that patch is applied in debian package.


On Wed, Jan 27, 2016 at 6:02 PM, Massimo Martelli <hirog...@gmail.com>
wrote:

> But at-spi-dbus-bus.desktop still got started in the second log, wasn't
> that a problem?
>



-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

How are you starting session? With display manager? lightdm, gdm?

I see in log file gnome-flashback-init, gnome-flashback and gnome-panel
is-disabled:1 - that could mean that XDG_CURRENT_DESKTOP is not set
correctly Show output from this command:
echo $XDG_CURRENT_DESKTOP

--

It is nice that patch fixed problem, but still I have no idea why
at-spi-bus-launcher is started... Oh, I found why:
http://anonscm.debian.org/cgit/pkg-a11y/at-spi2-core.git/commit/?id=e049804d87fab6c1209f2470cd53acb772885eb7

Dmitry: did you see this bug? can you make sure that patch is applied in
at-spi2-core?


On Wed, Jan 27, 2016 at 5:18 PM, Massimo Martelli <hirog...@gmail.com>
wrote:

> Ok, so patch is applied, and it works great.
> There is no .xsession-errors, anyway I'm attaching the session debug
> log as requested.
> at-spi-dbus-bus.desktop is launched anyway.
> In the log it seems to say that it's not disabled. is there any other
> way to check/change it other than gsettings?
>
> gnome-session-binary[12358]: DEBUG(+): GsmManager:  ID:
> /org/gnome/SessionManager/App25 app-id:at-spi-dbus-bus.desktop
> is-disabled:0   is-conditionally-disabled:0
> ...
> gnome-session-binary[12358]: DEBUG(+): GsmAutostartApp: starting at-
> spi-dbus-bus.desktop: command=/usr/lib/at-spi2-core/at-spi-bus-launcher
> --launch-immediately startup-
> id=1014d5c9efaca4005714539074499674010123580024




-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

Ok, so there is no extra problem. :) Only at-spi2-core must be patched and
then this bug can be closed.


On Wed, Jan 27, 2016 at 5:46 PM, Massimo Martelli <hirog...@gmail.com>
wrote:

> Normally I use gdm, but that log was produced starting X and the gnome
> session manually, so that must be why gnome-panel was disabled.
> Setting the XDG_CURRENT_DESKTOP before starting manually both X and
> session produced the log I'm attaching now.




-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

Just to be 100% sure, this returns "false", right?:
gsettings get org.gnome.desktop.interface toolkit-accessibility

Ok, lets first apply that patch and test if it works. If it does not,
please attach .xsession-errors with --debug added to gnome-session.


On Wed, Jan 27, 2016 at 3:54 AM, Massimo Martelli <hirog...@gmail.com>
wrote:

> I'm sorry I thought you meant THIS one: https://git.gnome.org/browse/at
> -spi2-core/commit/bus?id=2a70ba6bf83a675664cda8f68f2d1e815612db53
> That's the commented line I was talking about. Anyway tomorrow I'll
> apply the patch and try again.
> I really don't know what to say about it starting even if it's not
> enabled, but I'm sure I'm not mistaken about it.
> Anything else I can check to help you find the cause?
>



-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

Is there something in ~/.xsession-errors? You could try to start session
with --debug. Open /usr/lib/gnome-flashback/gnome-flashback-metacity and
add --debug and then look in .xsession-errors and/or post it somewhere.

On Tue, Jan 26, 2016 at 6:53 PM, Massimo Martelli <hirog...@gmail.com>
wrote:

> Thank you for your reply, however looks like it's not enabled on my
> system. Is there any kind of log or output I could check?
> The only thing that came to mind was to check for X11 logs, but there's
> nothing interesting there, google was no help, and besides, other
> sessions work just fine, so I figured it has to be this specific
> session. Also I forgot to mention, I tried creating another user and
> logging that in (out of fear that some per-user configuration was to
> blame), but the problem keeps happening on that new user too.
>
> On mar, 2016-01-26 at 14:47 +0200, Alberts Muktupāvels wrote:
> > Any chance that you have enabled toolkit accessibility?
> > org.gnome.desktop.interface toolkit-accessibility is enabled?
> >
> > If so, can you patch at-spi2-core with patch from this bug:
> > https://bugzilla.gnome.org/show_bug.cgi?id=753931
> >
> >
> > On Mon, Jan 25, 2016 at 2:23 AM, Maxxie <hirog...@gmail.com> wrote:
> > > Package: gnome-session-flashback
> > > Version: 3.18.1-1
> > > Severity: important
> > >
> > > Every time I start a gnome flashback session it just shows me a
> > > black screen
> > > and the mouse which can't be moved. After waiting a couple of
> > > minutes the
> > > session starts and it works perfectly until the logout. While the
> > > screen is
> > > black I'm able to ssh to my computer and even start graphical
> > > programs in it
> > > (tried gedit). Switching user does not trigger the problem, nor
> > > does standby.
> > > Other gnome sessions work flawlessly.
> > >
> > >
> > >
> > > -- System Information:
> > > Debian Release: stretch/sid
> > >   APT prefers unstable
> > >   APT policy: (500, 'unstable'), (1, 'experimental')
> > > Architecture: amd64 (x86_64)
> > >
> > > Kernel: Linux 4.5.0-rc1-maxxie (SMP w/8 CPU cores; PREEMPT)
> > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> > > Shell: /bin/sh linked to /bin/dash
> > > Init: systemd (via /run/systemd/system)
> > >
> > > Versions of packages gnome-session-flashback depends on:
> > > ii  gnome-flashback3.18.1-1
> > > ii  gnome-panel3.18.1-1
> > > ii  gnome-session-bin  3.18.1.2-1
> > > ii  gnome-session-common   3.18.1.2-1
> > > ii  gnome-settings-daemon  3.18.2-1
> > > ii  gnome-shell [notification-daemon]  3.18.3-2
> > > ii  metacity   1:3.18.1-1
> > > ii  nautilus   3.18.4-1
> > > ii  notification-daemon3.18.1-1
> > >
> > > Versions of packages gnome-session-flashback recommends:
> > > ii  gnome-power-manager  3.18.0-1
> > > ii  gnome-screensaver3.6.1-7+b1
> > >
> > > Versions of packages gnome-session-flashback suggests:
> > > ii  desktop-base  8.0.2
> > > ii  gnome-keyring 3.18.3-1
> > > ii  gnome-user-guide  3.18.1-1
> > >
> > > -- no debconf information
> > >
> > >
> >
> >
>



-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

On Wed, Jan 27, 2016 at 3:33 AM, Massimo Martelli <hirog...@gmail.com>
wrote:

> Looks like you were half right about accessibility.
> From the logs I found out this:
> gnome-session-binary[4732]: WARNING: Application 'at-spi-dbus-
> bus.desktop' failed to register before timeout
> appearing right after the black screen. Anyway I do have accessibility
> disabled (triple-checked) and it's weird that other gnome sessions work
>

It would be nice to understand why it was autostarted even if it was
disabled...


> fine. What's even weirder is that it looks like my at-spi-dbus-
> bus.desktop already has that line not commented so the patch is not
> needed.
>

What line commented out?


> For now, since I don't use it, I worked around the issue moving the at-
> spi-dbus-bus.desktop file out of the way. Thank you so much for your
> kind help, I guess I'll have to report to the gnome bugtracker for this
> issue :)
>

gnome-session should start it only if it is enabled:
AutostartCondition=GSETTINGS org.gnome.desktop.interface
toolkit-accessibility

Failed to register before timeout was fixed today (master):
https://git.gnome.org/browse/at-spi2-core/commit/?id=d4ae614301bbc7f7204dab795cbd6f1289c401d2

and gnome-3-18 branch:
https://git.gnome.org/browse/at-spi2-core/commit/?h=gnome-3-18

-- 
Alberts Muktupāvels

Bug#812555: gnome-session-flashback (temporary) black screen

[Alberts Muktupāvels]

Any chance that you have enabled toolkit accessibility?
org.gnome.desktop.interface toolkit-accessibility is enabled?

If so, can you patch at-spi2-core with patch from this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=753931


On Mon, Jan 25, 2016 at 2:23 AM, Maxxie <hirog...@gmail.com> wrote:

> Package: gnome-session-flashback
> Version: 3.18.1-1
> Severity: important
>
> Every time I start a gnome flashback session it just shows me a black
> screen
> and the mouse which can't be moved. After waiting a couple of minutes the
> session starts and it works perfectly until the logout. While the screen is
> black I'm able to ssh to my computer and even start graphical programs in
> it
> (tried gedit). Switching user does not trigger the problem, nor does
> standby.
> Other gnome sessions work flawlessly.
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.5.0-rc1-maxxie (SMP w/8 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-session-flashback depends on:
> ii  gnome-flashback3.18.1-1
> ii  gnome-panel3.18.1-1
> ii  gnome-session-bin  3.18.1.2-1
> ii  gnome-session-common   3.18.1.2-1
> ii  gnome-settings-daemon  3.18.2-1
> ii  gnome-shell [notification-daemon]  3.18.3-2
> ii  metacity   1:3.18.1-1
> ii  nautilus   3.18.4-1
> ii  notification-daemon3.18.1-1
>
> Versions of packages gnome-session-flashback recommends:
> ii  gnome-power-manager  3.18.0-1
> ii  gnome-screensaver3.6.1-7+b1
>
> Versions of packages gnome-session-flashback suggests:
> ii  desktop-base  8.0.2
> ii  gnome-keyring 3.18.3-1
> ii  gnome-user-guide  3.18.1-1
>
> -- no debconf information
>
>


-- 
Alberts Muktupāvels

Bug#804150: gnome-flashback: windows move very slowly

[Alberts Muktupāvels]

Hi,

this is not very useful... Please try to provide more info so we can
understand what is going on.

1) What video card do you have / video drivers?
2) Do you have same problem when you disable compositing manager?:
gsettings set org.gnome.metacity compositing-manager false
3) Which version was last that did not have this problem?
4) Do you have this problem only with server side decorations
(gnome-terminal) and/or also with csd windows (nautilus)?

And any other info that could be helpful.

On Thu, Nov 5, 2015 at 3:12 PM, Joachim Schmidt  wrote:

> Package: gnome-flashback
> Version: 3.18.1-1
> Severity: normal
>
> Dear Maintainer,
>
> "every" window moves very slowly by mouse move on my Intel 2-core machine.
> This
> is only in flashback mode.
>
>

Bug#801157: notification-daemon:amd64: Notification body is blank when containing a

[Alberts Muktupāvels]

On Wed, Oct 7, 2015 at 2:11 AM, Frédéric Brière  wrote:

> Package: notification-daemon
> Version: 3.18.0-1
> Severity: normal
>
> If the body of a notification contains a  tag, notification-daemon
> will display an empty body for that notification.
>
>   $ notify-send 'Summary' 'Body line 1Body line 2'
>

That is not valid pango markup. This is now fixed upstream:
https://git.gnome.org/browse/notification-daemon/commit/?id=620c53fc9cec4ac4ed79754c71429be9db4a7a77

Bug#790615: metacity crashes with SIGSEGV in meta_frame_get_frame_bounds

[Alberts Muktupāvels]

On Tue, Jun 30, 2015 at 3:39 PM, Antonio Ospite a...@ao2.it wrote:

 On Tue, 30 Jun 2015 14:38:04 +0300
 Alberts Muktupāvels alberts.muktupav...@gmail.com wrote:

   Since I upgraded to metacity 3.17 I get these sporadic crashes.
  
   The first thing I looked at was in dmesg and this is what I got:
  
   traps: metacity[2515] general protection ip:7f1153f2dc00
 sp:7fffac774eb8
   error:0 in libmetacity-private.so.3.0.0[7f1153ef4000+a]
  
   I then investigated further with gdb and got a backtrace of the crash,
   please see the attached file.
  
   If I had to guess I'd say that the crash may be related to some
 activity
   with modal dialogs from Gtk, but I am not 100% sure about that.
  
 
  Can you give steps how to reproduce crash?
 

 It does not happen every time, but I'd say that when it does, it is
 after a dialog has been shown.

 For instance I use sylpheed, an email client based on Gtk2, and when
 checking new emails a dialog with a progress meter is shown, sometimes
 when metacity crashes it looks like it is when the dialogue is just
 going to be destroyed.

 I also managed to trigger the crash using zenity 3.16.3, with zenity
 --calendar or zenity --error after clicking OK, but this is not
 consistent either, it happens only sometimes.


When I try to reproduce it just does not want to crash... :( It happens
when I don't expect it.

Let me know if you have any more questions.


Please report this bug upstream:
https://bugzilla.gnome.org/enter_bug.cgi?product=metacity

-- 
Alberts Muktupāvels

Bug#790615: metacity crashes with SIGSEGV in meta_frame_get_frame_bounds

[Alberts Muktupāvels]

 Since I upgraded to metacity 3.17 I get these sporadic crashes.

 The first thing I looked at was in dmesg and this is what I got:

 traps: metacity[2515] general protection ip:7f1153f2dc00 sp:7fffac774eb8
 error:0 in libmetacity-private.so.3.0.0[7f1153ef4000+a]

 I then investigated further with gdb and got a backtrace of the crash,
 please see the attached file.

 If I had to guess I'd say that the crash may be related to some activity
 with modal dialogs from Gtk, but I am not 100% sure about that.


Can you give steps how to reproduce crash?


 I can avoid the crashes by using metacity=3.14.3-1 but that mean I loose
 the windows theme.

 BTW, is there an IRC channel where we can discuss gnome-flashback
 issues?


No. Please use gnome-flashback-l...@gnome.org mailing list.

Bug#773644: gnome-session-flashback: Applications with header bar do not show fallback menus in flashback session, no way to access menu

[Alberts Muktupāvels]

On Sun, 21 Dec 2014 12:49:47 +0100 Florian fb...@gmx.net wrote:
 Package: gnome-session-flashback
 Version: 3.8.1-7
 Severity: important

 Gnome applications with header bar do not show their fallback menus in
flashback
 session. I also tried the newer flashback package from experimental, but
without
 success. This seems to be related to this list message:

https://mail.gnome.org/archives/gnome-flashback-list/2014-September/msg00019.html

 I have not found any indication that these patches already exist, but
maybe someone
 with knowledge of these things does know what to do here? I think this
problem
 quite severely limits the usability of several gnome applications in the
flashback
 session currently in jessie.

Bugs:
1) https://bugzilla.gnome.org/show_bug.cgi?id=739534
2) https://bugzilla.gnome.org/show_bug.cgi?id=738264

wip/flashback branches in gnome-session, gnome-shell, gnome-settings-daemon
and gnome-flashback.

 thanks

 florian



 -- System Information:
 Debian Release: 8.0
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)

 Versions of packages gnome-session-flashback depends on:
 ii  gnome-flashback3.10.0-3
 ii  gnome-panel3.8.1-7
 ii  gnome-screensaver  3.6.1-2
 ii  gnome-session-bin  3.14.0-2
 ii  gnome-session-common   3.14.0-2
 ii  gnome-settings-daemon  3.14.2-2
 ii  metacity   1:3.14.3-1
 ii  nautilus   3.14.1-2
 ii  notification-daemon0.7.6-2
 ii  policykit-1-gnome  0.105-2

 Versions of packages gnome-session-flashback recommends:
 ii  gnome-power-manager  3.14.1-1

 Versions of packages gnome-session-flashback suggests:
 ii  desktop-base  8.0.2
 ii  gnome-keyring 3.14.0-1+b1
 ii  gnome-user-guide  3.14.1-1

 -- no debconf information

Bug#773644: gnome-session-flashback: Applications with header bar do not show fallback menus in flashback session, no way to access menu

[Alberts Muktupāvels]

On Sun, 21 Dec 2014 12:49:47 +0100 Florian fb...@gmx.net wrote:
 Gnome applications with header bar do not show their fallback menus in
flashback
 session. I also tried the newer flashback package from experimental, but
without
 success. This seems to be related to this list message:

https://mail.gnome.org/archives/gnome-flashback-list/2014-September/msg00019.html

As workaround you can try to use xsettings overrides:
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
'{Gtk/ShellShowsAppMenu:0}'