Author Topic: E17 beta 3 bug thread  (Read 8935 times)

loukingjr

  • Guest
Re: E17 beta 3 bug thread
« Reply #15 on: December 19, 2010, 06:44:47 AM »
I'm not having any issues with e-17. of course I stopped using itaskbar-ng awhile ago. (I am still getting blank email notifications) lol

glad the sites back up  ;D

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12514
Re: E17 beta 3 bug thread
« Reply #16 on: December 19, 2010, 06:48:31 AM »
I'm not having any issues with e-17. of course I stopped using itaskbar-ng awhile ago. (I am still getting blank email notifications) lol

glad the sites back up  ;D

There is still a routing issue that won't be resolved until Monday. A work around was put in place for the weekend. I don't know if that will solve your blank email notification though.

Thanks to everyone who donates. You keep the servers running.

Offline MtnMan

  • Sr. Member
  • ****
  • Posts: 258
  • Aged to perfection
Re: E17 beta 3 bug thread
« Reply #17 on: December 19, 2010, 07:17:49 AM »
My comment may not be relevant here and I will let you decide to give it the boot. 
I use suspend frequently with the command ¨pm-suspend¨ set to the standby button on my keyboard.  Sometimes when it wakes most of my screen is black except for a few gadgets and panel.  Mouse clicks do not have effect in the black area but if I open a window and close, the screen is then drawn in that area.  I can then get a menu click, restart (Enlightenment) and the world is right again.  This happens rarely (once in 10 to 15 sleep cycles) and I have not been able to make it happen.  With the beta 3 update it still happens.
I have used the same routine for sleep with KDE but never had the issue.
I worry that the person who thought up Muzak may be thinking up something else. - Lily Tomlin

Offline corazon

  • Full Member
  • ***
  • Posts: 133
Re: E17 beta 3 bug thread
« Reply #18 on: December 19, 2010, 06:57:31 PM »
Concerning this error,

(Did a synaptic system update, I have E17, with kde installed for opera and k3b,
and now at startup there is an error,

"Couldn't recognize the image file format for file
/usr/share/gdm/themes/PCLinuxOS-Obsidian-2/background.jpg)

 I powered off twice, once after reinstalling kde4, and then again after removing it. Oddly, after posting here last night, when I started
up this morning, I went to fetch some coffee, and came back to see the E17 desktop ready for action!  :o  So I logged out, and
logged back in, and the error shows up. I let it sit a few minutes to insure it was not a timing issue, then logged in at the
'standard greeter'. I then powered off, and rebooted, and again, the desktop loaded normally. The odd widget/icon/permissions
issues remain.

nvidia 6100 motherboard video
gtk-theme-name="Aurora"
gtk-icon-theme-name="Blackwood"
E17 theme 'Noche'
.dmrc: Session=23E17

also, dbus-launch nautilus  as user fails, and yields this terminal output:

** Message: Initializing gksu extension...
Initializing nautilus-image-converter extension
Initializing nautilus-gdu extension
sys:1: GtkWarning: Error loading theme icon 'edit-clear' for stock: Unrecognized image file format
sys:1: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
sys:1: GtkWarning: gtk_default_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: IA__gtk_style_render_icon: assertion `pixbuf != NULL' failed
sys:1: Warning: g_object_ref: assertion `G_IS_OBJECT (object)' failed
sys:1: GtkWarning: Error loading theme icon 'image-missing' for stock: Unrecognized image file format
sys:1: GtkWarning: Error loading theme icon 'edit-find' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'go-next' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'go-previous' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'go-up' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'process-stop' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'view-refresh' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'zoom-out' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'zoom-in' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
sys:1: GtkWarning: Error loading theme icon 'window-close' for stock: Unrecognized image file format

** (nautilus:10957): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed
**
Eel:ERROR:eel-wrap-table.c:496:wrap_table_get_num_fitting: assertion failed: (max_child_size > 0)
Aborted

but dbus-launch nautilus as root, starts fine, with this terminal output:

** Message: Initializing gksu extension...
Initializing nautilus-image-converter extension
Initializing nautilus-gdu extension

and when nautilus is closed, adds this

** (nautilus:22326): WARNING **: Unable to add monitor: Not supported
sys:1: GtkWarning: IA__gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed

Also, when closing any gnome-terminal, I get an error:

"Enlightenment was unable to run the application: gnome-terminal
The application failed to start"

Cheers

Offline corazon

  • Full Member
  • ***
  • Posts: 133
Re: E17 beta 3 bug thread
« Reply #19 on: December 19, 2010, 08:00:09 PM »
So, with all kde4 uninstalled, I used synaptic just now to install k3b, and the kde4 base it requires.
When I start k3b, these errors appear:

could not find mime type "application/octet-stream"

When that is closed:

Could not find mime types:
inode/directory
inode/blockdevice
inode/chardevice
inode/socket
inode/fifo
application/x-shellscript
application/x-executable
application/x-desktop

the terminal output:

K3bQProcess::QProcess(0x0)
K3bQProcess::QProcess(0x0)
k3b(10844)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory!
k3b(10844)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(10844)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(10844)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory!
QMetaObject::invokeMethod: No such method K3b::Application::loadCommandLineOptionsForNewInstance()
[username@localhost ~]$ k3b(10844)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/usr/share/mime/magic"
k3b(10844)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/home/username/.local/share/mime/magic"

At this point, k3b appears ready to work, but segfaults when choosing an action:

Executable: k3b PID: 13712 Signal: 11 (Segmentation fault)

and,

after closing k3b, the terminal output continues:

(<unknown>:10844): Gtk-WARNING **: Error loading theme icon 'window-close' for stock: Unrecognized image file format

(<unknown>:10844): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

** (<unknown>:10844): CRITICAL **: aurora_style_draw_render_icon: assertion `base_pixbuf != NULL' failed

(<unknown>:10844): Gtk-CRITICAL **: IA__gtk_style_render_icon: assertion `pixbuf != NULL' failed

(<unknown>:10844): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:10844): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:10844): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed
KCrash: Application 'k3b' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/username/.kde4/socket-localhost.localdomain/kdeinit4__0

Also, E17 segVs as synaptic operates, the operation completes, and choosing F1
to recover from the segV minimizes synaptic, and the desktop stays open. Synaptic still works when
maximised.

Most of these issues appeared after a full system update that included many kde4, and E17 updates.
I should have reported minor errors earlier on, and updated E17 separately, before updating kde.

Cheers

Offline corazon

  • Full Member
  • ***
  • Posts: 133
Re: E17 beta 3 bug thread
« Reply #20 on: December 20, 2010, 05:22:48 AM »
k3b ran fine as root...  ::)   go figure. Whatever is amiss, I'll use the new E17 iso it burned to reinstall, and hopefully
terminate the weird kabuki dance.
Cheers

Offline Agust

  • Hero Member
  • *****
  • Posts: 977
Re: E17 beta 3 bug thread
« Reply #21 on: December 20, 2010, 05:35:22 AM »
I do not understand, I have no problem with E17, only that with beta3 ItaskNG not work fine.
I work E17 very hard and I have no problem.
I use the Light version with Ecomorph and I'm just in heaven.  ;D
Just a comment.
Not all problems are the fault of Enlightenment.

Greetings and enjoy E17PCLinuxOS!!! is fantastic Sure!!!
Agust

PCLinuxOS e17 Club Member

Pclos user since 2005!

Offline smurfslover

  • Hero Member
  • *****
  • Posts: 811
Re: E17 beta 3 bug thread
« Reply #22 on: December 20, 2010, 09:31:20 AM »
k3b ran fine as root...  ::)   go figure. Whatever is amiss, I'll use the new E17 iso it burned to reinstall, and hopefully
terminate the weird kabuki dance.
Cheers

Probably broken config for your user, try removing
~/.kde4/share/config/k3brc and ~/.kde4/share/applications/k3b/ and try k3b again.
Registered Linux User 440970

Every windows machine has an un-patchable critical vulnerability... Its called "Power ON" switch.

Offline corazon

  • Full Member
  • ***
  • Posts: 133
Re: E17 beta 3 bug thread
« Reply #23 on: December 20, 2010, 10:55:57 PM »
k3b ran fine as root...  ::)   go figure. Whatever is amiss, I'll use the new E17 iso it burned to reinstall, and hopefully
terminate the weird kabuki dance.
Cheers

Probably broken config for your user, try removing
~/.kde4/share/config/k3brc and ~/.kde4/share/applications/k3b/ and try k3b again.
Hi, in this process, I already reinstalled the full kde4 in synaptic, no help, deleted the kde4 folder, then uninstalled all kde apps by synaptic, rebooted, and reinstalled, once full, once just k3b and dependencies, no help. Tried  many E17 themes, gtk themes, verified that file formats are read correctly by graphics apps, yada yada, so I pin the tail on the donkey, and guess that the latest kde, gnome, E17,and gtk dependencies and permissions are not properly set up after synaptic is done with them, to work well with each other, and its really not surprising, since they are separate projects, each reinventing their own wheels, which is part of the alluring nature of the beast.

I'll install the new E17 iso. Probably will work perfect. I back-up anything important in triplicate, off the main system, and its good practice to see what makes the OS tick.  8)
Cheers


Offline MtnMan

  • Sr. Member
  • ****
  • Posts: 258
  • Aged to perfection
Re: E17 beta 3 bug thread
« Reply #24 on: December 21, 2010, 08:02:55 AM »
My comment may not be relevant here and I will let you decide to give it the boot. 
I use suspend frequently with the command ¨pm-suspend¨ set to the standby button on my keyboard.  Sometimes when it wakes most of my screen is black except for a few gadgets and panel.  Mouse clicks do not have effect in the black area but if I open a window and close, the screen is then drawn in that area.  I can then get a menu click, restart (Enlightenment) and the world is right again.  This happens rarely (once in 10 to 15 sleep cycles) and I have not been able to make it happen.  With the beta 3 update it still happens.
I have used the same routine for sleep with KDE but never had the issue.
I just wanted to report back that the problem was between the keyboard and chair.  I was playing with effects a lot (especially the ¨ experimental ¨).  After login without ecomorph there has been no need to F5 the desktop.  BTW I am using the lite version and think it is fantastic.
I worry that the person who thought up Muzak may be thinking up something else. - Lily Tomlin

Offline smurfslover

  • Hero Member
  • *****
  • Posts: 811
Re: E17 beta 3 bug thread
« Reply #25 on: December 21, 2010, 09:54:47 AM »
BTW I am using the lite version and think it is fantastic.

Thanks ;)
Registered Linux User 440970

Every windows machine has an un-patchable critical vulnerability... Its called "Power ON" switch.

Offline gacurt

  • Jr. Member
  • **
  • Posts: 27
Re: E17 beta 3 bug thread
« Reply #26 on: December 22, 2010, 09:57:20 PM »
When changing desktops, an open item stays on the screen, if minimized it stays with the correct desktop. System started with lxde install, added E17 with task enlightenment. Lxde operates properly. I noticed this after installing ecomorph, don't know if it was occurring beforehand. Ecomorph and ecomp removed, no change. I will hold off removing and reinstalling e17 until I am sure there is nothing that should be checked / information submitted. Otherwise has been operating on two other pc's well, other than opera being very slow.
Reinstalled econfig, works properly now.
« Last Edit: December 31, 2010, 08:05:49 AM by gacurt »

Offline smurfslover

  • Hero Member
  • *****
  • Posts: 811
Re: E17 beta 3 bug thread
« Reply #27 on: December 22, 2010, 10:12:54 PM »
If you enable ecomorph you must disable the e17 composite and dropshadow modules.
Registered Linux User 440970

Every windows machine has an un-patchable critical vulnerability... Its called "Power ON" switch.

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12514
Re: E17 beta 3 bug thread
« Reply #28 on: December 26, 2010, 09:41:58 PM »
Enlightenment packages have been updated which fixes a system wide ordering issue. itask-ng drag and drop still funky but ordering through the menu settings work fine.

Thanks to everyone who donates. You keep the servers running.

Offline smurfslover

  • Hero Member
  • *****
  • Posts: 811
Re: E17 beta 3 bug thread
« Reply #29 on: December 26, 2010, 10:37:00 PM »
Enlightenment packages have been updated which fixes a system wide ordering issue. itask-ng drag and drop still funky but ordering through the menu settings work fine.

Thanks for the update, reordering works ok now all we need is working drag'n drop :)
Registered Linux User 440970

Every windows machine has an un-patchable critical vulnerability... Its called "Power ON" switch.