I installed debian 7 with lightdm and MATE 1.8 (from backports) on a new PC.
Since the first day the mose keeps disappearing. For example when I click on something, the mouse disappears and only comes back when I move it. Sometimes it already disappears when hovering over a button (especially annoying when it happens while you try to resize a window).
That problem did not happen for example in LXDE, which I installed just to test that.
I did install MATE 1.8 on several laptops/PCs so far, never hat that problem. Maybe it's because of quite recent hardware?
In Jessie the lightdm login screen does not bring up a lightdm-gtk-greeter dialog box but what seems to be some other one. I can increase the font size by modifying the /etc/lightdm/lightdm-gtk-greeter.conf file, but the login dialog box will not grow to accommodate the larger font (old eyes). The lightdm-gtk-greeter dialog box in Wheezy was a rectangle with a glyph of a console centered in its upper portion, and all the files I have examined indicate that this should be the same in Jessie, but instead the login screen in Jessie displays a narrower rectangle with a head-and-shoulder stylization off to the left.
Yesterday I have upgraded from repo and there was an update regarding mate-desktop and mate-desktop-common to version 1.10.1 (while the rest of the packages are 1.8.x). Well I upgraded and now I cannot start mate-display-properies to configure my monitor, it crashes all the time.
This is the error found with gdb: Starting program: /usr/bin/mate-display-properties [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [New Thread 0xb645ab40 (LWP 5958)]
No symbol table info available.
I am on Debian 8 testing
Linux debian 4.1.0-1-686-pae #1 SMP Debian 4.1.3-1 (2015-08-03) i686 GNU/Linux
My mouse cursor is disappearing when it's not moving, or when I scroll a window with the middle wheel... Then when I move the mouse, the cursor is appearing!
This has started after few things...:
- old video card has died (ati hd4850) - integrated motherboard video card used (ati hd4250) after solving the black screen (xorg, ati drivers... you know :s ) - since many weeks, computer has not been used before I've plugged a hd7970, solved 1 more time the black screen (.....)
And after many updates + this new video card = cursor is kidding :p
I've tried to change my cursor settings in the GUI config, nothing better.
Is it just me or does a page full of animated GIFs act funny on Fedora 14?
Half the emoticons like to flash and disappear and things, even right clicking one and doing "view image" links to a gif that keeps disappearing and flickering. But when saved and viewed in another program (aMSN for instance) the GIF is fine.
I have an odd issue -- fairly fresh Debian Testing install, using Lightdm.
After booting up, Lightdm starts, and then a moment or two later restarts. As a result, any keystrokes captured by the first run (e.g. the first few characters of my username) are lost. My lightdm log is:
Code: Select all[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.16.7, UID=0 PID=827 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.
I have Debien 7.8 Wheezy installed on my laptop, along with the GNOME desktop. As I absolutely hate the new GNOME layout I want to install MATE so I can get the classic GNOME 2 desktop back. But I have no internet connection here at home (I only have my phone for internet and I can't tether it).
So I'm wondering if it's possible for me to download all the packages and install MATE offline? I don't even know what all the packages are that I need.I can download the packages with my phone with no issue.
I installed Debian on my laptop with the Debian DVDs in case you were wondering. when I downloaded the Debian DVD ISOs, I only saw three ISO files, but the documentation said that it's a 10 DVD set. What happened to the other 7 DVD ISOs?
I recently installed 8.1, the Gnome Classic DE isn't anything near worth using now. What happened to The Gnome Classic that I know and love? I don't mind MATE too much, if only the applets I put in the panel would stay put between logins instead of manifesting wherever The OS decides IT wants them instead of where I placed and locked them.
I'm looking for a way to get back the Gnome Classic I know and love from Wheezy (first choice), or get the applets in MATE to stay where I put them (second choice).
Since I've made the switch to Systemd, I've been having various problems with LightDM.
The most interesting and frustrating problem is when I choose Shutdown or Restart from the XFCE4 shutdown menu, the XFCE4 session closes but then the lightDM greeter pops back up. The system doesn't even try to shut down.
Its as if restart and shutdown both act the same as the Logout button.
Im running XFCE4 4.12 (but same behaviour on 4.10). I have the latest LightDM and the latest Systemd.
Are there any sound schemes for GNOME and MATE? Like different system sounds and a logon-logoff sound and a system sound for when I empty the trash bin? Like the way Ubuntu does, just with different sounds. I'm not that crazy about Ubuntu's system sounds.
I know I don't need it, I think it would just make a nice addition to my laptop and later my desktop.
This is probably a bit of an unusual combination, but I'm using Digikam on Maté. Maybe the problem I'm about to describe just isn't an issue on KDE.
I have my photos in digikam, separated out into various folders. I use the timeline view or the tag view to show just a subset of photos, where the photos are scattered across different folders. Then I want to take those photos and make copies of them onto somewhere else outside of digikam's control, like a USB stick or an external drive or even just another folder. I do not want to change the photos which are in digikam, and I don't want to lose the folder information, tags etc.
I select the photos I want, and choose "Edit"->"Copy". But in my file manager Caja there is no "Paste" command available. I guess that Digikam has copied them into a KDE clipboard and Caja can't find them.
I can drag them into another folder of digikam, and that offers me a pop menu - do I want to move or copy? I can also cancel this if I realise it's not what I want to do.
I can also drag them to Caja, but then I have to be really careful. If I just let go (expecting the move/copy prompt), then it just goes right ahead and moves the pictures out of digikam, which is absolutely awful. The photos are gone from digikam, I lose what folders they were in, I lose what tags they had, and there's no confirmation. I have to spend ages moving the photos back where they came from, trying really hard not to lose any, and even then the tags are gone. I guess the file timestamps are destroyed too but I guess that's not so important. It's just a difficult task depending on how many photos there were and how many different folders, and how jumbled the filenames were.
Ok, so now I know that I have to hold the Ctrl key down when I drag, but still the mouse can accidentally let go before I press the key (I can only press the Ctrl after I start dragging, otherwise it deselects the photo I drag with).
The whole thing just seems fragile and error-prone, and there must be a way to make this less painful.
Maybe I can use something other than caja which handles the drop bit of the drag-and-drop better?
Maybe I can configure digikam to temporarily "lock" the photo database to prevent any accidental changes to the files?
Maybe I can configure digikam to confirm before moving files like this, so I can say "cancel"? (I already have "confirm when moving to wastebin" and "confirm when permanently deleting")
Maybe there's another mechanism for copy/paste from digikam to the file system which is more reliable? Some kind of export with a plain copy?
I'm guessing one popular response might be "don't use digikam with Maté", but I like both so that's tricky to resolve.
Failing any of those, is there any separate tool to search through a tree of photos, select those from a given timerange, and copy them to somewhere else? Either keeping the original folder structure or flattening it?
I'm using MATE with Lightdm as display manager in Jessie and I've been using a very simple script run from /usr/share/lightdm/lightdm.conf.d/01_debian.conf to slow down the mouse cursor, something like
Code: Select all#!/bin/bash
xinput --set-prop 10 269 -1
xinput --set-prop 10 267 1.100000 the script was placed in my ~ and called from 01_debian.conf , and so far it used to work.
Lately this script wasn't executed properly, most likely because I had unplugged the mouse from its usb port and then plugged again in a different port, and as a result Lightdm wouldn't start at all.
After much trying, because this by coincidence happened after the update to 8.4, I realized that it wasn't a serious failure of the X server as I suspected (the update included a new version of the flgrx driver), but a simple matter of Lightdm failing because of this script: in fact, I could still manually start the session with startx as regular user, although this only gave me access to a LXDE session instead of MATE (I have also the LXDE environment because when I installed Jessie I did use the LXDE version and then added MATE).
What happened was that the mouse properties were scrambled up, so xinput --set-prop 10 269 -1 had now to be something like xinput --set-prop 10 268 -1 and so on - therefore the script failed and in turns Lightdm failed as well.
-is this supposed to happen when you unplug the mouse and then plug it back in a different usb port? It reminds me of some windows-like behavior, where usb peripherals had to be always in the same port to work properly.
-is Ligthdm supposed to fail because of this, or is it kind of a bug? It looks weird to me that instead of simply not executing the script, the whole display manager fails.
In testing, with an identical setup, as a matter of fact the script failed as well (it's on another partition on the same hardware) but Lightdm started as usual.
-when trying to modify the mouse properties in that script, I couldn't get them right again: what looked correct in the booted system, was once again off at the next reboot (i.e. property 269 was 270 again and so on), therefore I ditched the above setup and placed everything in the .xsessionrc file, and it worked again.
-why startx defaulted to the LXDE environment? where is this setting stored? How could I have specified to start a MATE session instead from command line?
I'm using Mate on Jessie. The problem is that mate-volume-control kinda sucks as an audio control. It doesn't have nearly enough options for a proper volume control program. Pulse is much better for my needs. It or Alsa. Is it possible to remove mate-volume-control, or at least make Pulse the default volume control?
I can't setup or change MIME-Types in Mate/Caja (filemanager)
I use MATE Desktop on Debian 8.1 - File Manager is Caja (1.8.2) - I put in a USB Stick whit Pics. In the Popup Window they came up, normally i can setup a Default behavior for Pics, Music ... But, in my Window the Options are not available. (Grey) The same in "Settings" from Caja (Datenträger) Data Medium.
I updated my system as usually. Sadly since then my screen flickers every 10 (or so) seconds. It turns black for like 10ms and then back to whatever it showed before. This behavior occurs after some uptime. Haven't measured the flicker-free time span yet but I guess it starts after 15 to 30 minutes.I'm using a up-to-date Squeeze with KDE4 an the nvidia-driver for me GeForceGo. Interesting thing is: It does not flicker while using fluxbox using same xserver.
I was experiencing some latency issues when loading KDE on my (squeeze) HTPC box, so I decided to replace the system drive with one that was a bit faster (and larger). Faced with the unpleasantness of having to repeat the many troubleshooting and configuration issues I had with the previous installation, I decided to copy a known good installation. As it turned out it didn't make much difference. I still spent several hours reconfiguring screen and font resolutions, setting up a wireless bridge, removing unnecessary server components, reconfiguring apt proxy settings, resetting hostname and IP addresses, and getting passthrough audio working again.
Anway, once completed, the system was much more responsive, so I was happy--until I tried to burn an ISO to the DVD. When K3b loads it informs me that it is missing several necessary applications, including cdrecord, cdrdao, mkisofs, etc. All the necessary applications were installed and working on the original system which I copied. I verified their existence on the new installation via "aptitude search <packagename>". I even performed a reinstall of said packages. Nevertheless, K3b refuses to detect their existence.Just to be clear, all my boxen are built to standard. Same motherboard, same CPU, same memory, same HDDs, same DVD burners. I do this purposely to avoid just these sorts of issues. I don't see how a working configuration on one machine can fail on another. I am beginning to believe that this is yet more evidence to support my theory that the universe is not only unpredictable, but arbitrary and inconsistent and possibly even perverse.
I found a nice old mini industrial PC with an Jetway NF92 motherboard (Atom N270/Intel GMA945 GPU).
Installed Jessie on it, I have a strange problem under X11: mouse pointer is garbled (looks like somebody cut the arrow in four separate sprite and shake them well , and screen flickering. If I move down the mouse in the lower part of the screen, the screen flicker slowly, if the mouse goes in the top part of the screen, screen flicker rapidly... And finally, putting the pointer on the last line of the screen make the screen stop flickering with perfect screen....
Code: Select allroot@telmat:~# uname -a Linux telmat 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) i686 GNU/Linux root@telmat:~#
Code: Select allroot@telmat:~# lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
Happens on Jessie AMD64 with mate, I can't go to a tty to kill mate system monitor, mouse stop working, keyboard stop working. I tried changing the theme, and now it freeze opening mate system monitor.
I've got a dell optiplex gx620 running 10.04. I just upgraded it from 9.04 (through 9.10 first). The reason I upgraded was becasue I had some problems after installing VLC. Once I'd done this my desktop stopped loading up... in 9.04 I just got the desktop background appearing and top and and bottom toolbars + the mouse pointer all flickering and egg timing. Now in 10.04 I get pretty much the same thing, just the mouse pointer and the occasional white box in the centre of the screen as if it's trying to display a logon box for me but it just can't quite get there... (it used to auto logon).
So, being a noob, I figure I'll just upgrade and hope that that sorts things out... so here I am a whole two distributions down the line still with the same problem. I've had a look around the xorg.conf and found that everything is pretty much default, I did change the device from fx***something*** to vesa in a random attempt to fix things. No dice... same issue. I then had a look in the x log and didn't really see any errors appearing.So I am now wondering if the prolem is X or if it's something else? Trouble is I don't really know where to start.
At links the mouse pointer disappears within Internet Explorer 6.0. I just updated to the latest version of ubuntu which run like a charm. This problem however is annoying.I can press Ctrl to see the pointer but the fact is it should never disappear.
I do have problems with the graphics (Intel 4500) which sometimes at reproducable cases stops responding. (When trying to update graphically and having to answer a question in a child window to the main window). Is this problem a wine setting or something with x11 or compiz or ?
I just installed the ATI Catalyst drivers for my Radeon HD3200, and upon reboot my mouse has disappeared. I can still use it, it's just that there's no pointer on the screen. In addition, moving windows and loading/scrolling any window is very, very slow.I also noticed there's no entry for the mouse in xorg.confI have run aticonfig --intial and aticonfig --initial -f, to no avail.
I have got an interesting issue here. After having ubuntu running for awhile I will visit a certain website that maybe running a script or flash or something and then all of a sudden the screen goes blank for a second and then everything comes back except the mouse pointer is no longer visible. I can logout and then back in and the pointer is back. I wasn't going to ask about it but it is getting annoying having to log out and than back in. I am running a ati card with the iopen source ati driver. It is a VisionTek 9250 pci card with 128 mb of ram. I wonder if it is a combo of this, Adobe Flash and Compiz.
I'm trying to login as guest, but this option does not seem to be available even after changing the LightDM configuration file. I'm on Debian Wheezy + XFCE 4.8. My /etc/lightdm/lightdm.conf looks like this:
System is Wheezy 7.9 with lightdm and MATE desktop.
I have 128GB SSD with various partitions for operating systems and a separate HDD for the /home folders for each OS. Wheezy is my primary system, the others, apart from the original XP are experimental.
/etc/lightdm/lightdm-gtk-greeter.conf is Code: Select all# # background = Background file to use, either an image path or a color (e.g. #772953) # show-language-selector (true or false) # theme-name = GTK+ theme to use
The problem is that each time I use the Ubuntu system and I change back to Debian, the greeter background contains snippets of whatever was displayed while I was in Ubuntu. What I don't understand is how this can happen, given that the operating systems are installed in separate partitions with separate /home partitions as well. After I have used Debian and restart, the greeter screen is clear, as it should be.URL....
I'm running Debian 8.4 on a Lenovo W500 laptop and I recently upgraded from kernel version 3.2.0-4 to 3.16.0-4. Since then I encounter issues with lightdm (I suppose) which manifest themselves in two different scenarios:
1) scenario 1: lightdm fails to start.Instead of showing the graphical login screen, the system boots into terminal. Lightdm seems to be running, but I can't enter the X-Session (Alt+Ctrl+F7 doesn't work), nor can I restart the lightdm via
Code: Select all# service lightdm stop # service lightdm start
dmesg shows the following (I've only pasted the end of dmesg): Code: Select all[ 240.100071] INFO: task kworker/0:2:39 blocked for more than 120 seconds. [ 240.106512] Not tainted 3.16.0-4-amd64 #1 [ 240.112956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.119494] kworker/0:2 D ffff880155155a48 0 39 2 0x00000000
and /var/log/lightdm/lightdm.log shows errors of type Code: Select allGtk-CRITICAL: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
when I then try to shutdown via Code: Select all# shutdown -h now
the OS gets stuck on a message of the form Code: Select allirq 17: nobody cared
and eventually I have to force a shutdown by holding the poweroff button.scenario 2: lightdm starts, but can't be stopped/In this case I can login and use the system as usual, but when I try to shutdown either via # shutdown -h now, or via the GUI or the power button, the system gets stuck and I have to force a shutdown by holding the poweroff button.It seems that people had similar issues on other distros (see e.g.: URL... but there doesn't seem to be a good fix so far. I can for now solve the issue by downgrading the kernel to 3.2.0-4, but I was wondering if there is a permanent fix.