I’m not a TW user, but perhaps a rollback might be worth a shot here?
I’ll leave others to advise further as I’m in uncharted territory.
I exported user package by yast software manager did a clean install and import back user package config file, all packages are same now, but printer detected and working !!!
That’s good to know. Thanks for the update.
once again same problem, after update tumbleweed 20190428
cups error log :
W [30/Apr/2019:05:56:18 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:05:56:18 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:05:56:18 +0530] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
E [30/Apr/2019:05:56:18 +0530] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address.
E [30/Apr/2019:06:07:40 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:07:40 +0530] [cups-deviced] PID 3970 (cups-brf) stopped with status 1!
E [30/Apr/2019:06:08:32 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:08:32 +0530] [cups-deviced] PID 4043 (cups-brf) stopped with status 1!
W [30/Apr/2019:06:16:57 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:06:16:57 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:06:16:57 +0530] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
E [30/Apr/2019:06:16:57 +0530] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address.
E [30/Apr/2019:06:17:50 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:17:50 +0530] [cups-deviced] PID 1853 (cups-brf) stopped with status 1!
E [30/Apr/2019:06:18:45 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:18:45 +0530] [cups-deviced] PID 2064 (cups-brf) stopped with status 1!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-brf.drv\"!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv4.drv\"!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/cupsfilters.drv\"!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv3.drv\"!
E [30/Apr/2019:06:18:49 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-ubrl.drv\"!
E [30/Apr/2019:06:53:32 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:53:32 +0530] [cups-deviced] PID 4451 (cups-brf) stopped with status 1!
E [30/Apr/2019:06:53:39 +0530] [CGI] cups-brf must be called as root
E [30/Apr/2019:06:53:39 +0530] [cups-deviced] PID 4576 (cups-brf) stopped with status 1!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-brf.drv\"!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv4.drv\"!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/cupsfilters.drv\"!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv3.drv\"!
E [30/Apr/2019:06:53:43 +0530] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-ubrl.drv\"!
W [30/Apr/2019:06:55:03 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:06:55:03 +0530] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [30/Apr/2019:06:55:03 +0530] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Bug report required.
after 2-3 days searching … fixed the issue (trick)
https://bbs.archlinux.org/viewtopic.php?pid=1299897#p1299897
Well ‘udev-configure-printer’ supplies the udev rule for USB-connected printers, but for whatever reason this rule is apparently not being matched. FWIW, it looks like this
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="systemd", ENV{SYSTEMD_WANTS}="configure-printer@usb-$env{BUSNUM}-$env{DEVNUM}.service"
# Low-level USB device remove trigger
ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
Usually, explicit ‘lp’ group assignment for printers is not needed as systemd takes care of user access dynamically…
systemd will dynamically create device units for all kernel devices that are marked with the “systemd” udev tag (by default all block and network devices, and a few others). This may be used to define dependencies between devices and other units. To tag a udev device, use “TAG+=“systemd”” in the udev rules file, see udev(7) for details.
https://www.freedesktop.org/software/systemd/man/systemd.device.html
Anyway, I guess the pragmatic fix is the device-specific udev rule that you’ve now applied. 
Even though I don’t own Epson hardware, I decided to download and install the Epson Linux driver package (epson-printer-utility-1.0.2-1lsb3.2.x86_64) and then checked the supplied udev rule (/etc/udev/rules.d/79-udev-epson.rules )…
# chmod device EPSON group # ACTION=="add", ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666" ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"
Only the second entry is active of course, and no group explicitly assigned, only r/w access to the device node for all users. So, I’m not sure why you encountered problems with printing as such.
As I tested 2-3 times, with fresh install also, driver works on first install, and after 2-3 reboot didnt work, (I am using root only account on my machine), though The fix is working fine till now… as its a multifunctional printer, printing and scanning both working fine with driver (epson-inkjet-printer-escpr Ver 1.6.35-1.1