[Bug 1958982] Re: rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3: rtl8821ce kernel module failed to build

2022-01-28 Thread neclepsio 
As a solution until this package is fixed, I installed
https://github.com/tomaspinho/rtl8821ce

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958982

Title:
  rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3: rtl8821ce kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1958982/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958982] Re: rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3: rtl8821ce kernel module failed to build

2022-01-28 Thread neclepsio 
This bug is particularly important, because this package does not
compile under kernel 5.13, and the default driver makes the entire
desktop crash. It seems to work with kernel 5.11, that's why I did not
notice the problem before.

When hung, the syslog (using default kernel driver I think) shows
continously the following line:

   rtw_8821ce :02:00.0: pci bus timeout, check dma status

I attach the make.log that shows compiling fails.

PS: I am writing this under kernel 5.11, and make.log is for 5.11,
because 5.13 is unusable for me. I get the same error with 5.13 but I am
not sure the compiling error are exactly the same.

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1958982/+attachment/5558009/+files/make.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958982

Title:
  rtl8821ce-dkms 5.5.2.1-0ubuntu4~20.04.3: rtl8821ce kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1958982/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1903886] [NEW] Wrong driver is chosen

2020-11-11 Thread neclepsio 
Public bug reported:

When adding an Epson Stylus SX235W (and possibly others) to Ubuntu 20.04
there is no error, but prints are heavily misaligned: colors are
vertically off of centimetres. Driver is epson-201108w and model is
recognized as "Epson Stylus Scan 2500 foomatic/stcolor"

If before installing the printer, you install the package printer-
driver-gutenprint, it will be recognized as "Epson Stylus
SX215+Gutenprint v5.3.3" and will work correctly.

As an additional note: in my previous Ubuntu 20.04 installation the
printer installed but had an error on printing and I installed the
package looking at CUPS logs. In a fresh installation, no error is
shown, the prints work but with totally misaligned colors. I think this
is a regression.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 11 17:47:53 2020
InstallationDate: Installed on 2020-10-27 (14 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lpstat: device for EPSON-Epson-Stylus-SX235: 
dnssd://Epson%20Stylus%20SX235._pdl-datastream._tcp.local/
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
 Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 004: ID 062a:4180 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 250 G7 Notebook PC
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON-Epson-Stylus-SX235.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON-Epson-Stylus-SX235.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=7b9265a8-c279-4d43-852e-8f18f0c7cb8e ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2020
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 86C1
dmi.board.vendor: HP
dmi.board.version: 89.35
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd07/31/2020:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 250 G7 Notebook PC
dmi.product.sku: 1F3N0EA#ABZ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903886

Title:
  Wrong driver is chosen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1903886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

2018-12-06 Thread neclepsio 
I can add an important information to this bug. If the laptop lid is
open, I can correctly manage three different monitors: the built-in one
and the two connected to the docking station. If the lid is closed, only
one of the monitors connected to the docking station is available.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802636

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

2018-11-22 Thread neclepsio 
** Tags added: kernel-da-key

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802636

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

2018-11-19 Thread neclepsio 
The last kernel does not fix, I added the tag but I cannot mark it as
confirmed.

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802636

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

2018-11-12 Thread neclepsio 
The problem also occurs in Wayland.

Ps: I tried to follow https://wiki.ubuntu.com/Bugs/FindRightPackage,
maybe it needs to be updated?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802636

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802636] [NEW] REGRESSION: only one displayport fron docking station is used at a time

2018-11-10 Thread neclepsio 
Public bug reported:

When my HP 840 G3 is connected to its docking station only one
DisplayPort is used at a time. If I disconnect the one in use, the other
is enabled. Only one display is detected. I'm using a fresh installation
of Ubuntu 18.10. Before, on 18.04, it worked.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 10 12:49:30 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079]
InstallationDate: Installed on 2018-11-01 (9 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp.
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 03f0:521d Hewlett-Packard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteBook 840 G3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=1203967d-3709-4fd4-966f-4c08b53203ce ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.16
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.76
dmi.chassis.asset.tag: 5CG7320Q91
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 840 G3
dmi.product.sku: L3C65AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic ubuntu

** Description changed:

- When my HP 840 G2 is connected to its docking station only one
+ When my HP 840 G3 is connected to its docking station only one
  DisplayPort is used at a time. If I disconnect the one in use, the other
  is enabled. Only one display is detected. I'm using a fresh installation
  of Ubuntu 18.10. Before, on 18.04, it worked.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 12:49:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
+  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
  InstallationDate: Installed on 2018-11-01 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp. 
-  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
-  Bus 001 Device 002: ID 03f0:521d Hewlett-Packard 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp.
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 002: ID 03f0:521d Hewlett-Packard
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-

[Bug 1565349] Re: No such file or directory while executing existing 64bit binary

2016-05-03 Thread neclepsio 
Workaround here https://bugs.launchpad.net/bugs/840998

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565349

Title:
  No such file or directory while executing existing 64bit binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565349] Re: No such file or directory while executing existing 64bit binary

2016-04-22 Thread neclepsio 
Here is a workaround: https://bugs.launchpad.net/bugs/840998

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565349

Title:
  No such file or directory while executing existing 64bit binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1566998] Re: Wrong time when using automatic setting

2016-04-22 Thread neclepsio 
I confirm it works now. Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1566998] Re: Wrong time when using automatic setting

2016-04-21 Thread neclepsio 
The file was missing. It now works. Thank you very much. But since it's
a common case, why it isn't handled correctly by default? I never had
problems with previous versions.

I could not test if ntp works because I have no network connection now.
Previously, the offset persisted the ntp update. I will let you know as
soon as possible.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1566998] Re: Wrong time when using automatic setting

2016-04-21 Thread neclepsio 
The file was missing. It now works. Thank you very much. But since it's a
common case, why it isn't handled correctly by default? I never had
problems with previous versions.
Il 20 apr 2016 11:35 PM, "Steve Langasek"  ha
scritto:

So you may want to check if you have this setting in /etc/adjtime (in
particular, the third line 'LOCAL')

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  I had to add UTC=yes to /etc/defaults/rcS because time was wrong when
  using automatic setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 19:29:00 2016
  InstallationDate: Installed on 2016-03-25 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rcS: 2016-04-06T19:22:59.183036

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1566998] Re: Wrong time when using automatic setting

2016-04-21 Thread neclepsio 
I could not test if ntp works because I have no network connection now.
Previously, the offset persisted the ntp update. I don't know if this
configuration will solve that too?
Il 21 apr 2016 10:19 AM, "Ignazio Di Napoli"  ha
scritto:

The file was missing. It now works. Thank you very much. But since it's a
common case, why it isn't handled correctly by default? I never had
problems with previous versions.
Il 20 apr 2016 11:35 PM, "Steve Langasek"  ha
scritto:

So you may want to check if you have this setting in /etc/adjtime (in
particular, the third line 'LOCAL')

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  I had to add UTC=yes to /etc/defaults/rcS because time was wrong when
  using automatic setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 19:29:00 2016
  InstallationDate: Installed on 2016-03-25 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rcS: 2016-04-06T19:22:59.183036

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 840998] Re: LSB-based executable (printer driver) aborts with "No such file or directory"

2016-04-20 Thread neclepsio 
*** This bug is a duplicate of bug 837745 ***
https://bugs.launchpad.net/bugs/837745

Thank you! It works!
Il 17 apr 2016 8:10 PM, "Paul Cunnell" <840...@bugs.launchpad.net> ha
scritto:

> *** This bug is a duplicate of bug 837745 ***
> https://bugs.launchpad.net/bugs/837745
>
> I has the same problem, on ubuntu 16.04 beta 2, and after much searching
> came across this report. I had installed lsb and the epson-inkjet-
> printer-201112w_1.0.0-1lsb3.2_amd64.deb from the Epson download site.
> Looking in /lib, there was just ld-linux.so.2, a symlink to -> i386
> -linux-gnu/ld-2.23.so.
>
> So mostly following the steps in comment #13, I created the following
> symlinks:
> cd /lib
> ln -sf ld-linux.so.2 /lib/ld-lsb.so.3
> ln -sf ld-linux.so.2 /lib/ld-lsb.so.2
> ln -sf ld-linux.so.2 /lib/ld-lsb.so.1
> ln -s /lib/x86_64-linux-gnu/ld-2.23.so /lib64/ld-lsb-x86-64.so.3
> ln -s /lib/x86_64-linux-gnu/ld-2.23.so /lib64/ld-lsb-x86-64.so.2
>
> ...and as if by magic the printer kicked into life! Not sure these are
> all necessary, but hey, a few extra symlinks never hurt ;-)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/840998
>
> Title:
>   LSB-based executable (printer driver) aborts with "No such file or
>   directory"
>
> Status in lsb package in Ubuntu:
>   Triaged
>
> Bug description:
>   I'm using an updated Ubuntu 11.10 beta 1 (amd64).
>
>   I have an Epson SX420W printer/scanner. I tried both the free and the
>   proprietary drivers that Jockey displayed, and I tried to connect the
>   printer with both USB and network.
>
>   In every case, the drivers are installed correctly and the printer looks
> ready, but each time I start a print job, I have the following notification
> : "Printer EPSON - Epson SW420W series may not be connected".
>   The strange thing is that the scanner works fine with SimpleScan.
>
>   In Ubuntu 11.04, with cups 1.4.6, I use the same proprietary driver
>   that is proposed in Oneiric, and everything works fine.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 11.10
>   Package: cups 1.5.0-5
>   ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
>   Uname: Linux 3.0.0-10-generic x86_64
>   NonfreeKernelModules: fglrx
>   Architecture: amd64
>   Date: Sun Sep  4 15:09:59 2011
>   InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
>   Lpstat: device for EPSON-Epson-Stylus-SX420W:
> dnssd://EPSON24AF57%20(Epson%20Stylus%20SX420W)._printer._tcp.local/
>   MachineType: TOSHIBA Satellite L550
>   Papersize: a4
>   PpdFiles: EPSON-Epson-Stylus-SX420W: Epson Stylus SX420W Series -
> epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=fr_FR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic
> root=UUID=f46a9835-9ee1-4b8e-bcfa-0824d96d2045 ro quiet splash vt.handoff=7
>   SourcePackage: cups
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/18/2009
>   dmi.bios.vendor: TOSHIBA
>   dmi.bios.version: V1.90
>   dmi.board.name: KTWAA
>   dmi.board.vendor: TOSHIBA
>   dmi.board.version: 1.00
>   dmi.chassis.asset.tag: *
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: TOSHIBA
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteL550:pvrPSLW8E-00Q00MFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
>   dmi.product.name: Satellite L550
>   dmi.product.version: PSLW8E-00Q00MFR
>   dmi.sys.vendor: TOSHIBA
>   mtime.conffile..etc.cups.cupsd.conf: 2011-09-04T14:02:26.093735
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/840998/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840998

Title:
  LSB-based executable (printer driver) aborts with "No such file or
  directory"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/840998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1566998] Re: Wrong time when using automatic setting

2016-04-17 Thread neclepsio 
I'm sure the time is off and ntp update does not solve. I thought to
have solved with UTC=yes but I just checked again and I was wrong. Maybe
something with time zone (Rome) or DST? On the pc I also have Windows 7.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565349] Re: No such file or directory while executing existing 64bit binary

2016-04-15 Thread neclepsio 
Is there any workaround? Is it possible that the new LTS will break
printing with epson printers in 10 days?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565349

Title:
  No such file or directory while executing existing 64bit binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1566998] [NEW] Wrong time when using automatic setting

2016-04-06 Thread neclepsio 
Public bug reported:

I had to add UTC=yes to /etc/defaults/rcS because time was wrong when
using automatic setting.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initscripts 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr  6 19:29:00 2016
InstallationDate: Installed on 2016-03-25 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
SourcePackage: sysvinit
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.rcS: 2016-04-06T19:22:59.183036

** Affects: sysvinit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566998

Title:
  Wrong time when using automatic setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1566998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 840998] Re: LSB-based executable (printer driver) aborts with "No such file or directory"

2016-04-04 Thread neclepsio 
*** This bug is a duplicate of bug 837745 ***
https://bugs.launchpad.net/bugs/837745

Adouzzy, which symlink? I tried to create as per comment #12 but it
still does not work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840998

Title:
  LSB-based executable (printer driver) aborts with "No such file or
  directory"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/840998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565349] Re: No such file or directory while executing existing 64bit binary

2016-04-03 Thread neclepsio 
I think this is the cause of https://bugs.launchpad.net/ubuntu/+source
/system-config-printer/+bug/1562789

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565349

Title:
  No such file or directory while executing existing 64bit binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1565349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1562789] Re: Epson printer won't print on 16.04

2016-04-03 Thread neclepsio 
I think this is a duplicate of https://bugs.launchpad.net/bugs/1565349

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562789

Title:
  Epson printer won't print on 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1562789/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565349] [NEW] No such file or directory while executing existing 64bit binary

2016-04-02 Thread neclepsio 
Public bug reported:

With this error, I can only find references for 32bit executables on
64bit system. This is not the case: the binary is 64bit, the interpreter
and every library seems in place.


ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
./epson-escpr-wrapper
bash: ./epson-escpr-wrapper: No such file or directory

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
ldd epson-escpr-wrapper
 linux-vdso.so.1 => (0x7ffdc3f7a000)
 libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 
(0x7f0ce852c000)
 libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7f0ce82ac000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0ce808e000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0ce7d85000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0ce79bb000)
 libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 
(0x7f0ce777)
 libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 
(0x7f0ce743f000)
 libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 
(0x7f0ce7233000)
 libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 
(0x7f0ce7021000)
 libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0ce6e07000)
 /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 (0x55ed62393000)
 libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f0ce6b35000)
 libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 
(0x7f0ce6905000)
 libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f0ce6701000)
 libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 
(0x7f0ce64f6000)
 libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 
(0x7f0ce629)
 libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x7f0ce605d000)
 libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f0ce5e4a000)
 libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f0ce5c13000)
 libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 
(0x7f0ce59e)
 libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f0ce576)
 libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f0ce5513000)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ce530f000)
 libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f0ce510b000)
 libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f0ce4eef000)
 libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7f0ce4ce7000)
 libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f0ce4c61000)
 libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7f0ce4a3f000)
 librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0ce4837000)
 liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0ce4614000)
 libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f0ce4333000)
 libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f0ce40c3000)
 libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f0ce3eae000)

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
file epson-escpr-wrapper
epson-escpr-wrapper: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-lsb-x86-64.so.3, for GNU/Linux 
2.6.15, BuildID[sha1]=558bd286d0e69cd3994a848c7c04d09a026cc2c4, stripped

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lsb-base 9.20160110
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr  2 22:16:04 2016
Dependencies:
 
InstallationDate: Installed on 2016-03-25 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
PackageArchitecture: all
SourcePackage: lsb
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lsb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565349

Title:
  No such file or directory while executing existing 64bit binary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1565349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1066529] Re: All jobs stopped, epson_inkjet_printer_filter failed

2016-04-02 Thread neclepsio 
There is a regression on 16.04. I don't think it's a duplicate of
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/840998: that was
caused by a broken symlink to  /lib/x86_64-linux-gnu/ld-2.23.so; this is
not the case.

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
./epson-escpr-wrapper 
bash: ./epson-escpr-wrapper: No such file or directory

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
ldd epson-escpr-wrapper 
linux-vdso.so.1 =>  (0x7ffdc3f7a000)
libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 
(0x7f0ce852c000)
libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 
(0x7f0ce82ac000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f0ce808e000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0ce7d85000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0ce79bb000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 
(0x7f0ce777)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 
(0x7f0ce743f000)
libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 
(0x7f0ce7233000)
libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 
(0x7f0ce7021000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0ce6e07000)
/lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 
(0x55ed62393000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 
(0x7f0ce6b35000)
libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 
(0x7f0ce6905000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 
(0x7f0ce6701000)
libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 
(0x7f0ce64f6000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 
(0x7f0ce629)
libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 
(0x7f0ce605d000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 
(0x7f0ce5e4a000)
libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 
(0x7f0ce5c13000)
libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 
(0x7f0ce59e)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7f0ce576)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7f0ce5513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ce530f000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 
(0x7f0ce510b000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f0ce4eef000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7f0ce4ce7000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f0ce4c61000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f0ce4a3f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0ce4837000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0ce4614000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f0ce4333000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f0ce40c3000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f0ce3eae000)

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
file epson-escpr-wrapper 
epson-escpr-wrapper: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-lsb-x86-64.so.3, for GNU/Linux 
2.6.15, BuildID[sha1]=558bd286d0e69cd3994a848c7c04d09a026cc2c4, stripped

ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ 
file /lib64/ld-linux-x86-64.so.2 
/lib64/ld-linux-x86-64.so.2: symbolic link to /lib/x86_64-linux-gnu/ld-2.23.so

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066529

Title:
  All jobs stopped, epson_inkjet_printer_filter failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1066529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1527590] Re: gedit unusable when menu can't be displayed

2016-04-02 Thread neclepsio 
Setting UBUNTU_MENUPROXY does not help. Also, if I understand correctly,
I'm not affected by #3: if menu is set to display in window titlebar, it
works for me (if not using sudo).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527590

Title:
  gedit unusable when menu can't be displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1527590] Re: gedit unusable when menu can't be displayed

2016-04-02 Thread neclepsio 
Same here. Fresh install, fully updated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527590

Title:
  gedit unusable when menu can't be displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 438136] Re: palimpsest bad sectors false positive

2009-10-29 Thread neclepsio 
I have the same problem with a Hitachi disk, counting 458798 bad
sectors. Every other parameter is ok.

-- 
palimpsest bad sectors false positive
https://bugs.launchpad.net/bugs/438136
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs