I have tried to use the extensions toggle-touchpad and touchpad-indicator that claim to be able to do this, but neither will load properly. They show up with a little exclamation-point-triangle in the "Tweaks" panel saying "Error loading extension". How to get Jessie gnome system succeeded in getting their touchpad disabled via a simpe toggle mechanism?
I got a problem with a Dell Latitude E5500. I can not disable the hardware beep after the gdm3 login screen has been loaded. All alsa beeps and system sounds are disabled and/or muted. I also tried setterm -blength 0, xset -b in startup scripts. They disable terminal-beeps, but not the halt or the gdm login beep. I tried wasting around with the gconftool, but nothing happened. It is an annoying sound. If you use, init 0 to shut down, no beep comes up.
For some time now I have been unable to update flashplugin. I have been waiting the problem to fix itself, but no.
Here is what happens when I try to update flash:
Code: Select allrob@ace:~$ sudo update-flashplugin-nonfree --status Flash Player version installed on this system : 11.2.202.457 Flash Player version available on upstream site: 11.2.202.460 flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
[Code] ....
The same thing happens on both my Debian Jessie machines..
Any way to force the update? Need to update their flashplugin on Jessie?
To use most of my Kali applications, I want to be able to log into an X session as root. I know it is generally a bad idea and I don't want to do it as a rule, but it is useful for penetration testing (e.g. nmap and its GUI don't have most of the useful options when run as a regular user).
So how do I get GDM3 to allow me to log in as root? Currently, if I type in the user name "root" and log in, it just takes me back to GDM3. Could it work to add root to my user group (I really don't want to add all kinds of security holes)?
How do you disable startx in Jessie when it boots up? In Wheezy I just had to disable the gdm3 service. I also tried a few settings in grub, but it still starts.
I installed jessie from a beta/rc shortly before release on my MacBook Pro 13 Retina and have kept it up to-date with apt-get dist-upgrade. Rcently gdm3/gnome-session have stopped working together. When I log in the screen goes black for a couple of seconds then goes back to the login screen. This happens with "System Default", "GNOME Classic" and "GNOME", but not with "GNOME on Wayland". However, Wayland seems to have some other issues. I haven't tried an alternative dm yet, eg lightdm, but the GNOME desktop does work when started with startx.
I've just used journalctl to get logs of what gdm3 and gnome-session were doing at the time. After booting I waited until the clock reached the next minute (19:55) so I'd know at which point in the logs I'd hit enter on my password. I'll post the gdm log separately in two chunks because the forum server doesn't seem to like text attachments and they're too long for one post.
Log from gnome-session: Code: Select all-- Logs begin at Thu 2015-05-07 19:54:06 CEST, end at Thu 2015-05-07 19:56:41 CEST. -- May 07 19:54:08 jeanette gnome-session[885]: gnome-session[885]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
1 Debian Gnome3 does not create ~/.config/monitors.xml 2 according to dconf editor
the location is
/etc/gnome-settings-daemon/xrandr/monitors.xml
and I tweaked, but no success.
[URL] .... method can be applied to GDM3 directory.
Since I have configured my x rortation only be xrandr command by shell init script, and never had configured by GUI setting, the monitors.xml was not created. When I done with GUI, the file is created as usual.
I'm using jessie and since I upgraded from wheezy, gdm3 no longer shows a list of users in the logon screen. (I can still log on by selecting "other users").
I had previously had the same symptoms on wheezy, but had fixed it by changing "UID_MIN" to 500 in /etc/login.defs
Running Jessie (with a low-pinned Debian-based repositories added to my sources.list (e.g. Kali, kxstudio) for those packages not currently available on Debian (like the Kali menu of security tools). Running on a HP 15-r189nd (Energy Star) laptop.
First question: How do I get GDM3 to add root as an option during login? I can type the root user name in. I don't need it to show the root user in the user list (would actually prefer to need to type it in), but I do want to be able to start an X session as root, since some of the Kali tools (e.g. nmap) needs root to function fully. If I type in root and try to start, it just takes me back to the GDM3 login.
Second question: When I want to select my Desktop Enviroment/Window Manager in GDM3, the list appears below the little gear so I can only see half of the list (xfce not visible to select). How do I change the GDM3 appearance/settings that will change the position of the DE list?
Third question: How do I get multiple X sessions running simultaneously? What I have been able to do, while logged in as myuser and running X on tty7, is to log into a tty[1-6] as root, and then startx -- :1, but this somehow skips my default desktop manager (GDM3) and boot straight into LXDE (with no menus!). In /etc/X11/default-diplay-manager I have: /usr/sbin/gdm3 ? How do I get startx -- :1 to start a desktop manager?
Fourth question: When I did the above startx -- :1 as root, it would start the X session in the same tty (e.g. tty2) where I was logged in as root running the startx command. It used to be (in older Linux versions) that startx -- :1 would start an X session on tty8 (and the default would be :0 on tty7). Is this the (new) way things are supposed to work? Or is there something wrong with my setup?
Question 5: Once I have started an LXDE session as root, how do I get it to show the full application menu that my regular user can see? Can I just copy the config files over? Which ones? Or is there a better way?
Question 6: Gnome used to start fine. Then I ran Gnome on Wayland once, and now regular Gnome (on X?) no longer runs, but give me a "Oops! Something went wrong" error and Alt-F4 just takes me back to GDM3. Classic Gnome and Gnome on Wayland still runs OK. Should I log a bug report?
I changed my user name with the following commands:usermod -l $newname $oldnamegroupmod -n $newname $oldname usermod -d /home/$newname -m $newnameAlso replaced every instance of /home/$oldname ith /home/$newname in ~/.config.Now gdm3 hangs with a black screen and wristwatch icon. (I can move the icon with the mouse.) This worked fine with gdm. I've looked for gdm3 files that have /home/$oldname in my home and in /etc and couldn't find anything significant.Anyone have any ideas or suggestions on how to fix this or where to look? For now, I've disabled gdm3, and I'm using startx. This is an installation in virtualbox. I just tried using ctrl-alt-F1, but it dropped me to console in the host system. (Nice rush of adrenaline came with that.)
The only errors in Xorg.0.log are there even with a successful startx. (EE) Failed to load module "xboxvideo" (module does not exist, 0)(EE) open /dev/fb0: No such file or directoryCouple more bits of relevant information - this was a live-build that I installed using refractainstaller. I also changed /etc/inittab to disable auto-login. Here are the changes, original lines commented out, new lines look like the inittab in my regular squeeze install, but I don't think this is the problem (see below.)
#1:2345:respawn:/bin/login -f user </dev/tty1 >/dev/tty1 2>&1 #2:23:respawn:/bin/login -f user </dev/tty2 >/dev/tty2 2>&1 #3:23:respawn:/bin/login -f user </dev/tty3 >/dev/tty3 2>&1
Yesterday I done an upgrade with apt and since that time whenever I boot up I am presented with only a blank screen and an unresponsive cursor. I cannot switch console using Ctl+Alt+F*. The only thing I can do is Alt+SysRq+(R,E,I,S) which kills gdm3 and gets me back to the console.
* I can get into Xorg fine via the startx command * As a temporary fix, if I enable automatic login (via /etc/gdm3/daemon.conf) then gdm3 works.
But I can't get the normal authenticated login screen to work.
Output of journalctl for a failed attempt at running gdm3 with verbose debugging enabled:
Code: Select allOct 25 01:24:43 [hostname-removed] systemd[1]: Starting GNOME Display Manager... Oct 25 01:24:43 [hostname-removed] systemd[1]: Started GNOME Display Manager. Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Enabling debugging Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Changing user:group to Debian-gdm:Debian-gdm Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Successfully connected to D-Bus
[Code] ....
One other thing worth noting, before upgrading yesterday, I changed mirrors and accidentally pasted in "stable" into /etc/apt/sources.list. So basically I did an initial upgrade, realised my mistake, switched back to testing (which I was on before) and done another upgrade, which is when I noticed this problem.
In the gmd3 greeter.conf-defaults file its tells me the themes are located /desktop/gnome/interface/gtk_theme, but wheres that directory actually at, like how I can find it?
Btw, I know I can go back to gdm, but I'd rather understand how to theme this, before. I might just.I'm using compiz, btw, if that makes any difference.
I just installed successfully Wheezy, but I can't change my Login Window Theme.I put the three files (.desktop .xml and.jpg) in/usr/share/gdm/autostart/LoginWindow/),I think that my mistake is here but I don't know where to put the .xml file and the .jpg files.And the I edited the file/etc/gdm3/greeter.gconf-defaults.The background is well-displayed but the "theme" is still the same.
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
Running Compiz as a standalone WM.Managed to get Slim working, will post how later, but have no sound. If I boot using gdm3 the sound works. Obviously gdm3 loads something Slim doesn't, but can't workout what!Tried adding /usr/bin/pulseaudio --start --log-target=syslog & to my script - no dice, still no sound
I have been using linux for about a year and have run into a new problem I am unable to solve. It started when I attempted to install some packages I needed to get VirtualBox to run VMs. I am on Jessie.
I am unable to install various packages, including gedit, aptitude etc. I do not think it is a problem with my sources.list as my laptop has the same sources.list and I am not encountering the same problems on it. Packages will not install any dependencies. -f install isn't doing anything for me.
My sources.list...
deb [arch=amd64,i386] http://ftp.ca.debian.org/debian/ jessie main contrib non-free deb-src [arch=amd64,i386] http://ftp.ca.debian.org/debian/ jessie main contrib non-free
deb http://ftp.ca.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.ca.debian.org/debian/ jessie-updates main contrib non-free
[Code] ....
I tried to check for held packages with
userone@localhost:~$ dpkg --get-selections | grep hold
After doing Debian's apt-get dist-upgrade from Wheezy/oldstable to Jessie/stable, I decided to try Kernel v4.2.0 instead of v3.16.0-4-amd64 to be even more updated. However, X doesn't work. /var/log/Xorg.0.log showed:
Code: Select allX.Org X Server 1.16.4 Release Date: 2014-12-20 [ 453.305] X Protocol Version 11, Revision 0 [ 453.305] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Recently tried to make RAID1 on MBR partitions scheme on Debian Jessie - debian-8.1.0-amd64-DVD-1. The issue - I have unable to boot from second drive after grub-install /dev/sdb by any ways. RAID1 itself for / swap and home is fully functional. Decided to try the same thing on GPT, same story. How to boot from second drive on most recent Debian Branches?
I recently upgraded from wheezy to jessie and everything went as planned with dist-upgrade. However I just noticed that I can't play any video file. I thought about upgrading vlc, as it was already installed but it had dependency problems. So I tried to remove it
Code: Select allsudo apt-get remove --purge vlc
Then If I try to install vlc I receive this message:
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may resolve the situation:
The following packages have unmet dependencies:
vlc : Depends: vlc-nox (= 2.2.0~rc2-2) but 2.0.3-5+deb7u2+b1 is to be installed Depends: libvlccore8 (>= 2.2.0~pre1) but it is not going to be installed Recommends: vlc-plugin-notify (= 2.2.0~rc2-2) but it is not going to be installed Recommends: vlc-plugin-samba (= 2.2.0~rc2-2) but it is not going to be installed Breaks: vlc-nox (< 2.2.0~pre2-2~) but 2.0.3-5+deb7u2+b1 is to be installed E: Unable to correct problems, you have held broken packages.
Now, I thought about removing vlc-data but I received this message saying that 253 packages will be removed (624Mb worth of applications). Am I uninstalling my entire system with this?
This is my sources.list
deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free
- Debian boots normally - I get the login screen - Once my credentials entered, I see only the grey foreground of the login screen for a couple of seconds, then a black screen with a prompt for like half a second and then I'm back to the login screen. No error message, nothing.
When booting in recovery mode and use startx, it works fine (it's my setup at the moment). From there, if I start gdm3 (systemctl start gdm.service), I get the black screen with a prompt and I can do nothing, I have to shut down directly by pressing the button.I tried to add Debian-gdm user to the video group (even if I don't use nVidia drivers), to replace gdm by lightdm and even to remove any display manager but the issue is not solved.Here are some outputs:
Code: Select all# dpkg-reconfigure gdm3 Job for gdm.service failed. See 'systemctl status gdm.service' and 'journalctl -xn' for details. invoke-rc.d: initscript gdm3, action "reload" failed Code: Select all# journalctl -xn -- Logs begin at Tue 2015-12-29 19:16:26 CET, end at Tue 2015-12-29 20:20:55 CET
[code]....
Since removing gdm didn't change anything, I assume it doesn't have anything to do with it but still.
I'm trying out a Jessie install and have noticed VNC doesn't work as well as it used to. I often install a desktop environment on a headless machine, disable *dm, and use vnc4server to create a desktop session if I want to use a GUI. When I try to do the same on Jessie, I run into problems.
Using Gnome, all I get is the generic "Oops something went wrong" error. Looking at .xsession-errors, there are some errors that hint at the problem.
Code: Select allXsession: X session started for ryan at Mon Dec 29 06:07:30 CST 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8
[Code] ....
Some possibly related bugs: [URL] ...
The same thing seems to happen with Cinnamon. Since I doubt a fix for the above issue will make it into Jessie, I tried XFCE. However, that doesn't work correctly either. When running XFCE via VNC something is misreporting the version of xrandr as 1.1 instead of 1.4. Since xfsettingsd appears to want version 1.2+, many things are broken.
This post on the Ubuntu forums suggests the issue might be fixed in xfsettingsd version 4.11: [URL] .....
Is there a better way of getting a remote desktop in Jessie that I'm overlooking?
I am using Jessie. 64 bits. I have been using Sound Converter in other distros (LMDE, Ubuntu, etc) in the past.Jessie has Sound Converter 2.1.3. I think I have installed the needed codecs. When I try to convert from mp4 to mp3, the program gets stuck, and nothing happens. Other formats can be converted.
When I use SoundKonverter (also in Jessie, version 2.1.1) it works with no problem, converting from mp4 to mp3. Nevertheless I would prefer to use Sound Converter.
A few weeks ago I have installed Debian Jessie on KDE Desktop Version. I have a problem with the Display Manager Kdm, if i log out session the monitor turns off (DVI No Signal), the only option that I have it's forced shutdown or reboot via power button. I try another DM lightdm and this works fine. But i liked to know why log out session crash on Kdm.
Adding : TerminateServer=true at the end of /etc/kde4/kdm/kdmrc (Section :[X-:*-Core], solve the issue.
I'm trying to install KDEConnect on my 64 bit Debian system. It's failing because of dependencies.
Tried installing the first dependency, sshfs. It said it cannot find the 64 bit package. So, I tried the 32 bit. That one depends on fuse. Tried to install fuse 32 bit. hat depends on sed. Tried installing 32 bit sed, but the package manager said it's risky to replace 64 bit sed with the 32 bit variant.
I stopped here thinking that I'm risking some stability and the road to the finish line is not visible till the end, meaning I might lose hours trying to do something that fails at the last step. This happened to me few times in the past (with other software) and I really don't want to repeat the incident. I need a stable system and I need my time.
The question is: how to get installed kdeconnect package on Jessie 64 bit ...
X won't start (awesome WM) after upgrading to jessie. It seems to startup up, then just stops. I'm running startx from the command line after logging in. The xorg log (bottom) looks good and I see an exit code of zero.
I do see this in sysout:
Code: Select alldebian xf86TokenToOptinfo: table is NULL
Googled around but I can't find anything specific on this one.
I'm not using any xorg.conf, as booting into a linux rescue cd everything works ok
Code: Select all[ 2275.960] X.Org X Server 1.16.4 Release Date: 2014-12-20 [ 2275.960] X Protocol Version 11, Revision 0 [ 2275.960] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 2275.960] Current Operating System: Linux jj 3.14.25 #1 SMP Fri Dec 5 10:17:33 EST 2014 x86_64
I'd like to have acestreamplaer installed in jessie, but I am not able to do it....
I tried with Acestream repos: deb http://repo.acestream.org/ubuntu/ saucy main
But I cant install it, I got this
acestream-player-data : Depende: libavcodec53 (>= 4:0.7-1) pero no es instalable o libavcodec-extra-53 (>= 4:0.7-1) pero no es instalable Depende: libavformat53 (>= 4:0.7-1) pero no es instalable o libavformat-extra-53 (>= 4:0.7-1) Depende: libavutil51 (>= 4:0.7-1) pero no es instalable o libavutil-extra-51 (>= 4:0.7-1) Depende: libdvbpsi7 (>= 0.2.0) pero no es instalable Depende: libupnp4 pero no es instalable o libupnp3 pero no es instalable Depende: libx264-120 pero no es instalable
