gnome won't start
by Jon LaBadie
On my F22 system I typically use mate as my desktop environment.
Occasionally I log out and try to login using gnome. It quickly
comes up with a screen saying "Opps, something has gone wrong".
If I try "gnome classic" instead, it takes a little longer and
I get a flash of an new desktop before the "Opps" screen.
After the failed login, I went debugging by logging into a
tty terminal.
Looking at ~/.xsessionerrors there are 4 lines of
"stty: standard input: Inappropriate ioctl for device"
and nothing else.
I don't notice any errors in /var/log/Xorg.0.log*.
If I try it logging in as a new user with gnome it starts
up fine.
If I remove ~/.gnome* and ~/.gconf* the problem still occurs.
Any hints where to look?
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
8 years, 3 months
Fedora 23 KDE spin -- no desktop cube?
by William Oliver
I just bought me a new laptop (HP envy) and installed Fedora 23 dual boot
with Win 8.1. Everything works great, but there are a couple of things
about the KDE installation that cause me a bit of a disappointment.
1) There's no desktop cube animation option. Is that a design/deployment
decision, or is it an installation problem? Obviously, losing a bit of
eye-candy is not the end of the world, but I'm a bit dissapointed.
The other is an Activity thing that I'll ask about in a second post, so as
not to mix topics.
Thanks for any information -- a Google search didn't supply anything.
billo
8 years, 3 months
Firefox and gmail troubles
by Chris Murphy
Fedora 23, Firefox 43.0, and 43.0.3.
In the last couple of weeks I started to get this message often while in Gmail:
Oops… the system encountered a problem (#007) - Retrying in 1s…
Often this takes a lot more than 1s to recover. It always happens when
sending emails, and the first attempt for an email always fails,
clicking send again always succeeds.
This happens in safe mode, and with a new test user login account (a
whole new login environment), and it happens with multiple gmail
accounts. If I reboot to OS X, and use Firefox 43, it never happens.
So the network and hardware are identical, the only factor seems to be
something unique to Fedora. There are no messages logged in the
journal at this time.
I've tried disabling firewalld, connecting to another network via
openvpn+private tunnel, and disabling ipv6. No change.
Any suggestions? In the meantime, I'm going to see if I can reproduce
in vmm/kvm booting Fedora 23 live. This is really super annoying.
--
Chris Murphy
8 years, 3 months
O.T. Affordable scanner
by Bob Marcan
Looking for affordable scanner:
no multifunction device (bad experience with Canon)
supported by sane
flatbed
a4 format
scan plain documents
scan photographs in color
scan photographs in B&W (brown&white, my grandpa was born 1888)
scan negative & slides
USB or WIFI
TIA, Bob
8 years, 3 months
Fedora 23 KDE spin -- Widgets falling through to wrong Activity?
by William Oliver
I just installed the Fedora23 KDE spin in a new laptop (HP envy). It has
gone great except for a couple of small glitches. This glitch has to do
with Activies.
When I create a Widget in an activity, it sometimes disappears when I
move it, and ends up in a different Activity. I looked in my
.xsession-error file and see the following, that looks a bit suspicious:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 55266, resource id:
27262984, major code: 18 (ChangeProperty), minor code: 0
list is empty
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:
QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 19809, resource id:
27263004, major code: 18 (ChangeProperty), minor code: 0
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
QXcbWindow: Unhandled client message: "_NET_CURRENT_DESKTOP"
If this isn't the right forum, can someone tell me where I should post
this?
Thanks,
billo
8 years, 3 months
boot problem
by Jeffrey Ross
I'm trying to get Fedora 23 to boot on a a system which will eventually
have no monitor attached (will use a serial console).
The system does have a graphics card in it (and was used for the initial
install) the system now starts booting properly but fails almost
immediately after re-sizing the screen from 80x24 to ???
to make matters even more complicated I am building the system on one
machine and then plan on moving the disks to another system which will
have a different video card (built in but not connected to a monitor)
See below for the serial console output.
Thanks, Jeff
[ 23.759536] ata6: PATA max UDMA/100 cmd 0x3420 ctl 0x3418 bmdma 0x30c8
irq 18
Starting dracut initque[ 24.055876] PTP clock support registered
ue hook...
Starting Show Plymouth [ 24.134932] [drm] Memory usable by
graphics device = 512M
Boot Screen...
[ 24.227675] [drm] Replacing VGA console driver
[ 24.287989] Console: switching to colour dummy device 80x25
[ 24.388640] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.5-k
[ 24.458296] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 24.528976] random: nonblocking pool is initialized
[ 24.592252] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 24.671223] [drm] Driver supports precise vblank timestamp query.
[ 24.744110] vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 24.865151] [drm] initialized overlay support
[ 24.917174] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD
(20150619/video-1157)
[ 25.004502] ACPI: Video Device [IGD0] (multi-head: yes rom: no post: no)
[ 25.086802] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7
[ 25.196256] [drm] Initialized i915 1.6.0 20150522 for 0000:00:02.0 on
minor 0
[ 25.281702] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec)
set to dynamic conservative mode
[ 25.406402] fbcon: inteldrmfb (fb0) is primary device
[ 25.441912] Console: switching to colour frame buffer device 160x64
[ 25.581652] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 25.581655] i915 0000:00:02.0: registered panic notifier
[ 25.830435] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1)
00:1a:4d:14:12:30
[ 25.925019] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 25.925053] e1000e 0000:00:19.0 eth0: MAC: 6, PHY: 6, PBA No: FFFFFF-0FF
[ 26.008784] e1000e 0000:00:19.0 enp0s25: renamed from eth0
8 years, 3 months
Re: [Fedoar 23] Unable to boot Fedora 23 on ASUS ROG Laptop
by Earl Ramirez
>
>
> Date: Tue, 29 Dec 2015 16:32:56 -0800
> From: Tod Merley <todbot88(a)gmail.com>
> To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> Subject: Re: [Fedoar 23] Unable to boot Fedora 23 on ASUS ROG Laptop
> Message-ID:
> <CAPLzRZ_CU=
> WN9f-9gZ9+ptPSgpd3TCJg4Gd-4ZnBt7RREi6fMw(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Possibly related .. http://forums.fedoraforum.org/showthread.php?t=306465
>
> On Tue, Dec 29, 2015 at 4:00 AM, Kari Koskinen <kakoskin(a)gmail.com> wrote:
>
> >
> >
> > 2015-12-29 13:33 GMT+02:00 Earl A Ramirez <earlaramirez(a)gmail.com>:
> >>
> >> Here is where it is stuck; I am using the Fedora 23 x86_64 workstation;
> >> are there any kernel argument that I can use to fix this so that I am
> able
> >> to boot and eventually install Fedora 23?
> >>
> >> Have you tried starting live image in basig graphics mode? You can do
> > this by selecting option "Troupleshooting" in the boot menu and then
> > selecting to boot in basig graphics mode.
> >
> > This will disable kernel modesetting and use basig graphics drivers. Be
> > warned that if you install in basig graphics mode you will have to remove
> > option nomodeset from kernel commandline of the installed system or
> create
> > file /etc/X11/xorg.conf to get sane resolution for GUI.
> >
> >
> >
> > --
> > Kari Koskinen
> >
> > --
> > users mailing list
> > users(a)lists.fedoraproject.org
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
> >
> >
>
Thanks Kari, I had to use Bumblebee since my laptop uses Optimus technology
as Tod pointed out. I disabled the 'nomodeset' from the kernel command line
and just before the GDM loads the OS and it will lock up and you can hear
the fan blowing as if all the resources are being consumed. The only way
around this is to power down the box, if I don't touch the kernel command
line and let it boot, it will get to the GDM; however, each time I try to
login it will come right back to the login screen, but I can go to another
virtual console.
It is fair to say that I can close this thread and open a new one for
Bumblebee because I am able to boot Fedora 23 on the ASUS ROG laptop.
--
Kind Regards
Earl Ramirez
8 years, 3 months
mouse
by Patrick Dupre
Hello,
Using fedora 22 (laptop), the right click of the mouse (USB) does not work.
How can I investigate ?
Thank
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 3 months
WiFi connected but no internet
by hicham
hello everyone
using fedora 23 with gnome, I am having trouble getting connecting to the
net. I get a WiFi connection and i am assigned an ip address from the
router, a question mark appears on top of the screen instead of the wave
logo
but no Internet access
8 years, 3 months
