... that circumvents both problems but does not solve them turns out to be
disabling Wayland and sticking with Xorg by means of changing
#WaylandEnable=false
to
WaylandEnable=false
in /etc/gdm3/daemon.conf and rebooting. The original problems didn't go away, of
course; the bugs still persist in
affects 948288 gdm3
affects 950504 gnome-shell
--
In http://bugs.debian.org/948288 , we deal with a segfault of gnome-shell and
Mesa issues using the default kernel command line without nomodeset. In
http://bugs.debian.org/950504, we deal with the boot process getting stuck when
nomodeset
Dear Bernhard,
As to what happens with nomodeset, I posted another bug report against gdm3:
http://bugs.debian.org/950504. There, we probably won't have to deal with a
gnome-shell segfault and Mesa issues that we have to deal with here.
Best regards,
Md Ayquassar
Here are some initial boot photos.
I added nomodeset as described in https://askubuntu.com/a/38834 . Then, the boot
process displayed some error concerning UMS and radeon early in the process, and
the screen resolution is different. The boot process still gets stuck, and
switching with Ctrl+Alt+F1 followed by Ctrl+Alt+F2 makes it
In the attachment you find /var/log/Xorg.0.log. It contains some error message.
Concerning nomodeset: can I add it during boot process when the grub screen pops
up?
[37.930]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[37.931] Build Operating System: Linux 4.9.0-8-amd64 i686
unless someone has a deterministic
concurrent access to that data.
Fourth, I apologize for long delays.I don’t always have the laptop at my direct
disposal.
31.01.2020, 02:09, Bernhard Übelacker Hello Md
Ayquassar,
sorry, I did not recognize that you
seem to have a usrmerge'd system.
Then I
Dear Bernhard:
In the attachment you find the output again and file generated, namely,
/tmp/reportbug-gnome-shell-backup-20200130-3154-vovyhuqk. (I think the
attachments might be easier to view due to line breaks at proper places.)
Best regards,
Md Ayquassar
reportbug-gnome-shell-backup
Below you find the output of
guest@T42-LAPTOP:~$ reportbug --template gnome-shell
1>>/tmp/reportbug_output.log
2>&1
copied and pasted from the file repotbug_output.log:
Warning: no reportbug configuration found. Proceeding in novice mode.
Detected character set: UTF-8
Please change your
Below you find is the dmesg output.
[ 0.00] Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
[ 0.00] Disabled fast string operations
[ 0.00] x86/fpu: x87 FPU will use FXSAVE
[ 0.00]
Thank you!
The new title describes the issue pretty well.
As for me personally, I'm more interested in a slightly different question of
how
to have white-on-black uxterm by default. (Naturally, one could hack
/usr/bin/uxterm, but this is likely to break on the next package update).
reassign 932375 mutter
severity 932375 wishlist
thanks
Reassign reason: as suggested by Sven, the issue is apparently more related to
the window/display manager rather than to UXTerm itself, cf.
http://gitlab.gnome.org/GNOME/mutter/issues/677
ood* bug report or a wishlist issue for mutter,
since it's not a user-level application that I interact with directly: I know
nothing about mutter. However, I may reassign the current bug report there.
20.07.2019, 19:32, Sven Joachim On 2019-07-20 19:56 +0300,
Md Ayquassar wrote:
> So,
So, would
$ cat .Xdefaults
UXTerm*reverseVideo: true
and a reboot be sufficient? Without rebooting, there is no effect so far. As for
the startup files, I am not aware of any user-level user ones beyond .xinitrc,
~/.Xresources and ~/.config/autostart/*desktop, and all of them seem to be
ignored
Nnow with more newlines for proper html formatting:
The following doesn't help either:
$ cat .config/autostart/source_Xresources.desktop
[Desktop Entry]
Type=Application
Exec=xrdb -merge ~/.Xresources
Hidden=false
X-GNOME-Autostart-enabled=true
Name=Source Xresources
Comment=Source local
The following doesn't help either:
$ cat .config/autostart/source_Xresources.desktop [Desktop
Entry]Type=Application
Exec=xrdb -merge ~/.Xresources
Hidden=false
X-GNOME-Autostart-enabled=true
Name=Source Xresources
Comment=Source local .Xresources
$ cat ~/.Xresources
UXTerm*reverseVideo: true
I know about the -rv option. It's one-off, i.e., you have to provide it again
and
again. As for .xinitrc, I thought that wayland doesn't source it on startup.
> > Anyway, having said all that, what's the "official" way to have the
uxterm
> > default colors *automatically* white-on-black now?
Now properly formatted such that the html output is ok.
$ echo $XDG_SESSION_TYPE
wayland
$ echo $DESKTOP_SESSION
gnome
$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
After taking a look at the reason why they dropped support for loading
.Xresources by default (cf.
$ echo $XDG_SESSION_TYPE
wayland$ echo $DESKTOP_SESSION
gnome$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
After taking a look at the reason why they dropped support for loading
.Xresources by default (cf.
https://bugzilla.redhat.com/show_bug.cgi?id=1225384),
I decided to test whether
Do you use Gnome with Wayland?
I don't know; probably it's still xorg after upgrading from Debian stretch. I'll
double-check and post here in short.
Package: xterm
Version: 344-1
By default, the color of a uxterm is black foreground and white background.
However, I'd like to have it reverse: white text on black background. To this
end, I put
UXTerm*reverseVideo: true
into my ~/.Xresources, run xrdb ~/.Xresources, and reboot. I observe no
Package: thunderbird
Version: 1:60.3.0-1~deb9u1
For several (all?) IMAP e-mail accounts of mine in Thunderbird, whenever I write
a long mail and send it, the autosaved copies in the "Drafts" folder won't
disappear. However, the expected behavior is that after sending an e-mail, all
draft copies
Package: wodim
Version: 9:1.1.11-3+b2
Severity: critical
Starting with a blank 4.7 Gb DVD-R in the optical drive "HL-DT-ST DVD+-RW
GS30N",
my_file.iso containing a freshly downloaded copy of Windows 10 (US English,
x64),
and issuing
$ sudo wodim -v driver=mmc_cd_dvd dev=/dev/sg1 -dummy -dao
Thank you, Norbert. Notice that this bugreport intentionally doesn't insist on a
particular version to be included into Debian, leavong the choice to you: - 2.0
(from http://support.river-valley.com/wiki/index.php?title=Elsarticle.cls) is
mildly buggy (as usual) and very stable. I did try it out.
Package: texlive-publishers
Version: 2016.20170123-5
Severity: wishlist
Please update elsarticle to a newer version. The elsarticle version shipped with
Debian stable (and, to the best of my knowledge, 2018.20180505-1 from Debian
testing), is 1.2.0 from 2009. In the meantime, I saw version 2.0
severity 509574 normalthanks
Similar problem for me here: the lines
deb http://httpredir.debian.org/debian stable-proposed-updates main non-free
contrib
deb-src http://httpredir.debian.org/debian stable-proposed-updates main non-free
contrib
in /etc/apt/sources.list lead to
W: Konflikt bei
26 matches
Mail list logo
