[Bug 1975391] Re: Subiquity crashes if the hd contains a previous Proxmox PVE install

2022-05-25 Thread Typhoe
Ok, thank you.

If I encounter the error again or manage to reproduce it, I'll post the
logs here then!

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

Title:
  Subiquity crashes if the hd contains a previous Proxmox PVE install

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


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

[Bug 1975391] Re: Subiquity crashes if the hd contains a previous Proxmox PVE install

2022-05-22 Thread Typhoe
Hum, sorry was not using an usb stick but directly the iso mounted as a
virtual DVD (IODD 2541).

I sent the crash logs to canonical (3 or 5 times) when subiquity asked for 
that, but don't know where they ended if you ask for them.
I didn't know "snap", and as the crash log was not mentioning anything, I first 
tried to see the system logs and see if I could update something and relaunch 
the installer.
snap refresh subiquity inded updated the installer, but it was still crashing...


If needed, I can try to reproduced the crashes tomorrow on another server, and 
see if I can get logs.
If I don't use a usb stick, are the crash logs available somewhere? The network 
is working and I should be able to scp them to another server.
Thanks

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

Title:
  Subiquity crashes if the hd contains a previous Proxmox PVE install

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


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

[Bug 1975391] [NEW] Subiquity crashes if the hd contains a previous Proxmox PVE install

2022-05-21 Thread Typhoe
Public bug reported:

I tried to install ubuntu server 22.04 on an Intel NUC8 server.
The main SSD still contained a previous Proxmox PVE v7 install (boot fat32+LVM, 
default proxmox install settings).
Each time subiquity would crash
Resolved the problem by removing every partitions on the SSD and rebooting

** Affects: subiquity (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/1975391

Title:
  Subiquity crashes if the hd contains a previous Proxmox PVE install

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


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

[Bug 1559692] Re: server image has no keyboard, desktop image works

2016-03-26 Thread Typhoe
Hi,

do you know when the fix committed will be in the daily iso?

I'm also affected by this problem. 
I try to install xenial (server and netboot iso) on an Intel Nuc (keyboard used 
is a logitech K400 wireless) and the keyboard stops working after the grub 
screen. Choosing the language is not possible.

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/1559692

Title:
  server image has no keyboard, desktop image works

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

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


[Bug 1296315] Re: 17e9:ff03 Displaylink and ASUS MB168B+ not working

2015-08-16 Thread Typhoe
few commands output:

ubuntu@ubuntu:~/Downloads/DisplayLink-Ubuntu-1.0.68$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080  60.0*+   60.0 40.0  
   1680x1050  60.0  
   1400x1050  60.0  
   1280x1024  59.9  
   1280x960   59.9  
   1152x864   60.0  
   1024x768   59.9  
   800x60059.9  
   640x48059.4  
   720x40059.6  
   640x40060.0  
   640x35059.8  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-1-0 connected 1920x1080+1920+0 344mm x 194mm
   1920x1080  60.0*+
   1280x1024  75.0  
   1024x768   75.1 70.1 60.0  
   800x60072.2 75.0 60.3  
   640x48075.0 72.8 60.0  

ubuntu@ubuntu:~/Downloads/DisplayLink-Ubuntu-1.0.68$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 1 name:nouveau
Provider 1: id: 0x310 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated 
providers: 1 name:modesetting

ubuntu@ubuntu:~/Downloads/DisplayLink-Ubuntu-1.0.68$ ls -l /dev/fb*
crw-rw 1 root video 29, 0 Aug 16 18:29 /dev/fb0
crw-rw 1 root video 29, 1 Aug 16 18:35 /dev/fb1

ubuntu@ubuntu:~/Downloads/DisplayLink-Ubuntu-1.0.68$ uname -a
Linux ubuntu 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ubuntu:~/Downloads/DisplayLink-Ubuntu-1.0.68$ lsb_release -d
Description:Ubuntu 15.04

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

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: 17e9:ff03 Displaylink and ASUS MB168B+ not working

2015-08-16 Thread Typhoe
Yes, just now.

I used the 15.04 x64 live-usb (I'm still running Arch Linux now).

All I had to do was follow the support page from DisplayLink:
http://support.displaylink.com/knowledgebase/articles/615714#ubuntu

sudo apt-get -y install dmks
wget -c 
http://downloads.displaylink.com/publicsoftware/DisplayLink-Ubuntu-1.0.68.zip
unzip DisplayLink-Ubuntu-1.0.68.zip
cd DisplayLink-Ubuntu-1.0.68
chmod +x displaylink-driver-1.0.68.run
sudo ./displaylink-driver-1.0.68.run

Output:
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.0.68  100%  
DisplayLink Linux Software 1.0.68 install script called: install
Distribution discovered: Ubuntu 15.04
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
Starting DLM systemd service

Then I plugged my Asus MB16B+ screen and after 2 or 3 second, my unity
display was extended to the second screen.

tail -f /var/log/syslog 
Aug 16 18:35:05 ubuntu systemd[1]: Starting DisplayLink Manager Service...
Aug 16 18:35:05 ubuntu kernel: [  364.262772] evdi: module verification failed: 
signature and/or  required key missing - tainting kernel
Aug 16 18:35:05 ubuntu kernel: [  364.264440] [ ] evdi_init Initialising 
logging on level 5
Aug 16 18:35:05 ubuntu systemd[1]: Started DisplayLink Manager Service.

dmesg
[  364.264440] [ ] evdi_init Initialising logging on level 5
[  383.349574] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
[  383.366326] usb 2-1: New USB device found, idVendor=17e9, idProduct=ff03
[  383.366333] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  383.366336] usb 2-1: Product: MB168B+
[  383.366339] usb 2-1: Manufacturer: DisplayLink
[  383.366342] usb 2-1: SerialNumber: DALMTF151588
[  383.37] usb 2-1: usbfs: process 6432 (DisplayLinkMana) did not claim 
interface 1 before use
[  391.596100] usb 2-1: USB disconnect, device number 5
[  392.563551] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[  392.580295] usb 2-1: New USB device found, idVendor=17e9, idProduct=ff03
[  392.580302] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  392.580305] usb 2-1: Product: MB168B+
[  392.580308] usb 2-1: Manufacturer: DisplayLink
[  392.580311] usb 2-1: SerialNumber: DALMTF151588
[  399.332641] [D] add_store  increasing device count to 1
[  399.332985] [D] evdi_crtc_init drm_crtc_init: 0
[  399.332992] [D] evdi_encoder_init drm_encoder_init: 0
[  399.333079] [D] evdi_detect Painter is disconnected
[  399.333085] evdi evdi.0: No connectors reported connected with modes
[  399.333090] [drm] Cannot find any crtc or sizes - going 1024x768
[  399.334501] evdi evdi.0: fb1: evdidrmfb frame buffer device
[  399.334507] [drm] evdi: evdi_stats_init
[  399.334520] [drm] Initialized evdi 1.0.68 20150717 on minor 1
[  399.542743] [W] evdi_painter_disconnect (dev=0) An unknown connection to 
8803d8896a00 tries to close us - ignoring
[  399.543134] [W] evdi_painter_disconnect (dev=0) An unknown connection to 
8803d8896a00 tries to close us - ignoring
[  399.565565] [D] evdi_detect Painter is disconnected
[  399.565569] [D] evdi_detect Painter is disconnected
[  399.565594] [D] evdi_detect Painter is disconnected
[  399.565596] [D] evdi_detect Painter is disconnected
[  399.565937] [D] evdi_painter_crtc_state_notify (dev=0) Notifying crtc state: 0
[  399.565942] [D] evdi_painter_crtc_state_notify (dev=0) Notifying crtc state: 0
[  399.616364] [W] evdi_painter_disconnect (dev=0) An unknown connection to 
8803f8356200 tries to close us - ignoring
[  399.623422] [D] evdi_painter_connect (dev=1) Connected with 8803f8356200
[  399.623428] [D] evdi_painter_connect (dev=1) Edid (3 bytes): 00 ff ff
[  399.623432] [D] evdi_detect (dev=1) Painter is connected
[  399.778573] [D] evdi_detect (dev=1) Painter is connected
[  399.778578] [D] evdi_painter_get_edid (dev=1) 00 ff ff
[  400.309430] [D] evdi_painter_mode_changed_notify (dev=1) Notifying mode 
changed: 1920x1080@60; bpp 32; pixel format 875713112
[  400.309463] [D] evdi_painter_crtc_state_notify (dev=1) Notifying crtc state: 
1

So everything seems quite good!

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

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: 17e9:ff03 Displaylink and ASUS MB168B+ not working

2015-08-16 Thread Typhoe
And by the way the "Displays" menu from Ubunty settings let me change
the second screen (named Ancor Communication Inc 15") position easily.

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

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: 17e9:ff03 Displaylink and ASUS MB168B+ not working

2015-08-09 Thread Typhoe
Displaylink released a driver in userland for ubuntu:

http://www.displaylink.com/downloads/ubuntu.php

This bug should be closed.

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

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: 17e9:ff03 Displaylink and ASUS MB168B+ not working

2015-02-15 Thread Typhoe
Hi,

it will have to wait for now as I'm not currently running ubuntu but
archlinux and would need to switch my HD before doing any other testing
than involving LiveCD/LiveUsb tests.

But so far, it doesn't seem to be any solution to this problem.

You can read a little about people complaining in this thread on DisplayLink 
forum:
http://displaylink.org/forum/showthread.php?s=be23744c6ca4e5f83770b81f98a9dc05&t=1748&page=16

Regards.

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

Title:
  17e9:ff03 Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2015-02-15 Thread Typhoe
Hi,

just tried the latest nightly of ubuntu (2015/02/15 iso)
lsb_release -d
Description:Ubuntu Vivid Vervet (development branch)

Still no change... The monitor is detected when plugged in (appears in
dmesg) but it is not recognized by the system and thus, can't be use...

Status of the problem is still unchanged so far...

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ubuntu:~$ dmesg
[  167.366484] usb 2-3: new SuperSpeed USB device number 6 using xhci_hcd
[  167.383178] usb 2-3: New USB device found, idVendor=17e9, idProduct=ff03
[  167.383196] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  167.383199] usb 2-3: Product: MB168B+
[  167.383202] usb 2-3: Manufacturer: DisplayLink
[  167.383204] usb 2-3: SerialNumber: DALMTF151588

root@ubuntu:/home/ubuntu# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080  60.0*+   60.0 40.0  
[...]
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

root@ubuntu:/home/ubuntu# xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau

root@ubuntu:/home/ubuntu# ls -l /dev/fb*
crw-rw 1 root video 29, 0 Feb 15 21:04 /dev/fb0

root@ubuntu:/home/ubuntu# dpkg -l | grep "^ii *xserver-xorg-video-modesetting"
ii  xserver-xorg-video-modesetting   0.9.0-1build1  
amd64X.Org X server -- Generic modesetting driver

root@ubuntu:/home/ubuntu# grep udl /etc/modprobe.d/blacklist-framebuffer.conf 
blacklist udlfb



** Changed in: xorg (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-04-04 Thread Typhoe
Hi,

I don't have any xorg.conf file in /etc/ and its sub dirs.

So far, I didn't manage to get any positive result...

Regards.

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11

2014-03-24 Thread Typhoe
Hi,

thank you Nikolaus, I tried a mainline kernel without any more
success...

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296315/comments/3

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

Title:
  17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195
  fails with EAGAIN after upgrade from 3.11.0-031100  to 3.11.0-11

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

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


[Bug 1296315] Xrandr.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040639/+files/Xrandr.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] UdevDb.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040627/+files/UdevDb.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] xdpyinfo.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040640/+files/xdpyinfo.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] xserver.devices.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040641/+files/xserver.devices.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] UdevLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040632/+files/UdevLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcInterrupts.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040625/+files/ProcInterrupts.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] XorgLogOld.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040638/+files/XorgLogOld.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] xserver.outputs.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xserver.outputs.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040642/+files/xserver.outputs.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcModules.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040626/+files/ProcModules.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] XorgLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040637/+files/XorgLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] DpkgLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040620/+files/DpkgLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Lspci.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040622/+files/Lspci.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] XorgLogOld.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040608/+files/XorgLogOld.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] XorgLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040607/+files/XorgLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] BootLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040617/+files/BootLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Lsusb.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040623/+files/Lsusb.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcCpuinfo.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040624/+files/ProcCpuinfo.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] DpkgLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040597/+files/DpkgLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] BootDmesg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040616/+files/BootDmesg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] UdevDb.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040605/+files/UdevDb.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] xserver.outputs.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xserver.outputs.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040612/+files/xserver.outputs.txt

** Description changed:

  Hi,
  
  I'm trying to use an USB3 external monitor Asus MB168B+ with displaylink
  technology.
  
  The monitor is detected by the kernel upon plug, but no driver seems to
  be loaded...
  
  My notebook is an ASUS G75VW
  sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
  G75VW.223
  01/07/2013
  
  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  
  apt-cache policy xorg
  xorg:
Installé : 1:7.7+1ubuntu8
Candidat : 1:7.7+1ubuntu8
   Table de version :
   *** 1:7.7+1ubuntu8 0
  500 http://ubuntu-archive.mirrors.free.org/ubuntu/ trusty/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  uname -a
  Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  
  Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB 
device number 6 using xhci_hcd
  Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
  Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+
  Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: 
DisplayLink
  Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: 
DALMTF151588
  Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-3"
  Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device
  
  xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
 1920x1080 60.0*+ 60.0 40.0
  <...>
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  
  xrandr --listproviders
  Providers: number : 1
  Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau
  
  ls -l /dev/fb*
  crw-rw 1 root video 29, 0 mars 23 12:34 /dev/fb0
  
  regards
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Mar 23 16:48:28 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF114M [GeForce GTX 670M] [10de:1213] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:2119]
  InstallationDate: Installed on 2014-03-21 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  MachineType: ASUSTeK COMPUTER INC. G75VW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed 
root=UUID=696d83ec-abd2-47e6-bf30-ce6bd4eb1514 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G75VW.223
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G75VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G75VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  --- 
  ApportVersion: 2.13.3

[Bug 1296315] xserver.devices.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040611/+files/xserver.devices.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] UdevLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040606/+files/UdevLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] HookError_source_xorg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "HookError_source_xorg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040598/+files/HookError_source_xorg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] HookError_source_xorg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "HookError_source_xorg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040621/+files/HookError_source_xorg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] BootLog.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040594/+files/BootLog.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Dependencies.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040596/+files/Dependencies.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcCpuinfo.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040602/+files/ProcCpuinfo.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] xdpyinfo.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040610/+files/xdpyinfo.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcModules.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040604/+files/ProcModules.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] CurrentDmesg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040618/+files/CurrentDmesg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Lspci.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040599/+files/Lspci.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] ProcInterrupts.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040603/+files/ProcInterrupts.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Dependencies.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040619/+files/Dependencies.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Xrandr.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040609/+files/Xrandr.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Lsusb.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1296315/+attachment/4040600/+files/Lsusb.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] CurrentDmesg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040595/+files/CurrentDmesg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] BootDmesg.txt

2014-03-24 Thread Typhoe
apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1296315/+attachment/4040593/+files/BootDmesg.txt

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

Title:
  Displaylink and ASUS MB168B+ not working

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

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


[Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-24 Thread Typhoe
Additional tests:

udlfb is blacklisted by default in trusty:
 grep udl /etc/modprobe.d/blacklist-framebuffer.conf 
blacklist udlfb

Generic modesetting driver is also present by default:
dpkg -l | grep "^ii *xserver-xorg-video-modesetting"
ii  xserver-xorg-video-modesetting  0.8.1-1build1   
   amd64X.Org X server -- Generic modesetting driver

After reading the Kernel/MainlineBuilds page, I tried a mainline kernel
https://wiki.ubuntu.com/Kernel/MainlineBuilds

I didn't found my kernel version on the mapping page (Trusty not indicated)
http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html

uname -a
Linux g75vw 3.13.0-19-generic #39-Ubuntu SMP Fri Mar 21 14:18:44 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

So I tried the kernel v3.13.7 as it seems the last of my version 
(configs-based-on-Ubuntu-3.13.0-19.40.patch)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.7-trusty/ 
linux-headers-3.13.7-031307_3.13.7-031307.201403240156_all.deb
linux-headers-3.13.7-031307-generic_3.13.7-031307.201403240156_amd64.deb
linux-image-3.13.7-031307-generic_3.13.7-031307.201403240156_amd64.deb
(no linux-image-extra deb as it is mainline?)

After a dpkg -i *.deb and a reboot, I still don't get any progress...
(manually modprobe udl, and trying to unplug/plug again the monitor)

uname -a
Linux g75vw 3.13.7-031307-generic #201403240156 SMP Mon Mar 24 05:57:41 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

Mar 24 11:39:11 g75vw kernel: [   80.303538] usbcore: registered new interface 
driver udl
Mar 24 11:39:39 g75vw kernel: [  107.757943] usb 4-3: USB disconnect, device 
number 3
Mar 24 11:39:48 g75vw kernel: [  116.561490] usb 4-3: new SuperSpeed USB device 
number 6 using xhci_hcd
Mar 24 11:39:48 g75vw mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-3"
Mar 24 11:39:48 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device
Mar 24 11:39:48 g75vw kernel: [  116.577674] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
Mar 24 11:39:48 g75vw kernel: [  116.577680] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Mar 24 11:39:48 g75vw kernel: [  116.577683] usb 4-3: Product: MB168B+
Mar 24 11:39:48 g75vw kernel: [  116.577685] usb 4-3: Manufacturer: DisplayLink
Mar 24 11:39:48 g75vw kernel: [  116.577688] usb 4-3: SerialNumber: DALMTF151588


** Tags added: apport-collected reproducible single-occurrence

** Description changed:

  Hi,
  
  I'm trying to use an USB3 external monitor Asus MB168B+ with displaylink
  technology.
  
  The monitor is detected by the kernel upon plug, but no driver seems to
  be loaded...
  
  My notebook is an ASUS G75VW
  sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
  G75VW.223
  01/07/2013
  
  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  
  apt-cache policy xorg
  xorg:
Installé : 1:7.7+1ubuntu8
Candidat : 1:7.7+1ubuntu8
   Table de version :
   *** 1:7.7+1ubuntu8 0
  500 http://ubuntu-archive.mirrors.free.org/ubuntu/ trusty/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  uname -a
  Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  
  Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB 
device number 6 using xhci_hcd
  Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
  Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+
  Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: 
DisplayLink
  Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: 
DALMTF151588
  Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-3"
  Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device
  
  xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
 1920x1080 60.0*+ 60.0 40.0
  <...>
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  
  xrandr --listproviders
  Providers: number : 1
  Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau
  
  ls -l /dev/fb*
  crw-rw 1 root video 29, 0 mars 23 12:34 /dev/fb0
  
  regards
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options

[Bug 1296315] Re: Displaylink and ASUS MB168B+ not working

2014-03-23 Thread Typhoe
sudo lsusb -d17e9:ff03 -vvv

Bus 004 Device 006: ID 17e9:ff03 DisplayLink 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize0 9
  idVendor   0x17e9 DisplayLink
  idProduct  0xff03 
  bcdDevice1.70
  iManufacturer   1 DisplayLink
  iProduct2 MB168B+
  iSerial 3 DALMTF151588
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  116
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  126mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   4
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0 
  bInterfaceProtocol  3 
  iInterface  0 
  ** UNRECOGNIZED:  0c 5f 01 00 0a 00 04 04 01 00 04 00
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08  EP 8 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   5
bMaxBurst   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass   254 Application Specific Interface
  bInterfaceSubClass  1 Device Firmware Update
  bInterfaceProtocol  1 
  iInterface  0 
  Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType33
bmAttributes1
  Will Not Detach
  Manifestation Intolerant
  Upload Unsupported
  Download Supported
wDetachTimeout200 milliseconds
wTransferSize1024 bytes
bcdDFUVersion   1.01
  ** UNRECOGNIZED:  10 40 08 06 0c 08 02 09 46 66 6c 79 4d 6f 6e 69
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15
  wTotalLength   42
  bNumDeviceCaps  3
  USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType16
bDevCapabilityType  2
bmAttributes   0x0002
  Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
bLength10
bDescriptorType16
bDevCapabilityType  3
bmAttributes 0x00
wSpeedsSupported   0x000e
  Device can operate at Full Speed (12Mbps)
  Device can operate at High Speed (480Mbps)
  Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport   2
  Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat  10 micro seconds
bU2DevExitLat 366 micro seconds
  Container ID Device Capability:
bLength20
bDescriptorType16
bDevCapabilityType  4
bReserved   0
ContainerID {30a29107-ae36-1349-6d97-f02a0eda5f4a}
Device Status: 0x000c
  (Bus Powered)
  U1 Enabled
  U2 Enabled

-- 
You received this bug notific

[Bug 1296315] [NEW] Displaylink and ASUS MB168B+ not working

2014-03-23 Thread Typhoe
Public bug reported:

Hi,

I'm trying to use an USB3 external monitor Asus MB168B+ with displaylink
technology.

The monitor is detected by the kernel upon plug, but no driver seems to
be loaded...

My notebook is an ASUS G75VW
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
G75VW.223
01/07/2013

lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04

apt-cache policy xorg
xorg:
  Installé : 1:7.7+1ubuntu8
  Candidat : 1:7.7+1ubuntu8
 Table de version :
 *** 1:7.7+1ubuntu8 0
500 http://ubuntu-archive.mirrors.free.org/ubuntu/ trusty/main amd64 
Packages
100 /var/lib/dpkg/status

uname -a
Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB device 
number 6 using xhci_hcd
Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+
Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: DisplayLink
Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: DALMTF151588
Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-3"
Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device

xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080 60.0*+ 60.0 40.0
<...>
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau

ls -l /dev/fb*
crw-rw 1 root video 29, 0 mars 23 12:34 /dev/fb0

regards

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Mar 23 16:48:28 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF114M [GeForce GTX 670M] [10de:1213] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:2119]
InstallationDate: Installed on 2014-03-21 (1 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
MachineType: ASUSTeK COMPUTER INC. G75VW
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed 
root=UUID=696d83ec-abd2-47e6-bf30-ce6bd4eb1514 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  Displaylink and ASUS MB168B+ not working

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

[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11

2014-03-23 Thread Typhoe
Hi,

to answer Matthew Carpenter, I own an ASUS MB168B+ and no, it isn't
working in the latest 14.04 releases...

I'm still in the process of reading all I can find about this problem,
but so far, as everyone, I can't find any clear instructions about "how
to make it simply works"...

My notebook is an ASUS G75VW
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
G75VW.223
01/07/2013

uname -a
Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB device 
number 6 using xhci_hcd
Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, 
idVendor=17e9, idProduct=ff03
Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+
Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: DisplayLink
Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: DALMTF151588
Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-3"
Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device

xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 382mm x 215mm
   1920x1080  60.0*+   60.0 40.0  
<...>
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated 
providers: 0 name:nouveau

ls -l /dev/fb*
crw-rw 1 root video 29, 0 mars  23 12:34 /dev/fb0

I'll add an apport report from my notebook if it can help...

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

Title:
  17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195
  fails with EAGAIN after upgrade from 3.11.0-031100  to 3.11.0-11

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

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


[Bug 1155997] [NEW] Network transferts crash with SW-IOMMU space messages

2013-03-16 Thread Typhoe
Public bug reported:

Hi,

when transferring around more than 1Go of data using the ethernet controller 
(04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet 
(rev c0)) with driver atl1c , my syslog gets full of messages "DMA: out of 
SW-IOMMU space for 4096 bytes at device 04:00.0" and my ethernet connection 
stops working.
To reproduce this problem, I simply copy a few files from my internal SSD to my 
NAS.

The byte size of the messages varies if I then try to access internet
with my browser or any other network oriented application (smaller
packets?)...

sudo lspci -s 04:00.0 -vv
04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev 
c0)
Subsystem: ASUSTeK Computer Inc. Device 1487
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status

Regards.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Sat Mar 16 17:40:32 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1853x404+65+24'"
InstallationDate: Installed on 2013-02-24 (19 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130224)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
XsessionErrors:
 (nautilus:1884): GnomeDesktop-WARNING **: Unable to create loader for mime 
type video/x-matroska: Format d'image non reconnu
 (nautilus:1884): GnomeDesktop-WARNING **: Error creating thumbnail for 
file:///media/typhoe/downloads/sabnzbd/complete/Anime_Series/Gankutsuou_h264_dual_audio/Gankutsuou_09_(h264)%5Bcc293c31%5D.mkv:
 Format d'image non reconnu

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


** Tags: amd64 apport-bug raring

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

Title:
  Network transferts crash with SW-IOMMU space messages

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

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

[Bug 1064250] [NEW] chromium-browser crashed with SIGSEGV

2012-10-09 Thread Typhoe
Public bug reported:

Hi,

simply letting gmail open in chromium and locking my session before
leaving.

On the morrow, chromium has crashed.

regards.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Oct  9 10:38:12 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:
 
SegvAnalysis:
 Segfault happened at: 0x7f6b2ecbe61c:  mov0x150(%rax),%r12
 PC (0x7f6b2ecbe61c) ok
 source "0x150(%rax)" (0x0150) not located in a known VMA region (needed 
readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
Stacktrace:
 #0  0x7f6b2ecbe61c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff0e6dce98
StacktraceTop: ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

** Affects: chromium-browser (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash quantal running-unity

** Visibility changed to: Public

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

Title:
  chromium-browser crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1064250/+subscriptions

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


[Bug 436452] Re: easytag assert failure: *** stack smashing detected ***: easytag terminated

2012-10-08 Thread Typhoe
** Changed in: easytag (Ubuntu)
   Status: Triaged => 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/436452

Title:
  easytag assert failure: *** stack smashing detected ***: easytag
  terminated

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

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


[Bug 850689] Re: package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

2012-10-08 Thread Typhoe
** Changed in: zeitgeist-extensions (Ubuntu)
   Status: New => Incomplete

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

Title:
  package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to
  install/upgrade: le sous-processus nouveau script pre-removal a
  retourné une erreur de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist-extensions/+bug/850689/+subscriptions

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

[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-10-08 Thread Typhoe
Latest iso from 2012/10/08 solves the problem.

Thank you!

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed => 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/1030165

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+subscriptions

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


[Bug 940171] Re: kernel BUG at /build/buildd/linux-3.0.0/fs/btrfs/extent-tree.c:5510

2012-10-08 Thread Typhoe
Hi,

got this bug this morning too

Kernel BUG at/build/buildd/linux-3.5.0/fs/btrfs/extent-tree.c:6109!
I'm using kernel 3.5.0-14-generic on a Dell Optiflex 780

I can't get any access back to my system...
I was using a / and a /home in btrfs both.

Trying to boot on a usb key doesn't help because the kernel detects the
hard drive and try to also access the btrfs filesystem  and crash...

Regards

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

Title:
  kernel BUG at /build/buildd/linux-3.0.0/fs/btrfs/extent-tree.c:5510

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

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


[Bug 915626] Re: usb-creator-gtk crashed with SIGSEGV

2012-10-05 Thread Typhoe
Using quantal up to date on 11/05/2012, trying to create an usb key of
quantal AMD64, I get these crashes after I'm been asked for my password.

I'm using an usb 3 port (usb key is 2.0 only).

The password is asked pretty quick in regard of previous times (before
quantal).

I tried to write the iso again, typing my password as soon as it's asked
for, same crash!

I tried to wait (till the usb key led stopped blinking), then typed my
password, the creation of the ubuntu usb key worked!

I'll guess the program doesn't wait enough time before trying to make
the usb key bootable.

regards.

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

Title:
  usb-creator-gtk crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/915626/+subscriptions

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


[Bug 1062120] Re: usb-creator-gtk crashed with SIGSEGV

2012-10-05 Thread Typhoe
*** This bug is a duplicate of bug 915626 ***
https://bugs.launchpad.net/bugs/915626

I'm using an usb 3 port (usb key is 2.0 only).

The password is asked pretty quick in regard of previous times (before
quantal).

I tried to write the iso again, typing my password as soon as it's asked
for, same crash!

I tried to wait (till the usb key led stopped blinking), then typed my
password, the creation of the ubuntu usb key worked!

I'll guess the program doesn't wait enough time before trying to make
the usb key bootable.

regards.

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

Title:
  usb-creator-gtk crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1062120/+subscriptions

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


[Bug 1046088] Re: No Brightness Control on ASUS G75VW Notbook

2012-09-16 Thread Typhoe
Hi,

same problem here.


typhoe@g75vw:~$ cat /sys/class/dmi/id/sys_vendor
ASUSTeK COMPUTER INC.
typhoe@g75vw:~$ cat /sys/class/dmi/id/product_name
G75VW

Regards.

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

Title:
  No Brightness Control on ASUS G75VW Notbook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1046088/+subscriptions

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


[Bug 1044747] Re: mtp filesystem can't mount

2012-09-01 Thread Typhoe
In syslog, these lines are repeted again and again:


Sep  1 18:07:31 g75vw kernel: [ 1075.064067] usb 3-2.1.2: new high-speed USB 
device number 108 using xhci_hcd
Sep  1 18:07:31 g75vw kernel: [ 1075.080955] usb 3-2.1.2: New USB device found, 
idVendor=04e8, idProduct=6860
Sep  1 18:07:31 g75vw kernel: [ 1075.080962] usb 3-2.1.2: New USB device 
strings: Mfr=2, Product=3, SerialNumber=4
Sep  1 18:07:31 g75vw kernel: [ 1075.080966] usb 3-2.1.2: Product: GT-I9300
Sep  1 18:07:31 g75vw kernel: [ 1075.080969] usb 3-2.1.2: Manufacturer: samsung
Sep  1 18:07:31 g75vw kernel: [ 1075.080971] usb 3-2.1.2: SerialNumber: 
4df1b2e6569d5f8d
Sep  1 18:07:31 g75vw kernel: [ 1075.081206] usb 3-2.1.2: ep 0x82 - rounding 
interval to 32768 microframes, ep desc says 0 microframes
Sep  1 18:07:31 g75vw kernel: [ 1075.081214] usb 3-2.1.2: ep 0x4 - rounding 
interval to 32768 microframes, ep desc says 0 microframes
Sep  1 18:07:31 g75vw kernel: [ 1075.081222] usb 3-2.1.2: ep 0x85 - rounding 
interval to 32768 microframes, ep desc says 0 microframes
Sep  1 18:07:31 g75vw kernel: [ 1075.081228] usb 3-2.1.2: ep 0x7 - rounding 
interval to 32768 microframes, ep desc says 0 microframes
Sep  1 18:07:31 g75vw kernel: [ 1075.122317] usb 3-2.1.2: USB disconnect, 
device number 108

mtp-detect doesn't always detect my phone:


typhoe@g75vw:~$ sudo mtp-detect 
libmtp version: 1.1.4

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT 
P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
   Found 1 device(s):
   Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 
7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 3, dev 90
Attempting to connect device(s)
ignoring usb_claim_interface = -99PTP_ERROR_IO: failed to open session, trying 
again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.

then again, the same command:

typhoe@g75vw:~$ sudo mtp-detect 
libmtp version: 1.1.4

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT 
P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
   Found 1 device(s):
   Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 
7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 3, dev 9
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
< repeat for more than 300 times > 
Error 7: Found a bad handle, trying to ignore it.
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object 
handles.
Error 2: Error 02ff: PTP: I/O error
USB low-level info:
   Interface has a kernel driver attached.
   bcdUSB: 512
   bDeviceClass: 0
   bDeviceSubClass: 0
   bDeviceProtocol: 0
   idVendor: 04e8
   idProduct: 6860
   IN endpoint maxpacket: 512 bytes
   OUT endpoint maxpacket: 512 bytes
   Raw device info:
  Bus location: 3
  Device number: 9
  Device entry info:
 Vendor: Samsung
 Vendor id: 0x04e8
 Product: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 
7.7/10.1/S2/S3/Nexus/Note/Y
 Vendor id: 0x6860
 Device flags: 0x48008107
Device info:
   Manufacturer: samsung
   Model: GT-I9300
   Device version: 1.0
   Serial number: 4df1b2e6569d5f8d
   Vendor extension ID: 0x0006
   Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
   Detected object size: 64 bits
   Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
   1001: get device info
   1002: Open session
   1003: Close session
   1004: Get storage IDs
   1005: Get storage info
   1006: Get number of objects
   1007: Get object handles
   1008: Get object info
   1009: Get object
   100a: Get thumbnail
   100b: Delete object
   100c: Send object info
   100d: Send object
   1014: Get device property description
   1015: Get device property value
   1016: Set device property value
   1017: Reset device property value
   101b: Get partial object
   9801: Get object properties supported
   9802: Get object property description
   9803: Get object property value
   9804: Set object property value
   9805: Get object property list
   9810: Get object references
   9811: Set object references
   95c1: Unknown (95c1)
   95c2: Unknown (95c2)
   95c3: Unknown (95c3)
   95c4: Unknown (95c4)
   95c5: Unknown (95c5)
Events supported:
   0x4002
   0x4003
   0x4004
   0x4005
Device Properties Supported:
   0xd401: Synchronization Partner
   0xd402: Friendly Device Name
   0x5003: Image Size
Playable File (Object

[Bug 1044747] Re: mtp filesystem can't mount

2012-09-01 Thread Typhoe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

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

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


[Bug 1044747] [NEW] mtp filesystem can't mount

2012-09-01 Thread Typhoe
Public bug reported:

Hi,

I tried to connect my phone (Samsung GT-I9300 / Galaxy S3 on CyanogenMod
9.1) to my notebook.

Quantal doesn't seem to be able to mount the 2 filesystems availble on
the phone (internal storage and external one, microSD).

In Nautilus, the mount points appear and disappear every few seconds.

I don'tget this behaviour on an other Quantal PC, so maybe it's due to
the USB3 available on this notebook (the other PC is USB2 only, and on
it, I can connect my phone).

Regards.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: mtp-tools 1.1.4-1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CheckboxSubmission: 07c1b2f1302af9a0aa8bf3fa10951319
CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
Date: Sat Sep  1 17:56:32 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.3)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: libmtp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mtp quantal running-unity usb3

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

Title:
  mtp filesystem can't mount

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

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


[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-08-27 Thread Typhoe
Here is also the syslog from this session.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+attachment/3279579/+files/syslog

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

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+subscriptions

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


[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-08-27 Thread Typhoe
Hi,

here is a Xorg.log from latest daily liveCD of quantal amd64 (august,
27th).

Nothing was installed except ssh to let me stop lightdm and get the log
from /var/log (otherwise, as Xorg restart every few seconds... It's not
easy to do anything directly).

Regards.

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+attachment/3279578/+files/Xorg.0.log

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

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+subscriptions

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


[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-08-22 Thread Typhoe
Ok,

I'll update the bug report using the lastest daily of quantal this week
end.

Is there a command line to generate a report using apport? 
Otherwise, I'll only be able to get you the Xorg log (as, without desktop... 
I'll only have command line access).

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

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+subscriptions

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


[Bug 736743] Re: environment block not implemented on btrfs

2012-07-27 Thread Typhoe
Quantal alpha 3 also affected...

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

Title:
  environment block not implemented on btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/736743/+subscriptions

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


[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-07-27 Thread Typhoe
Notebook is an Asus G75VW
Nvidia Card is GTx-670M


typhoe@g75vw:~$ sudo lspci -s 01:00.0 -vvn
01:00.0 0300: 10de:1213 (rev a1) (prog-if 00 [VGA controller])
Subsystem: 1043:2119
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [128 v1] Power Budgeting 
Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
Kernel driver in use: nvidia
Kernel modules: nvidia_current_updates, nouveau, nvidiafb

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

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

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

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


[Bug 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-07-27 Thread Typhoe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030165

Title:
  Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

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

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


[Bug 1030165] [NEW] Xorg can't use nvidia card with nouveau but doesn't fallback to vesa

2012-07-27 Thread Typhoe
Public bug reported:

Hi,

using the livecd (quantal alpha 3), I can't get a desktop display.

I tried to install using the alternate CD. Install setup works, but on first 
boot, nouveau is used and can't get the video card to work, so the X server is 
re-spawned every few seconds, but no desktop (not even a login screen)...
Xorg doesn't fallback to vesa mode...

I had to switch to console (ctrl+alt+f1) and install nvidia driver
(nvidia-current-updates) then reboot to get a working xorg.

Shouldn't xorg fallback to vesa mode if nouveau can't be used? 
I tried to boot on an old 10.04 LTS cdrom, and I can get a working desktop (at 
least the display ;-) ) in vesa mode with it!

Regards.


typhoe@g75vw:~$ lsb_release -rd
Description:Ubuntu quantal (development branch)
Release:12.10


typhoe@g75vw:~$ apt-cache policy xorg xserver-xorg-video-nouveau 
nvidia-current-updates
xorg:
  Installé : 1:7.7+1ubuntu1
  Candidat : 1:7.7+1ubuntu1
 Table de version :
 *** 1:7.7+1ubuntu1 0
500 http://fr.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
100 /var/lib/dpkg/status
xserver-xorg-video-nouveau:
  Installé : 1:1.0.1-1build1
  Candidat : 1:1.0.1-1build1
 Table de version :
 *** 1:1.0.1-1build1 0
500 http://fr.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
100 /var/lib/dpkg/status
nvidia-current-updates:
  Installé : 302.17-0ubuntu2
  Candidat : 302.17-0ubuntu2
 Table de version :
 *** 302.17-0ubuntu2 0
500 http://fr.archive.ubuntu.com/ubuntu/ quantal/restricted amd64 
Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  302.17  Tue Jun 12 16:03:22 
PDT 2012
 GCC version:  gcc version 4.7.1 (Ubuntu/Linaro 4.7.1-5ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity.support.test.0:
 
ApportVersion: 2.4-0ubuntu5
Architecture: amd64
CheckboxSubmission: 07c1b2f1302af9a0aa8bf3fa10951319
CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Sat Jul 28 00:29:18 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: nvidia-current-updates, 302.17, 3.5.0-6-generic, x86_64: installed
ExtraDebuggingInterest: Yes,
GraphicsCard:
 NVIDIA Corporation Device [10de:1213] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:2119]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.3)
MachineType: ASUSTeK COMPUTER INC. G75VW
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-6-generic 
root=UUID=6dca5550-c0e2-443d-b88c-d7c923b64aef ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG75VW.207:bd04/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.37-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~really6.14.4-0ubuntu2
version.xserver-xorg-video-intel: xserver-

[Bug 863593] Re: (Oneiric regression) Missing access to sound cards

2011-10-05 Thread Typhoe
Hi,

sorry for the lack of update from me, but it seems my problem has
disappeared.

I can't reproduce it.

The sound card is now correctly detected at each boot. I'm using the
standard LightDM (the new logon screen) and neither with unity or gnome
3 has the pb occurred anymore.

So for me, this bug report can be closed.

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/863593

Title:
  (Oneiric regression) Missing access to sound cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863593/+subscriptions

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


[Bug 863593] Re: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No sound in oneiric

2011-09-30 Thread Typhoe
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
Subsystem: Lenovo ThinkPad T61
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/863593

Title:
  Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No
  sound in oneiric

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863593/+subscriptions

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


[Bug 863593] [NEW] Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No sound in oneiric

2011-09-30 Thread Typhoe
Public bug reported:

No sound and audio card seems undetected.

Was working in maverick.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: alsa-base 1.0.24+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: aplay: device_list:240: no soundcards found...
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
ArecordDevices: arecord: device_list:240: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/by-path', '/dev/snd/controlC29', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! 
audioconvert ! audioresample ! gconfaudiosink'
CheckboxDescription:
 Cliquez sur « tester » afin de jouer un son sur le périphérique de lecture 
détecté automatiquement.
 
 Avez-vous entendu un son et était-il exempt de distorsion, cliquetis ou autres 
bruits étranges ?
CheckboxTest: audio/playback_auto
Date: Fri Sep 30 21:26:36 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7KETC8WW (2.28 )
dmi.board.name: 89185QG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7KETC8WW(2.28):bd05/08/2009:svnLENOVO:pn89185QG:pvrThinkPadR61:rvnLENOVO:rn89185QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 89185QG
dmi.product.version: ThinkPad R61
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug audio checkbox-bug oneiric

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

Title:
  Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No
  sound in oneiric

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863593/+subscriptions

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

[Bug 863593] Re: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No sound in oneiric

2011-09-30 Thread Typhoe
lspci -vv -s 00:1b.0
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
Subsystem: Lenovo ThinkPad T61
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

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

Title:
  Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No
  sound in oneiric

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863593/+subscriptions

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


[Bug 863593] Re: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No sound in oneiric

2011-09-30 Thread Typhoe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863593

Title:
  Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) No
  sound in oneiric

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/863593/+subscriptions

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


[Bug 850689] Re: package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

2011-09-15 Thread Typhoe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850689

Title:
  package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to
  install/upgrade: le sous-processus nouveau script pre-removal a
  retourné une erreur de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist-extensions/+bug/850689/+subscriptions

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

[Bug 850689] [NEW] package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

2011-09-15 Thread Typhoe
Public bug reported:

just doing a dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: zeitgeist-extension-fts 0.0.7-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 15 09:50:24 2011
ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
PackageArchitecture: all
SourcePackage: zeitgeist-extensions
Title: package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to 
install/upgrade: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: zeitgeist-extensions (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package oneiric

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

Title:
  package zeitgeist-extension-fts 0.0.7-0ubuntu2 failed to
  install/upgrade: le sous-processus nouveau script pre-removal a
  retourné une erreur de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist-extensions/+bug/850689/+subscriptions

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

[Bug 423025] Re: package apturl 0.3.6ubuntu1 f ailed to install/upgrade: erreur pendant la créatio n du répertoire « ./usr/lib/python2.6/d ist-packages/AptUrl/gtk »: Aucun fichier ou do ssier de ce ty

2009-09-02 Thread Typhoe

** Attachment added: "AptOrdering.txt"
   http://launchpadlibrarian.net/31218766/AptOrdering.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/31218767/Dependencies.txt

** Attachment added: "Dmesg.gz"
   http://launchpadlibrarian.net/31218768/Dmesg.gz

** Attachment added: "DpkgTerminalLog.txt"
   http://launchpadlibrarian.net/31218769/DpkgTerminalLog.txt

-- 
package apturl 0.3.6ubuntu1 failed to install/upgrade: erreur pendant la 
création du répertoire « ./usr/lib/python2.6/dist-packages/AptUrl/gtk »: Aucun 
fichier ou dossier de ce type
https://bugs.launchpad.net/bugs/423025
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

[Bug 423025] [NEW] package apturl 0.3.6ubunt u1 failed to install/upgrade: erreur pendant la cré ation du répertoire « ./usr/lib/python2 .6/dist-packages/AptUrl/gtk »: Aucun fichier ou dossier de ce

2009-09-02 Thread Typhoe
Public bug reported:

Binary package hint: apturl

package apturl 0.3.6ubuntu1 failed to install/upgrade: erreur pendant la
création du répertoire « ./usr/lib/python2.6/dist-packages/AptUrl/gtk »:
Aucun fichier ou dossier de ce type

ProblemType: Package
Architecture: amd64
Date: Wed Sep  2 09:53:56 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: erreur pendant la création du répertoire 
« ./usr/lib/python2.6/dist-packages/AptUrl/gtk »: Aucun fichier ou dossier de 
ce type
NonfreeKernelModules: nvidia
Package: apturl 0.3.6ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SourcePackage: apturl
Title: package apturl 0.3.6ubuntu1 failed to install/upgrade: erreur pendant la 
création du répertoire « ./usr/lib/python2.6/dist-packages/AptUrl/gtk »: Aucun 
fichier ou dossier de ce type
Uname: Linux 2.6.31-9-generic x86_64

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


** Tags: amd64 apport-package

-- 
package apturl 0.3.6ubuntu1 failed to install/upgrade: erreur pendant la 
création du répertoire « ./usr/lib/python2.6/dist-packages/AptUrl/gtk »: Aucun 
fichier ou dossier de ce type
https://bugs.launchpad.net/bugs/423025
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

[Bug 185704] Re: gnome-screensaver-gl-helper crashed with SIGSEGV

2008-10-22 Thread Typhoe
Same problem also here.

I use a blank screen as my screen saver.

when I lock my session and try to log back, I can't (not seeing the
dialog box. The mouse cursor is there, and disappear on the dialog box
position).

Killing the screen saver from terminal let me get back in my session.

-- 
gnome-screensaver-gl-helper crashed with SIGSEGV
https://bugs.launchpad.net/bugs/185704
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


[Bug 270980] Re: setVirtual() doesn't set correct value if second display is bigger

2008-09-17 Thread Typhoe
Today, I have a little problem with my intrepid install... the window
server won't start anymore (guess intrepid is definitively still in
alpha ;) stage).

Anyway, my card is a nvidia one.
$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)

I'm using the nvidia driver provided by your packages if I'm not wrong.
Not the "envy" one, the standard one proposed by the nvidia-common
package.

As soon as I'll have my intrepid working again, I'll post the xorg log
you asked.

-- 
setVirtual() doesn't set correct value if second display is bigger
https://bugs.launchpad.net/bugs/270980
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


[Bug 270980] Re: setVirtual() doesn't set correct value if second display is bigger

2008-09-16 Thread Typhoe
Hi Alberto,

that worked.

Test 1.
1. Xorg.conf already with the right virtual display setting (3600 1200) for me.
2. Edit file, remove section Display and virtual setting
3. Restart Xorg
4. Use screen-resolution-extra to activate extended screen (first screen in 
1680x1050, change second to 1920x1200)
5. Check xorg.conf, Virtual is set to 3600 1200
=> OK


Test 2.
1. Xorg.conf already with the right virtual display setting (3600 1200) for me.
2. Edit file, remove section Display and virtual setting
3. Restart Xorg
4. Use screen-resolution-extra to activate extended screen (first screen in 
1680x1050, leave second to default which is equal to the setting of first 
screen 1680x1050)
5. Check xorg.conf, Virtual is set to 3360 1050
3. Restart Xorg
4. Check display: First screen is in 1680x1050, second is in 1400x1050 (should 
be in 1680x1050, problem of my screen, not relevant).
5. Decide to put second display in its native resolution: 1920x1200, so launch 
again screen-resolution-extra, but second screen does not offer resolution 
above 1680x1050 anymore.
6. Try to disable extended display in screen-resolution-extra : no changes are 
done to the xorg.conf
=> NOK (not ok) 
If we don't specify the max resolution of second display first time, we can't 
change the setting after to get an other resolution (greater) for the second 
screen in the app.

Test 3.
1. Change Xorg.conf with a lower virtual display setting (2400 1050) than twice 
the horizontal size of the primary screen.
2. Restart Xorg
3. Use screen-resolution-extra to activate extended screen (first screen in 
1680x1050, the second can't be set to anything greater than 1680x1050)
4. Check xorg.conf, Virtual is set to 3360 1050
=> NOK
If we have a previous Virtual setting in the xorg.conf, we have same problem as 
in test 2.

So, the formula to calculate the Virtual setting should be:
(MAX Horizontal size of screen 1 + MAX Horizontal size of screen 2) BY (MAX 
vertical size screen 1 + MAX vertical size screen 2)

Hope these tests will help.

Best regards,
Typhoe

-- 
setVirtual() doesn't set correct value if second display is bigger
https://bugs.launchpad.net/bugs/270980
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


[Bug 270980] Re: setVirtual() doesn't set correct value if second display is bigger

2008-09-16 Thread Typhoe
And I confirm that setting the virtual display to 3600 1200 in the
xorg.conf "manually" let me (after a xorg restart) choose the correct
resolutions for both my displays to use with the extended mode in the
gnome display setting window.

So that's definetly an error for screen-resolution-extra not to set the virtual 
display to me the max.
It should be:
 
(Horizontal size of screen 1 + Horizontal size of screen 2)BYmax of 
(vertical size screen 1,vertical size screen 2)

Thank you for your job,
regards,
Typhoe

-- 
setVirtual() doesn't set correct value if second display is bigger
https://bugs.launchpad.net/bugs/270980
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


[Bug 269757] Re: policyui.py crashed with NameError in setVirtual()

2008-09-16 Thread Typhoe
Hi,

I can confirm it doesn't crash anymore.

That issue is resolved.

But now I have a different problem (I made a new LP bug #270980):
My main notebook display is 1680x1050 and my secondary display is 1920x1200

The virtual setting in the xorg.conf file is set to 3360x1050 (1680*2 x 1050)...
Should be something like (1680+1920)x max(1050,1200) => 3600x1200 , shouldn't 
it?

Regards,
Typhoe

-- 
policyui.py crashed with NameError in setVirtual()
https://bugs.launchpad.net/bugs/269757
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


[Bug 270980] [NEW] setVirtual() doesn't set correct value if second display is bigger

2008-09-16 Thread Typhoe
Public bug reported:

Binary package hint: screen-resolution-extra

Hi,

My main notebook display is 1680x1050 and my secondary display is
1920x1200 (so it is bigger than the main one).

With screen-resolution-extra, the virtual setting in the xorg.conf file
is set to 3360x1050 (1680*2 x 1050)...

Should be something like (1680+1920)x max(1050,1200) => 3600x1200 ,
shouldn't it?

Regards,
Typhoe

** Affects: screen-resolution-extra (Ubuntu)
 Importance: Undecided
 Status: New

-- 
setVirtual() doesn't set correct value if second display is bigger
https://bugs.launchpad.net/bugs/270980
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


[Bug 262906] Re: policyui.py crashed with TypeError in setVirtual()

2008-09-13 Thread Typhoe
Hi, 
new LP report #269757
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/269757

Thanks too

-- 
policyui.py crashed with TypeError in setVirtual()
https://bugs.launchpad.net/bugs/262906
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


[Bug 269757] Re: policyui.py crashed with NameError in setVirtual()

2008-09-13 Thread Typhoe
That bug is NOT RESOLVED by the fix released for LB #262906.
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/262906

It could be the same I previously reported as LB #263682
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/263682 
which was marked as duplicate of bug #262906

-- 
policyui.py crashed with NameError in setVirtual()
https://bugs.launchpad.net/bugs/269757
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


[Bug 269757] Re: policyui.py crashed with NameError in setVirtual()

2008-09-13 Thread Typhoe

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/17574908/Dependencies.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/17574909/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/17574910/ProcStatus.txt

** Attachment added: "Traceback.txt"
   http://launchpadlibrarian.net/17574911/Traceback.txt

** Visibility changed to: Public

-- 
policyui.py crashed with NameError in setVirtual()
https://bugs.launchpad.net/bugs/269757
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


[Bug 262906] Re: policyui.py crashed with TypeError in setVirtual()

2008-09-12 Thread Typhoe
Sorry, problem still here for me with v0.1.1

I still get a crash when trying to set virtual desktop

Typhoe

-- 
policyui.py crashed with TypeError in setVirtual()
https://bugs.launchpad.net/bugs/262906
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


[Bug 263682] Re: policyui.py crashed with TypeError in setVirtual()

2008-09-01 Thread Typhoe
I tried to invoke the command using the command line.
Here is the ouput I got:
python /usr/share/screen-resolution-extra/policyui.py -1,-1:-1x-1 
1680,0:1920x1200 0,0:1680x1050
Traceback (most recent call last):
  File "/usr/share/screen-resolution-extra/policyui.py", line 190, in 
on_button1_clicked
status = self.conf.setVirtual(self.resolution)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in 
__call__
**keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback 
(most recent call last):
  File "/var/lib/python-support/python2.5/dbus/service.py", line 696, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File "/usr/share/screen-resolution-extra/screenresolution-mechanism.py", line 
259, in setVirtual
backup = source + time.time()
TypeError: cannot concatenate 'str' and 'float' objects

-- 
policyui.py crashed with TypeError in setVirtual()
https://bugs.launchpad.net/bugs/263682
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


[Bug 263682] Re: policyui.py crashed with TypeError in setVirtual()

2008-09-01 Thread Typhoe

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/17210365/Dependencies.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/17210366/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/17210367/ProcStatus.txt

** Attachment added: "Traceback.txt"
   http://launchpadlibrarian.net/17210368/Traceback.txt

** Visibility changed to: Public

-- 
policyui.py crashed with TypeError in setVirtual()
https://bugs.launchpad.net/bugs/263682
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


[Bug 242966] Re: snd_pcsp can take precedence of soundcards

2008-07-29 Thread Typhoe
Hi,

I too had this problem.

The fix 'b) use "padevchooser" to select the proper ALSA sink for your sound 
card (full name available from the PulseAudio Manager)' suggested by Conn 
worked perfectly for me.
sink = alsa_output.pci_8086_284b_alsa_playback_0

Lenovo R61 with lastest intrepid kernel/packages (2.6.26-5 64bits).
 Liste des PLAYBACK périphériques 
carte  0: Intel [HDA Intel], périphérique 0 : AD198x Analog [AD198x Analog]
  Sous-périphériques: 1/1
  Sous-périphérique: #0: subdevice #0
carte  0: Intel [HDA Intel], périphérique 1 : AD198x Digital [AD198x Digital]
  Sous-périphériques: 1/1
  Sous-périphérique: #0: subdevice #0
carte  1: pcsp [pcsp], périphérique 0 : pcspeaker [pcsp]
  Sous-périphériques: 1/1
  Sous-périphérique: #0: subdevice #0

Regards,
Typhoe

-- 
snd_pcsp can take precedence of soundcards
https://bugs.launchpad.net/bugs/242966
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

[Bug 178504] Re: [hardy] Intel audio sounds awful

2008-03-03 Thread Typhoe
Hi,

problem fixed for me in hardy now.

I still have to change the detected the sound device to be able to set
the sound volume, but I have sound again.

Regards

-- 
[hardy] Intel audio sounds awful
https://bugs.launchpad.net/bugs/178504
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


[Bug 178504] Re: [hardy] Intel audio sounds awful

2008-01-17 Thread Typhoe
Hi,

no sound at all on my notebook. 
 lspci |grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)

It is a Lenovo Thinkpad R61.

In Gutsy, I can get sound after unmuting the sound and setting the
volume controler to use the PCM and not the Microphone (which is the
default after a fresh install)

In Hardy, I can't get any sound at all...

Regards.

-- 
[hardy] Intel audio sounds awful
https://bugs.launchpad.net/bugs/178504
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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


[Bug 182013] Re: package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-11 Thread Typhoe
 apt-get install
Lecture des listes de paquets... Fait
Construction de l'arbre des d��pendances   
Lecture des informations d'��tat... Fait
0 mis �� jour, 0 nouvellement install��s, 0 �� enlever et 2 non mis �� jour.
1 partiellement install��s ou enlev��s.
Apr��s cette op��ration, 0o d'espace disque suppl��mentaires seront utilis��s.
Param��trage de flashplugin-nonfree (9.0.115.0ubuntu3) ...
Installing from local file 
/var/cache/flashplugin-nonfree/install_flash_player_9_linux.tar.gz
Flash Plugin installed.
/usr/lib/nspluginwrapper/i386/linux/npviewer.bin: error while loading shared 
libraries: libselinux.so.1: cannot open shared object file: No such file or 
directory
nspluginwrapper: no appropriate viewer found for 
/usr/lib/flashplugin-nonfree/libflashplayer.so
dpkg��: erreur de traitement de flashplugin-nonfree (--configure)��:
 le sous-processus post-installation script a retourn�� une erreur de sortie 
d'��tat 1
Des erreurs ont ��t�� rencontr��es pendant l'ex��cution��:
 flashplugin-nonfree
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: 
subprocess post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/182013
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 182013] Re: package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-11 Thread Typhoe
ldd /usr/lib/nspluginwrapper/i386/linux/npviewer.bin | grep "not found"
libselinux.so.1 => not found
libselinux.so.1 => not found
libselinux.so.1 => not found
libpixman-1.so.0 => not found

locate libselinux.so.1
/media/sda6/lib/libselinux.so.1
/lib/libselinux.so.1

locate libpixman-1.so.0
/usr/lib/libpixman-1.so.0.9.6
/usr/lib/libpixman-1.so.0

Hope this will help.

Regards

-- 
package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: 
subprocess post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/182013
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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


[Bug 182013] package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-11 Thread Typhoe
Public bug reported:

Binary package hint: flashplugin-nonfree

Fresh new install from Hardy alpha 3

Install the package in console

crash ...

Thank you

ProblemType: Package
Architecture: amd64
Date: Fri Jan 11 14:48:46 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: flashplugin-nonfree 9.0.115.0ubuntu3
PackageArchitecture: amd64
SourcePackage: flashplugin-nonfree
Title: package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: 
subprocess post-installation script returned error exit status 1
Uname: Linux thinkpad 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008 
x86_64 GNU/Linux

** Affects: flashplugin-nonfree (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package

-- 
package flashplugin-nonfree 9.0.115.0ubuntu3 failed to install/upgrade: 
subprocess post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/182013
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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


  1   2   >