Public bug reported:
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970520
downgrading to libwolfssl24_4.3.0+dfsg-2 solves the crash
** Affects: wolfssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
With openssl 1.1.1f-1ubuntu1 Qvpn from Qnap works again, so this bug can
be closed IMHO.
Neverthertheless I would prefer companies/producers of VPN solutions fix
and update their signatures (shouldn't be a rocket-science).
In my company I stay with PiVPN (instead of QVNP) seems more secure,
faste
As a quick addition for the QVPN app on a Qnap NAS in our network I just
installed a Raspberry 3 with PiVpn (pivpn.io) configured for OpenVPN, as
I'm in doubt Qnap will release an updated QVpn just in Time ...
Works like a charm and installation is super easy. With at least one
connection it seems
Gratulations to Joseph Salisbury
the test kernel works like a charm
My Lenovo T520 boots rather quick without having haveged installed.
Thanks for this quick fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
According to this page
https://debianforum.de/forum/viewtopic.php?f=33&t=169585&hilit=entropie
This newly introduced fix in 4.15.0-24 is the cause
'random: fix crng_ready() test'
when it's reverted (like in debian 4.9.88-1+deb9u1) boot is fine again
'linux (4.9.88-1+deb9u1) stretch-security; u
Have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631
it seems the kernel update breaks gdm
** Bug watch added: Debian Bug tracker #897631
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As no trick mentioned here worked ...
I made a fresh install and updated everything except the kernel (which
remains at 4.15.0-20). And my Lenovo T 520 works again.
So indeed kernel 4.15.0-24 seems the culprit. No glue why booting to
previous installed kernels doesn't work either as soon 4.15.0-2
@ #12
No booting to previous kernels (4.15.0-23 or -20) doesn't solve the
problem, also removing 4.15.0-24 doesn't help here.
I'm in doubt it's a kernel problem.
If you do a little research you'll find that this issue (Started gnome
display manager. dispatcher service .. tem changes.pp link
Here too on my Thinkpad T520.
Happens also on a complete fresh install after applying latest updates
from today
Curiously my home-build computer (using also intel-graphics) works
without any problem ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
A first test with Ubuntu 18.04 and my Epson V 300 showed: Things remain
the same as with 17.10. Only after the steps described in post #76 my
scanner began to work.
Btw. the opinion of the sane developers I talked with is rather clear
and easy: those who broke things have to fix them.
--
You rec
And please don't omit the permissions problem which occurs IMHO with all
iscan, brscan4 and some smfb* based scanners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from li
As im in contact with Olaf Meeuwissen (Sane developer and former Epson
developer, responsible for iscan, imagescan, and now utsushi) ...
He told between the lines that he's quite sure that no manufacturer will
correct his packages.
--
You received this bug notification because you are a member
@ marcelpaulo
have a look at comment #94
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manage notifications about this
Try another USB -Port, (no USB 3 whenever possible), check USB cables,
check if the file 'iscan' is in 'etc/sane.d/dll.d/
content:
'epkowa'
edit '/etc/sane.d/dll.conf'
comment all entries by adding '#' in front of every line
add 'epkowa' (uncommented !)
edit '/etc/sane.d/epkowa.conf'
comment th
If
1)'ls /usr/lib/sane/*'
shows:
/usr/lib/sane/libsane-epkowa.la/usr/lib/sane/libsane-epkowa.so.1.0.15
/usr/lib/sane/libsane-epkowa.so.1
then a
2)'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane'
is the cure for your scanner hickups ...
If not, you first need to r
@ Ken Wright
looks okay so far
finally
output of
'ls /usr/lib/x86_64-linux-gnu/sane/libsane-epkowa*'
and
'ls /etc/udev/rules.d/*.rules'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
@ Ken Wright
You know this is not a helpdesk ?
open a terminal and paste
'apt list --installed |grep -e esci -e iscan -e libsane1'
this shows your installed Sane backends (libsane1) and your iscan
installion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Output(s) seem fine
have you installed
http://support.epson.net/linux/en/iscan.php?model=perfection-v370&version=1.0.1
ß
I guess so but for beeing sure ...
Also
sane-backends (1.0.27-1~experimental2ubuntu2.1) artful ?
I ask so much because in comment 21 the epson V-370 is told to be
working. S
@ Ken Wright
As starting point:
output of
'lsusb'
and
'sudo sane-find-scanner'
'scanimage -L'
please
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers
Congratulations, great work Luca. And big relief ...
So I summarize the workarounds as follows (no need to crawl through this
lengthy bug report):
I.Brother:
1. brscan, brscan2, brscan3
a) 'sudo ln -sfr /usr/lib64/libbr* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/lib64/sane/libsane-brothe
Hi Luca,
can you please remove /etc/udev/rules.d/60-brother-libsane-type1.rules
completly ?
and add instead /etc/udev/rules.d/79-udev-brother.rules (see attach)
Don't worry about the 0777 (as long you posess your computer ;-). We can
later try to reduce permissions (but 0666 makes no real differ
@Luca
Bingo
udevadm test /devices/pci:00/:00:1d.7/usb2/2-4'
shows:
'Invalid rule /etc/udev/rules.d/60-brother-libsane-type1.rules:17:
unknown key 'SYSFS{idVendor}'
So consequently your device is configured as printer-only:
RUN '/lib/udev/tlp-usb-udev %p' /lib/udev/rules.d/85-tlp.rules
Hi Luca,
In your diff.sane.txt I've found these two entries (problem seems
related to settings of c189:130) :
< openat(AT_FDCWD, "/run/udev/data/c189:130", O_RDONLY|O_CLOEXEC) = 33
< fstat(33, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0
< fstat(33, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0
I have no idea what 'more-magic' xsane uses, as simple magic of root
using scanimage isn't sufficient.
as your diff shows no success, only 'permission denied' the cause of the
failure can't be identified ...
maybe a
'export SANE_DEBUG_DLL=128'
As user
'strace xsane 2>strace.user.log'
As root
Sorry
As root also only (no -L)
'strace xsane 2>strace.root.log'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manage
@ luca
could you do the following ?
'export SANE_DEBUG_DLL=128'
As user
'strace scanimage -L 2>strace.user.log'
As root
'strace scanimage -L 2>strace.root.log'
Finally
'diff strace.user.log strace.root.log'
And show us the diff ?
--
You received this bug notification because you are a mem
@Matt_H
Sorry, I should have asked first: Are you on 32 or 64 bit ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manag
@Matt_H
Please install this plugin
https://download2.ebz.epson.net/iscan/plugin/gt-f720/deb/x64/iscan-
gt-f720-bundle-1.0.1.x64.deb.tar.gz
Then continue with #36
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Hi Luca can you try
/etc/udev/rules.d/99-local.rules
SUBSYSTEM!="usb_device", ACTION!="add", GOTO="_end"
# For BROTHER MFC-1910W
SYSFS{idVendor}=="04f9",
SYMLINK+="scanner-%k",OWNER="root",GROUP="scanner",MODE="0660"
LABEL="_end"
--
You received this bug notification because you are a member o
@luca
What did I tell you
How about a debugging session ;-)
Open your terminal and paste:
'export SANE_DEBUG_DLL=255'
then try sane-find-scanner (with/without sudo)
scanimage -L (with/without sudo)
Xsane (with/without sudo)
also as root
show us the results.
--
You received this
Dear Jeremy
But be assured that I know Sane since a very long time (have a look at
my sane frontend Tame/2 for OS/2, anybody remebers ? It was the first
and only OS/2 scanning application supporting USB thanks to Maeda
Haruyuki- a japanese developer). I remember debugging sessions with
Osaka (wher
Please use the workaround for Epson Iscan, Brother brscan,brscan2 and
brscan3 Scanners from here
https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1728012/comments/36
brscan4 no luck until now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
'I have written to Brother support'
Nothing will happen. As only Ubuntu 17.10 is affected, no other Ubuntu-
Release, no other Linux-Distribution (e.g. Arch-Linux uses libsane
1.0.27 and no extra pecularities are reported) .
Hopefully Ubuntu switches at least for 18.04 LTS back to use non-
experim
As I've found now the origin of '/etc/udev/rules.d/79-udev-epson.rules'
- it was installed by the epson-printer-utility for my Epson XP 540 - I
tried what happens when I switch to a more 'common' udev rule.
I tried (similiar to the rule for brother scanners provided by Hans):
ATTRS{idVendor}=="04
At the moment I see only two possibilities
Try vuescan https://www.hamrick.com/
or try Hans Schwimmbecks 'ugly' workaround
https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1707352/comments/35
Debian recently released libsane1 1.0.27-1~experimental3 (hope never
dies ;-)
Changelog
@luca.mg
Im sorry to hear that.
BTW. Are you on wayland or xorg. If wayland, have you tried with xorg ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers
@luca.mg
Are you aware of these informations ?
http://stepsilon.com/ubuntu/install-scanner-brother-dcp-7055-ubuntu
"The Brother Linux scanner driver works only with a superuser by
default, as noted on the brother solutions site.
If you want to allow normal users to also use the scanner, this is
I have no glue why Epson has chosen '0777', maybe it's because they
upload a firmware to their scanners ...
Actual summary:
1.Brother:
brscan4 no luck until now (btw. the installer already seems to respect
/usr/lib/x86_64-linux-gnu/sane)
brscan, brscan2, brscan3
a) 'sudo ln -sfr /usr/lib64/li
Dear Hans could you please test if a more generic solution like the one
provided by Epson would also work for local attached Brother Scanners ?
A possible Example:
# chmod device BROTHER group
ATTRS{manufacturer}=="BROTHER", DRIVERS=="usb", SUBSYSTEMS=="usb",
ATTRS{idVendor}=="04f9", ATTRS{idPro
In the meanwhile I had a look on different brscan drivers ...
Unfortunately brscan4 has a complete different structure (so at least
one real user is needed)
Summary is now:
1. Brother brscan, brscan2, brscan 3
a) 'sudo ln -sfr /usr/lib64/libbr* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/l
Thanks Mariusz. Can you please specify which files are in /usr/lib/sane
(just to make the command below more precise) ?
To summarize we have now the following workarounds (all 64-bit):
1. Brother brscan3
a) 'sudo ln -sfr /usr/lib64/libbrscandec* /usr/lib/x86_64-linux-gnu'
b) 'sudo ln -sfr /usr/l
@ Hans Schwimmbeck
Great, so we have a fix for brother brscan3 scanners too.
Ah yes, linking is definitely a better way than copying (you may forgive
me, my workaround was only a first try).
Now we only need to know if, brscan, brscan2 and brscan4 scanners can be fixed
too by linking directori
@Michael Barraclough
Is it a fresh install ?
If yes, I'm sorry I'm not familiar with Kubuntu
If no, please consider a fresh installation of Kubuntu 17.10 (too many
things have changed since 16.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
@Michael Barraclough
Are you on 32 bit ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for sane
To manage
I verified that my Epson V300 works with a fresh Ubuntu 17.10
installation by doing the following steps
1. Install libsane1 1.0.27-1~experimental2ubuntu2.1
If you don't want to enable the proposed repository the easiest way is
to download the files and install them from local
https://launchpad.n
A Test here showed:
without 79-udev-epson.rules in /etc/udev/rules.d
only 'sudo scanimage -L works'
with 79-udev-epson.rules in /etc/udev/rules.d
no root needed, a simple 'scanimage -L' is sufficient
maybe for the brscan scanners also only the udev rule is missing
try to add
# Brother scanne
Do you have really copied the content of /usr/lib64/sane/ to
/usr/lib/x86_64-linux-gnu/sane ?
Whats with 79-udev-epson.rules in /etc/udev/rules.d ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170735
Please try 'sudo scanimage -L'
if scanimage succeeds and finds the scanner check if you have a file
named 79-udev-epson.rules in /etc/udev/rules.d
If yes content:
If no it should have the following content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="us
X-Org or wayland doens't matter. My scanner works with both (verfied).
Do you have a file named 79-udev-epson.rules in /etc/udev/rules.d ?
Mine has the following content:
# chmod device EPSON group
# ACTION=="add", ATTRS{manufacturer}=="EPSON", DRIVERS=="usb",
SUBSYSTEMS=="usb", ATTRS{idVendor}
If you don't want to enable the proposed repository the easiest way is
to download the files and install them from local
https://launchpad.net/ubuntu/artful/+upload/16734103/+files/libsane1_1.0.27-1~experimental2ubuntu2.1_amd64.deb
https://launchpad.net/ubuntu/artful/+upload/16734103/+files/sane-
Are on x-org or wayland ? Can you try what happens if you switch to
X-org ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
T
Can you try it as root ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for sane
To manage notifications ab
Thats interesting. I don't need to be root to scan.
So whats different is the question ? I don't believe it's the different
plugin. Iscan is identical I suppose.
Just for completeness:
apt list --installed |grep -e esci -e iscan -e libsane -e sane-utils
WARNING: apt does not have a stable CLI
BRScan users can you try what happens when copy the files (libsane-
brother*) from /usr/lib64/sane/ to /usr/lib/x86_64-linux-gnu/sane.
Maybe the fix for brother scanners is as easy as the one for the epson
ones ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
BRScan users can you try what happens when you copy the files (libsane-
brother*) from /usr/lib64/sane/ to /usr/lib/x86_64-linux-gnu/sane.
Maybe the fix for brother scanners is as easy as the one for the epson
ones ...
--
You received this bug notification because you are a member of Ubuntu
Bugs
Just for the record
scanimage -L
device `epkowa:interpreter:003:007' is a Epson Perfection V300 flatbed scanner
device `imagescan:esci:networkscan://192.168.50.24:1865' is a Epson XP-540
Iscan, simple-scan, Xsane are working as expected.
--
You received this bug notification because you are a
Just for the record
scanimage -L
device `epkowa:interpreter:003:007' is a Epson Perfection V300 flatbed scanner
device `imagescan:esci:networkscan://192.168.50.24:1865' is a Epson XP-540
Iscan, simple-scan, Xsane are working as expected.
--
You received this bug notification because you are a
Today I managed to bring back my dead Epson V300 alive :-)
1. Install libsane1 1.0.27-1~experimental2ubuntu2.1
2. Install iscan-gt-f720-bundle-1.0.1.x64.deb.tar.gz
3. Copy (or move) the files from /usr/lib/sane (libsane-epkowa.la,
libsane-epkowa.so.1, libsane-epkowa.so.1.0.15 in my case) to
/usr
Today I managed to bring back my dead Epson V300 alive :-)
1. Install libsane1 1.0.27-1~experimental2ubuntu2.1
2. Install iscan-gt-f720-bundle-1.0.1.x64.deb.tar.gz
3. Copy (or move) the files from /usr/lib/sane (libsane-epkowa.la,
libsane-epkowa.so.1, libsane-epkowa.so.1.0.15 in my case) to
/usr
True Epson iscan .deb's can be installed now.
But nevertheless Epson scanners relying on iscan refuse to work (Epson
V300 in my case).
scanimage -L doesn't detect them, neither iscan, simple-scan or xsane.
This is less than half a fix.
BTW. in Ubuntu 17.04 the scanner worked with libsane 1.0.25
I can confirm that the Epson Perfection V300 is also affected
Using libsane1 1.0.27-1~experimental2ubuntu2.1 allows me to install the
drivers without conflicts.
But the scanner is not recognized. Neither by scanimage, simple-scan or
iscan
lsusb shows that the scanner is attached
lsusb
Bus 002 D
Scanning using a HP Officejet Pro 476 attached via network works with
libsane1 (proved with simple-scan)
scanimage -L
device `hpaio:/net/hp_officejet_pro_x476dw_mfp?ip=192.168.200.43&queue=false'
is a Hewlett-Packard hp_officejet_pro_x476dw_mfp all-in-one
--
You received this bug notification b
Many thanks to everybody who tries to fix this.
IMHO Things go wrong, but keep in mind 17.10 lives for 9 months, so no
real tragedy. Quite more important is that 18.04 LTS will work out-of-
box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In the meanwhile I discovered:
The Epson XP-540 Scanner-part is identical to the Standalone Epson V39
Scanner. For the V39 the plugin-gt-s650 comes in two flavours: As fully
functional imagescan plugin, which doesn't have libsane as dependency
and as non-functional iscan plugin which relys on libs
Epson XP-540 attached locally also works (tested with simple-scan)
scanimage -L
device `imagescan:esci:networkscan://192.168.50.24:1865' is a Epson XP-540
device
`imagescan:esci:usb:/sys/devices/pci:00/:00:14.0/usb3/3-8/3-8:1.0' is a
EPSON XP-540_Series
It uses the imagescan-plugin-gt-
My Epson XP-540 works.
Curiously with simple-scan and with xsane, but not with Imagescan provided by
Epson.
But thats another problem, image-scan scans but can't save the scanned image
... With Ubuntu 17.04 (using Sane 1.0.25) behaviour of imagescan was identical.
I already reported this months
Just for the record. When installing iscan and esci-interpreter-gt-f720
using 'sudo dpkg -i --force-depends', they get installed. But my Epson
V300 is not recognized.
When I start 'scanimage -L' only my Epson XP-540 networkscanner is
found, not my local attached Epson V300
scanimage -L
device `im
Im sorry but https://launchpad.net/ubuntu/+source/sane-
backends/1.0.27-1~experimental2ubuntu2 doesn't solve the problem.
This is what I get when I want to install my Epson V300 (sorry comments
are in german, but I'm sure you understand what goes wrong: libsane is
missing):
Hinweis: »libsane1« wi
You may want to know using Linux Libertine O 5.3 OTF or TTF doesn't
solve the distored printing. Also Libreoffice 3.6.0.2 (latest available
for Ubuntu 12.0) doesn't change anything for this bug (or abend, or
issue, as you like)
BTW. Abiword is not affected, documents from there using Linux Liberti
+ I'm interested in how you found this. Could you please explain how you
found that LO uses the graphite engine with the font Linux Libertine O?
It's pure intuition ;-). More serious : after I've found out that
Libertine G (with Graphite) works, Libertine O (without Graphite)
doesn't and LO includ
attached is example.odt (same as parkett.odt from #11 but without
privacy informations) which was used for printout.
** Attachment added: "example.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1018069/+attachment/3399096/+files/example.odt
--
You received this bug notificat
Attached is example.png a scan of two printouts (Laser Kyocera FS C5025
versus Ink HP officejet 8000) for direct comparing
** Attachment added: "example.png"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1018069/+attachment/3399095/+files/example.png
--
You received this bug no
>"+ Could you please take a picture of the offending printout and attach
to this report?"
Later this evening I provide a scanned printout. Sorry had to delete my
second example - too much private information ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment removed: "Parkett.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1018069/+attachment/3398722/+files/Parkett.odt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018069
I've tested now a document (see attach) with Ubuntu 12.04 and
libreoffice 3.5.4 and linux libertine O 5.1.3 with different printers
HP officejet 6100: OK (inkjet using PCL as language)
HP Officejet 8000 OK (inkjet using PCL as language)
Brother MFC 8640N FAIL (Laser using PS as language)
Kyocera F
I've tested a document now at home with both Ubuntu 12.04 and
libreoffice 3.5.4 (up-do-date with proposed), Ubuntu 12.10 and
libreoffice 3.6.2rc2 (up-to-date with proposed), printer was a HP
Officejet 6100.
In both cases printout using Libertine O (the non graphite version of
the font, installed b
Similar happens with libreoffice 3.6.2 rc2.
After quickly opening/closing/opening any Libreoffice application
/writer/calc/impress ... the menuebar is visible (in 3.6.1 it was not, so
situation gets better ;-) but it doens't work, also keyboard shortcut's don't
...
After closing an libreoffice
example document which shows distortion when printed attached
** Attachment added: "Urlaubsvertretung 4-2012.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1018069/+attachment/3337618/+files/Urlaubsvertretung%204-2012.odt
--
You received this bug notification because you are
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
Linux Libertine 5.1.3 and Libreoffice 3.5.x (I've tested 3.5.3 and
3.5.4) don't play well together. On screen everthing looks nice, but on
printout the distances between the letters are complet
Public bug reported:
Linux Libertine 5.1.3 and Libreoffice 3.5.x (I've tested 3.5.3 and
3.5.4) don't play well together. On screen everthing looks nice, but on
printout the distances between the letters are completly distored. The
printout is hard to read and looks ugly. I've seen this on all our
** Changed in: remmina (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972465
Title:
1.0.0 can't connect as administrator on w2k server
To manage n
This bug got finally solved by freerpd 1.0.1-1ubuntu2.1 and remmina
1.0.0-1ubuntu6.1
Thanks folks and anybody involved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972465
Title:
1.0.0 can't connec
As downgrading remmina 1.0.0-1ubuntu5 didn't help anything. I digged a
little deeper and found now what causes the refuse of a connection.
Whenever I successfully connect with freerpd as administrator on w2k
and then disconnect, freerpd doesn't disconnect properly. So the
connection stays open
And now, after applying remmina 1.0.0-1ubuntu6 from proposed the bug is
back :-(
Console output from remmina:
Remmina plugin VNC (type=Protokoll) registered.
Remmina plugin VNCI (type=Protokoll) registered.
Remmina plugin RDP (type=Protokoll) registered.
Remmina plugin RDPF (type=Datei) registere
It drives me nuts (not knowing what did the fix): after applying all
updates to precise until today, including those from proposed I can
connect as administrator - no installed fix was directly related to
remminna or freerpd .
My strong guess now is that it somehow had to do with the usage of a
*** This bug is a duplicate of bug 947358 ***
https://bugs.launchpad.net/bugs/947358
Public bug reported:
When I copy the contents of directory /usr/share/games/smc/worlds to
the newly generated directory 'campaings' in /usr/share/games/smc,
secret mario cronicle (smc) starts and works as ex
*** This bug is a duplicate of bug 947358 ***
https://bugs.launchpad.net/bugs/947358
Sorry reporting too fast, did't find bug 947358 earlier
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988465
T
I've tried now grdesktop (unfortunaetly gtk 2) which uses rdesktop for
rdp connections instead of freerpd. Everything fine there, so I suppose
it's a bug with freerpd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I've tried now grdesktop (unfortunaetly gtk 2) which uses rdesktop for
rdp connections instead of freerpd. Everything fine there, so I suppose
it's a bug with freerpd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Please tell me what informations are needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972463
Title:
changed windows color theme in 1.0.0
To manage notifications about this bug go to:
https://b
Tell me what informations are needed I'll try to collect all. Aeh yes I
wanted to to connect via RPD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972465
Title:
1.0.0 can't connect as administrator
** Description changed:
In remmina 1.0.0 connecting to a windows 2000 server via RPD the color
theme changes from default (previous remmina versions like in oneiric
- ocelot didn't the used the color scheme of the server). Maybe thats a
+ ocelot didn't, they used the color scheme of the serv
Public bug reported:
Maybe thats a 'security-feature' ... I'm unable to connect to a w2k
server as administrator with remmina 1.0.0. Connection closes
instantaniously.
Previous versions allowed such (and it was very handy, cause I'm lazy
and don't want to walk to the physical place of the server
Public bug reported:
The version number displayed should be 1.0.0
** Affects: remmina (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972460
Ti
Public bug reported:
In remmina 1.0.0 connecting to a windows 2000 server via RPD the color
theme changes from default (previous remmina versions like in oneiric
ocelot didn't the used the color scheme of the server). Maybe thats a
feature ... but then it should be declared somewhere ...
** Af
Can't understand the 'noise', as remmina has in it's sources already a
remmina.svg (see attach) even when scaling it 2000% (should be large
enough ;-) no pixelation at all.
Sorry I would have done it (the remmina.svg icon), but as it already
exists: why inventing the wheel again ... ?
** Attachme
I'm sorry to tell that I can't verify if kernel 3.0.9 solves the
regression or not.
As the stick showed the same errors after installing kernel 3.0.9 as
mainline build, I've done a crosscheck with Ubuntu 11.04 (where the
stick always worked). Even there no frontend attached.
Seems the stick decid
According to this log kernel 3.0.9 should contain a fix for the
regression
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873247
Title:
11
Fedora from Redhat is affected too, and has integrated fixes for testing
https://bugzilla.redhat.com/show_bug.cgi?id=733827
for the fixes see
http://comments.gmane.org/gmane.linux.drivers.video-input-
infrastructure/36393
** Bug watch added: Red Hat Bugzilla #733827
https://bugzilla.redhat.
As bugzilla.kernel.org continues to be unreachable I've sent a mail to
Patrick Boettcher at dibcom France who developed the dib0700 module.
Hopefully he's gone have a look on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
1 - 100 of 166 matches
Mail list logo
